Telegram RegisterThe public register of Telegram
Telegram profile photo for Переоформлю

Channel

Переоформлю

@irlKaneokure

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

5subscribers

-78 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003777561721
TypeChannel
Username@irlKaneokure
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live11 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/irlKaneokure

Growth

48745.512 August 2026 — 83 subscribers13 August 2026 — 85 subscribers20 August 2026 — 87 subscribers27 August 2026 — 4 subscribers3 September 2026 — 5 subscribers512 August 20263 September 2026
5 measurements spanning 22 days, net -78. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 09:235+1
27 Aug 2026, 11:274-83
20 Aug 2026, 14:4387+2
13 Aug 2026, 22:2985+2
12 Aug 2026, 17:3383first reading

Engagement

20 posts held, back to 10 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

316 reactions across 13 posts, in 10 distinct kinds. The most used accounts for 19.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53011120212976914136219.6%
custom 53165558174560000204714.9%
custom 54408025512450651914213.3%
custom 60172000257953025513812.0%
custom 52041471173413037033611.4%
custom 5902097565142226487319.81%
custom 5377828117253488473309.49%
custom 5469743415275059862206.33%
🦄72.22%
💘30.949%

Custom emoji. 8 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 13 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 316 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 10 August 2026 to 12 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

12 Aug 2026, 17:25 UTC7 viewsread 12 August 2026

Мне не нравится этот пост я хочу его переделать

Signed ︎︎︎︎︎⏝ִ︶ ݃◍⃘ׄ͜ ֩ᰰ ☀️ֹ💌 ꛁМ𑩙ᩙ࣪⃞𑄜︪чບ ч𑩙𑜅н 𐑼⎯ִ‌‌ ִྀི🌈̫ #𝗣𝘂𝗱𝗱𝗶𝗻𝗴 #🐰крол

12 Aug 2026, 15:46 UTC23 viewsread 12 August 2026
Forwarded from @DirectorPhoboss

Posted without readable text

Signed ︎︎︎︎︎⏝ִ︶ ݃◍⃘ׄ͜ ֩ᰰ ☀️ֹ💌 ꛁМ𑩙ᩙ࣪⃞𑄜︪чບ ч𑩙𑜅н 𐑼⎯ִ‌‌ ִྀི🌈̫ #𝗣𝘂𝗱𝗱𝗶𝗻𝗴 #🐰крол

12 Aug 2026, 13:42 UTC30 viewsread 12 August 2026
Sticker

Sticker, posted without a caption

Signed ︎︎︎︎︎⏝ִ︶ ݃◍⃘ׄ͜ ֩ᰰ ☀️ֹ💌 ꛁМ𑩙ᩙ࣪⃞𑄜︪чບ ч𑩙𑜅н 𐑼⎯ִ‌‌ ִྀི🌈̫ #𝗣𝘂𝗱𝗱𝗶𝗻𝗴 #🐰крол

11 Aug 2026, 16:53 UTC91 views12 reactionsread 12 August 2026
Photo

🔵ТУПО Я — 🤩ОЧИ-ЧАН🤩🤩

custom 53011120212976914138💘2custom 59020975651422264872

11 Aug 2026, 15:32 UTC97 views2 reactionsread 12 August 2026
Sticker

Sticker, posted without a caption

custom 53011120212976914132

11 Aug 2026, 07:53 UTC121 views6 reactionsread 12 August 2026
Sticker

Sticker, posted without a caption

custom 52041471173413037032custom 53011120212976914132custom 53165558174560000201custom 59020975651422264871

11 Aug 2026, 07:52 UTC121 views48 reactionsread 12 August 2026
File

File, posted without a caption

custom 544080255124506519111custom 53011120212976914139custom 60172000257953025519custom 53165558174560000206custom 52041471173413037035custom 54697434152750598625custom 53778281172534884733

10 Aug 2026, 18:47 UTC125 views5 reactionsread 12 August 2026
Sticker

Sticker, posted without a caption

custom 53011120212976914132custom 53165558174560000201custom 54697434152750598621custom 60172000257953025511

10 Aug 2026, 18:47 UTC127 views56 reactionsread 12 August 2026

Posted without readable text

custom 590209756514222648712custom 54408025512450651919custom 60172000257953025519custom 53011120212976914137custom 53165558174560000206custom 53778281172534884736🦄5custom 52041471173413037032

Showing the 12 most recent of 20 posts we hold for @irlKaneokure. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 3 September 2026 — this entry's latest reading, not the date you are reading this.

“Переоформлю” (@irlKaneokure), 5 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/irlKaneokure.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.