#разрыв Мы будем скучать

Channel
ʟᴜᴍɪɴᴏᴜs ɪɴꜰᴏ
@luminousf1ood
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
81subscribers
+5 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003606413977 |
|---|---|
| Type | Channel |
| Username | @luminousf1ood |
| Created | Between 1 December 2025 and 21 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 9 September 2026 |
| On Telegram | t.me/luminousf1ood |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 09:36 | 81 | +1 |
| 18 Aug 2026, 11:33 | 80 | +4 |
| 10 Aug 2026, 22:53 | 76 | no change |
| 10 Aug 2026, 15:01 | 76 | first reading |
Engagement
20 posts held, back to 21 March 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 20 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
17 reactions across 8 posts, in 6 distinct kinds. The most used accounts for 29.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 29.4% | |
| 👎 | 3 | 17.6% | |
| 🥰 | 3 | 17.6% | |
| ❤🔥 | 2 | 11.8% | |
| 💔 | 2 | 11.8% | |
| 🔥 | 2 | 11.8% |
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 8 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 17 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 21 March 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.
Recent posts
Еще раз здравствуйте! На связи Хана 🫶 В связи с этим всем мною было принято решение закрыть набор на нн срок пока все не уладится, мы с моей командой администраторов не хотим проблем и сливов наших переписок во флуде Спасибо что с нами #РепостСоюз
❤1
Хаюшки! На связи Хана🫶 Спешу сообщить что в нашем флуде появилась крыса которая сливала нашу информацию в другой флуд, у нас подчистую забрали наше оформление и всё схоже, просим пожалуйста если вам напишут с идеей вступить во флуд "About the forgotten" пожалуйста не вступайте, владелец этого флуда очень нехороший человек и думаю можно будет рассказать вам это все но позже, просто не заходите не тратьте свои нервы об…
❤2🔥2🥰1
Хаюшки! На связи Хана🫶 Мы в срочном порядке ищем монтажёра для нашего флуда Что должен делать монтажёр •Просто видео хотя бы раз в неделю Монтажёру будет снижена норма и наши великие спасибо 🙏 #РепостСоюз
Хаюшки! На связи Хана🫶 Спешу сообщить что наш флуд завершил перезагрузку, поменялось •Названия •Аватарка •Совладелица сменила роль •Начались поиски монтажера •Ссылка на лайф Спасибо что остаётесь с нами🫶 #РепостСоюз
Channel name was changed to «ʟᴜᴍɪɴᴏᴜs ɪɴꜰᴏ»
Channel photo updated
Хаюшки! На связи Хана🫶 В связи со сменой владельца я хочу сообщить о том что наш флуд уходит на перезагрузку. Отныне владелец я и все вопросы по поводу вступления, союза и помощи пишите мне в личные сообщения: @iLoveHana1 Спасибо что остаётесь с нами🫶 #РепостСоюз
⛧°。 ⋆༺𝓝𝑒𝑤 𝑈𝑛𝑖𝑜𝑛༻⋆。 °⛧ ──────── ☆⋆。𖦹°‧★ ─────── ⊹ ࣪ ˖𝐼𝑡'𝑠 𝑜𝑛𝑙𝑦 𝑒𝑣𝑒𝑟 𝑦𝑜𝑢, 𝐼 𝑜𝑛𝑙𝑦 𝑡ℎ𝑖𝑛𝑘 𝑜𝑓 𝑦𝑜𝑢 𝐴𝑛𝑑 𝑖𝑓 𝑖𝑡'𝑠 𝑎 𝑏𝑙𝑒𝑠𝑠𝑖𝑛𝑔, 𝐼 𝑤𝑎𝑛𝑡 𝑖𝑡 𝑓𝑜𝑟 𝑦𝑜𝑢 𝐼𝑓 𝐼 𝑚𝑢𝑠𝑡 ℎ𝑎𝑣𝑒 𝑎 𝑓𝑢𝑡𝑢𝑟𝑒, 𝐼 𝑤𝑎𝑛𝑡 𝑖𝑡 𝑤𝑖𝑡ℎ 𝑦𝑜𝑢 𝑆𝑦𝑠𝑡𝑒𝑚 𝑖𝑛 𝑜𝑢𝑟 ℎ𝑒𝑎𝑟𝑡𝑠, 𝑦𝑜𝑢 𝑜𝑛𝑙𝑦 ℎ𝑎𝑑 𝑖𝑡 𝑏𝑒𝑓𝑜𝑟𝑒 𝑌𝑜𝑢 𝑜𝑛𝑙𝑦 𝑜𝑝𝑒𝑛 𝑡ℎ𝑒 𝑤𝑖𝑛𝑑𝑜𝑤, 𝑛𝑒𝑣𝑒𝑟 𝑜𝑝𝑒𝑛 𝑢𝑝 𝑡ℎ𝑒 𝑑𝑜𝑜𝑟 𝐴𝑛𝑑 𝐼 𝑙𝑜𝑣𝑒 𝑦𝑜𝑢, 𝐼 𝑙𝑜𝑣𝑒 𝑦𝑜𝑢, 𝑡𝑜𝑙𝑑 𝑦𝑜𝑢 𝐼 𝑑𝑜₊ ⊹ ──────── ☆⋆。𖦹°‧★ ─────── .𖥔 ݁ ˖𝑢𝑛𝑖𝑜𝑛: https://t.me/fdelmd ⋆·˚ ─*𝑑𝑎𝑡𝑒: 30.07.2026 #NewUnion
Хелоу! На связи Ханаби 🫶 Я сменила юз и решила выйти с Реста Юз был - @HanaAvataris Юз стал - @iLoveHana1 Спасибо что остаётесь с нами) #РепостСоюз
Здравствуйте! На связи Ханаби. Я ухожу на неопределённый срок в рест по личным причинам, просьба насчёт союзов присылать в личные сообщения мне - @HanaAvataris иначе я не смогу репостить информацию. Спасибо за понимание #РепостСоюз
👎1
Здравствуйте! На связи Ханабушка У нас есть некоторые изменения: Поменялись правила и изменился состав админов, также изменилась аватарка Юзы остались те же #РепостСоюз
Showing the 12 most recent of 20 posts we hold for @luminousf1ood. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 4 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.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“ʟᴜᴍɪɴᴏᴜs ɪɴꜰᴏ” (@luminousf1ood), 81 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/luminousf1ood.
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.