Telegram RegisterThe public register of Telegram
Telegram profile photo for рест||kk3f1rq💏

Channel

рест||kk3f1rq💏

@crazymegahui

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

11subscribers

-1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002115059296
TypeChannel
Username@crazymegahui
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live22 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/crazymegahui

Growth

111211.57 August 2026 — 12 subscribers12 August 2026 — 12 subscribers22 August 2026 — 11 subscribers7 August 202622 August 2026
3 measurements spanning 15 days, net -1. 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”. The vertical axis spans 11–12 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 20:4811-1
12 Aug 2026, 05:0012no change
7 Aug 2026, 12:4812first reading

Engagement

16 posts held, back to 10 June 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 16 posts for this entry, the most recent from 22 June 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
44s
Average length
15s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘7926.4%
🔥6020.1%
custom 53665432882517265204414.7%
custom 52470127034315723463110.4%
custom 5366171137925461039237.69%
165.35%
💋155.02%
🍓93.01%
🕊82.68%
👀51.67%
🎉41.34%
31.00%
🦄20.669%

Custom emoji. 3 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 areTelegram’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 10 of the 16 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 299reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 10 June 2024 to 22 June 2024, 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

22 Jun 2024, 12:46 UTC217 views13 reactionsread 12 August 2026
Photo

.. 🌺 new post !¡ cr: @crazymegahui ⭒๋࣭ ⭑связки с Аришей в комментариях!!✩°。 🌷ⲧⲉⳋⲋ —> #lumitalle #связки —проголосовать за канал

custom 524701270343157234643💘2🕊2🦄2

22 Jun 2024, 06:43 UTC184 views18 reactionsread 12 August 2026
Video

.. 🍒 new vi`deo !¡ cr:: @crazymegahui ੭ ੭ ⲥⲥыⲗⲟⳡⲕⲁ ⲏⲁ ⲃυⲇⲉⲟ — *пиу* ˎˊ˗ 🌷ⲧⲉⳋⲋ —> #питерскаятусовка #видеоотавтора —проголосовать за канал

💘7custom 53665432882517265204custom 53661711379254610393custom 524701270343157234621🕊1

19 Jun 2024, 07:45 UTC174 views47 reactionsread 12 August 2026
Photo

..🌸 new post !¡ cr: @crazymegahu ⭒๋࣭ ⭑связки со Славой в комментариях!!✩°。 🌷ⲧⲉⳋⲋ —> #славакпсс #связки —проголосовать за канал

🔥25💘10💋8custom 536654328825172652021custom 53661711379254610391

18 Jun 2024, 08:41 UTC203 views34 reactionsread 12 August 2026
Photo

.. 🎀 new post !¡ cr: @crazymegahui ⭒๋࣭ ⭑связки с букером в комментариях!!✩°。⋆ 🌷ⲧⲉⳋⲋ —> #booker #связки —проголосовать за канал

💘19👀5🔥52custom 52470127034315723462💋1

17 Jun 2024, 20:35 UTC148 views48 reactionsread 12 August 2026
Photo

..🕷 new post !¡ cr: @crazymegahui •связки с Русланом в комментариях!• 🌷ⲧⲉⳋⲋ —> #cmh #связки — проголосовать за канал

custom 536654328825172652020custom 524701270343157234675custom 53661711379254610395💘4💋2🔥2🕊2

17 Jun 2024, 20:19 UTC133 views31 reactionsread 12 August 2026
Forwarded from @seshkavePhoto

💊набор в папку + поиск мью т.к каналов много,я не успею следить за всеми и проявлять активность.если вы хотите чтоб я активила в ваших каналах то было бы славно добавиться в папку. ♰чтобы попасть в папку:: 1.быть подписаным на мой тгк. 2.репост этого поста к себе в тгк. 3.отметится под этим постом в комментариях.

custom 536617113792546103912custom 53665432882517265206custom 52470127034315723465🎉3💘3🔥2

17 Jun 2024, 18:54 UTC181 views42 reactionsread 12 August 2026
Video

мои ✨ⲥⲥыⲗⲟⳡⲕⲁ ⲏⲁ ⲃυⲇⲉⲟ — *пиу* 🖇️ ⲧⲉⳋⲋ —> #мазенцовы #видеоотавтора рт,рк,мью?

🔥19custom 53665432882517265207custom 5247012703431572346632🍓2custom 53661711379254610392💘1

17 Jun 2024, 14:41 UTC163 views15 reactionsread 12 August 2026
Sticker

Sticker, posted without a caption

💘9🍓3🕊3

Showing the 12 most recent of 16 posts we hold for @crazymegahui. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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 22 August 2026 — this entry's latest reading, not the date you are reading this.

“рест||kk3f1rq💏” (@crazymegahui), 11 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/crazymegahui.

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.