все бегом смотреть, лайкать и комментировать !!
custom 54429982544909191241custom 54563091527101729761

Channel
@offkickin
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
85subscribers
+67 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003880964798 |
|---|---|
| Type | Channel |
| Username | @offkickin |
| Created | Between 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/offkickin |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 05:57 | 85 | +16 |
| 29 Aug 2026, 15:07 | 69 | -6 |
| 22 Aug 2026, 16:54 | 75 | +21 |
| 16 Aug 2026, 05:04 | 54 | +30 |
| 11 Aug 2026, 11:03 | 24 | no change |
| 8 Aug 2026, 13:31 | 24 | +6 |
| 7 Aug 2026, 19:43 | 18 | first reading |
17 posts held, back to 6 August 2026 — the 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 17 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
102 reactions across 11 posts, in 11 distinct kinds. The most used accounts for 19.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5456309152710172976 | 20 | 19.6% | |
| custom 5442998254490919124 | 16 | 15.7% | |
| custom 5443127129279604532 | 12 | 11.8% | |
| custom 5438444923437230481 | 10 | 9.80% | |
| custom 5440429821098238614 | 10 | 9.80% | |
| custom 5438427932546605858 | 8 | 7.84% | |
| custom 5440362050809274969 | 8 | 7.84% | |
| custom 5438514098180495827 | 6 | 5.88% | |
| custom 5440676859027174208 | 6 | 5.88% | |
| custom 5438614686314570899 | 5 | 4.90% | |
| custom 5438634460344001448 | 1 | 0.98% |
Custom emoji. Every row above is a 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 11 of the 17 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 102 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 6 August 2026 to 10 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.
все бегом смотреть, лайкать и комментировать !!
custom 54429982544909191241custom 54563091527101729761
🎀 🤩]🤩ɛ𝞈 𝘃ı𝗱𝝴ᦅ’🎀𝗸ı𝗰kı𝗻;🤩 🤩➿🤩➿🤩➿🤩➿🤩 ( ℋᦅ𝞈 ყᦅ𝗎 𝗳𝝴ɛ𝗹 𝗹ı𝗸𝝴 𝘁ჩ𐐼𝘁, 🤩 ꭑყ ჩ𝝴𐐼ɾ𝘁 𝗯ɛ𐐼𝘁s 𝗳𐐼s𝘁 ! •𝘁ɾ𝗎𝝴 𝗯ꭑ / 🤩 :𝗹ı𝗻𝗸 & t𝘁🎀 🤩 ±𐐼𝗎𝗱ı𝘁ıᦅ𝗻 🤩 🤩➿🤩➿🤩➿🤩➿🤩 🎀
custom 54384449234372304814custom 54406768590271742082custom 54431271292796045322custom 54403620508092749691custom 54404298210982386141custom 54563091527101729761
Sticker, posted without a caption
custom 54563091527101729761
🎀 ☠️]🌟ᦅs𝘁𝝴ɾ’ 🎀 𝗸ı𝗰kı𝗻; 🐈⬛ 🤩➿🤩➿🤩➿🤩➿🤩 ( ℋ𐐼𝘁ı𝗻ᦋ ꭑ𝝴 ıs 𝗹ı𝗸𝝴 🍭 🎀 🤩 𐐼𝗹𝗹 ყᦅ𝗎 𝗱ᦅ •ı𝗰ᦅ𝗻ı𝗰 / ❤️ :𝗯ყ ꭑıs𝘁𐐼𝗸𝝴 & 🍲 ±𝗯ყ.𝗸𐐼𝘁ss𝝴ɾ𐐼𝗹ı𝘁 🎀 🕷 £ 𝗸ı𝗰kı𝗻' % .s𝗽ᦅɾ𝘁 🎩 ᦅ𝘁3 — 𝗺ı𝗻ı ‘𝗰ᦅ𝘃𝝴ɾ !sᦅᦅ𝗻, 🤩➿🤩➿🤩➿🤩➿🤩 🎀
custom 54429982544909191247custom 54563091527101729763custom 54384279325466058582custom 54386146863145708992custom 54384449234372304811custom 54403620508092749691custom 54404298210982386141custom 54406768590271742081
Sticker, posted without a caption
custom 54429982544909191242custom 54563091527101729761
Sticker, posted without a caption
custom 54404298210982386142custom 54429982544909191241custom 54563091527101729761
File, posted without a caption
custom 54563091527101729763custom 54431271292796045322custom 54384279325466058581custom 54384449234372304811custom 54385140981804958271custom 54386146863145708991custom 54403620508092749691custom 54404298210982386141
🎀 🤩]🤩𝗎𝗱ı𝘁ıᦅ𝗻’ 🎀𝗯𐐼𝗯ყꭑᦅ𝗻;🤩 🤩➿🤩➿🤩➿🤩➿🤩 ㅤ( ℋᦅ𝞈 ყᦅ𝗎 𝗳𝝴ɛ𝗹 𝗹ı𝗸𝝴 𝘁ჩ𐐼𝘁, 🤩 🤩 ꭑყ ჩ𝝴𐐼ɾ𝘁 𝗯ɛ𐐼𝘁s 𝗳𐐼s𝘁 ! •𝗯𝗎sყ / 🤩 :𝗰ჩı𝗾𝗎ı𝘁𐐼 & 🤩 🤩 ±𐐼ჩყ𝝴ᦅ𝗻× ɾ𝗎𝗸𐐼 🎀 🤩 £ 𝗸ı𝗰kı𝗻' % .s𝗽ᦅɾ𝘁 🤩 𝗯ᦅ𝘁 — ɾ𝗎𝗹𝝴s ‘🤩𝗻𝗱 !𐐼𝗻𝗸ɛ𝘁𐐼, ➿ 𝗳ɾɛ𝝴 - ᦅ𝘁3 ( 𐐼s𐐼 , # 🎀 𝗽ჩ𐐼ɾı𝘁𐐼 | 🤩 *ɾᦅɾa ) 🤩 *𝓘 𝗹ı-𝗹ı-𝗹ık𝝴 ı𝘁, I 𝗹ı-𝗹ı-𝗹ı𝗸ɛ ı𝘁» 🤩➿🤩➿🤩➿🤩➿🤩 🎀
custom 54563091527101729767custom 54385140981804958274custom 54384279325466058583custom 54384449234372304812custom 54386146863145708992custom 54403620508092749692custom 54404298210982386142custom 54406768590271742082
Sticker, posted without a caption
Sticker, posted without a caption
Sticker, posted without a caption
Sticker, posted without a caption
Showing the 12 most recent of 17 posts we hold for @offkickin. 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.
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“埜 ‹ 𝑲𝝸ᥴ𝑲𝝸ᥒ' .𝑾𝝸ᥒ᥊۫𝅄 ִ” (@offkickin), 85 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/offkickin.
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.