Telegram RegisterThe public register of Telegram
Telegram profile photo for `𝙇𝙐𝘾𝙆𝙔 𝙁𝙇𝙊𝙊𝘿`

Channel

`𝙇𝙐𝘾𝙆𝙔 𝙁𝙇𝙊𝙊𝘿`

@lucky_flood

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

8subscribers

+0 since we began measuring on 28 August 2026

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

Register entry

Telegram ID-1002316154388
TypeChannel
Username@lucky_flood
Descriptionⲏⲟⲃыύ υⲏⲫⲟ, ⲡⲣⲉⲕⲣⲁⲥⲏⲟⲅⲟ ⲫⲗⲩⲇⲁ 🤍 ⲃⲗⲇ:: @yang_danyon ⲥⲟ ⲃⲗⲇ:: @mreixs
CreatedBetween 1 September 2024 and 2 December 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 August 2026
Last confirmed live29 August 2026
Measurements held2
On Telegramt.me/lucky_flood

Growth

828 Aug 2026, 23:01 — 8 subscribers28 Aug 2026, 23:15 — 8 subscribers28 Aug 2026, 23:0128 Aug 2026, 23:15
2 measurements taken within a single day. 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 7–9 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 23:158no change
28 Aug 2026, 23:018first reading

Engagement

20 posts held, back to 2 December 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 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 January 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Videos
14

Lifetime counters from Telegram’s own channel header, read 28 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
5m 00s
Average length
21s

Measured directly from 14 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

50 reactions across 17 posts, in 14 distinct kinds. The most used accounts for 38.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🕊1938.0%
918.0%
🔥36.00%
🖕36.00%
🙏36.00%
🎉24.00%
💘24.00%
🤬24.00%
🦄24.00%
🍓12.00%
🍾12.00%
👌12.00%
😭12.00%
🥰12.00%

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 17 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 50 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 2 December 2024 to 12 January 2025, 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 Jan 2025, 10:13 UTC100 views7 reactionsread 28 August 2026

флуд закрывается. извините, ваш владелец не успевает сидеть в телефоне.

🖕3🤬2👌1😭1

11 Jan 2025, 23:08 UTC106 views5 reactionsread 28 August 2026
Video

❕𝙉𝙀𝙒 𝙋𝙊𝙎𝙏 ❕ я заметил что тут только один жн перс.

🙏2💘1🕊1🦄1

31 Dec 2024, 07:50 UTC123 views3 reactionsread 28 August 2026
Video

❕𝙉𝙀𝙒 𝙋𝙊𝙎𝙏 ❕ видео чучуть с опозданием ну что в этом такого.🙄

🔥3

26 Dec 2024, 20:18 UTC118 views2 reactionsread 28 August 2026

на новый год я повешу не герлянды , а участников которые не активничают.

🎉2

26 Dec 2024, 15:31 UTC107 viewsread 28 August 2026
Video

❕𝙉𝙀𝙒 𝙋𝙊𝙎𝙏 ❕ строчек мало , но видео долгое , лучшие ляльки.

25 Dec 2024, 07:04 UTC82 views4 reactionsread 28 August 2026
Video

❕𝙉𝙀𝙒 𝙋𝙊𝙎𝙏 ❕ чучуть изменения будут , ну кароче ёлочки просто прекрасные все молодцы , живите

2🍾1🕊1

23 Dec 2024, 05:22 UTC65 views4 reactionsread 28 August 2026
Video

!!новое видео!! кто не понял у намджуна премиум стикеры

🕊21💘1

20 Dec 2024, 22:23 UTC68 views2 reactionsread 28 August 2026
Video

!!новое видео!! со владелец приколист просто

🕊1🥰1

19 Dec 2024, 22:14 UTC65 views2 reactionsread 28 August 2026
Video

!!новое видео!! владельца любим , не обижаем , но по плану должно было быть другое видео , но оно вышло не очень.

1🕊1

18 Dec 2024, 22:44 UTC52 views1 reactionsread 28 August 2026
Video

!!новое видео!! по больше части со владелец попадает под буллинг , ну что за? забыл сюда владельца добавить

🕊1

18 Dec 2024, 17:53 UTC53 views5 reactionsread 28 August 2026
Video

!!новое видео!! совладелец плачет в подушку почему только 1 голос , те у кого было 0 голосов извините вас в видео нету

🕊31🙏1

17 Dec 2024, 03:38 UTC44 views2 reactionsread 28 August 2026
Video

!!новое видео!! чет тренды всякие выходят слишком часто ну ладно

1🕊1

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

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

“`𝙇𝙐𝘾𝙆𝙔 𝙁𝙇𝙊𝙊𝘿`” (@lucky_flood), 8 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/lucky_flood.

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.