Channel
@Hinata_Flood0
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
15subscribers
+6 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004487469624 |
|---|---|
| Type | Channel |
| Username | @Hinata_Flood0 |
| Created | 5 August 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/Hinata_Flood0 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 1 October 2026 and assigned it the closest of 31 fixed categories, at 80% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 20:20 | 15 | -3 |
| 19 Sept 2026, 10:38 | 18 | +3 |
| 1 Sept 2026, 05:18 | 15 | -2 |
| 25 Aug 2026, 01:24 | 17 | +3 |
| 17 Aug 2026, 11:16 | 14 | +5 |
| 12 Aug 2026, 12:47 | 9 | no change |
| 8 Aug 2026, 14:00 | 9 | first reading |
7 posts held, back to 5 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 7 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
9 reactions across 3 posts, in 6 distinct kinds. The most used accounts for 22.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5467604083475001143 | 2 | 22.2% | |
| custom 5467624136677308767 | 2 | 22.2% | |
| custom 5467823887016306160 | 2 | 22.2% | |
| custom 5467586521353735823 | 1 | 11.1% | |
| custom 5469820325254438754 | 1 | 11.1% | |
| 🕊 | 1 | 11.1% |
Custom emoji. 5 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 3 of the 7 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 9 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 5 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.
https://t.me/boost/Hinata_Flood0 ⲧⲟⲗьⲕⲟ ⲉⲥⲗυ ⲃⲁⲙ ⲏⲉ ⲏⲩⲿⲏы эⲧυ ⲅⲟⲗⲟⲥⲁ, ⲡⲣⲟⲅⲟⲗⲟⲥⲩύⲧⲉ ⳅⲁ ⲙⲟύ ⲧⲅⲕ Hinata’s flood ⳡⲧⲟ ⳝы ⲟⲫⲟⲣⲙⲗⲉⲏυⲉ ⲥⲧⲁⲗⲟ ⲉպⲉ ⳝⲟⲗⲉⲉ ⲕⲣⲁⲥυⲃыⲙ💜
custom 54676241366773087672custom 54678238870163061602custom 54676040834750011431custom 54698203252544387541
ᅠ💕 ᅠᅠᅠ ᅠᅠ ᅠ🎀ɐׂᥴׄȶы : 🦋Iruka Umino—14 ⲇⲏⲉύ ᅠ ᅠ ᅠ ᅠ
custom 54675865213537358231
. . .🎀ɗִׄ᧗ιׄꪦׄιׄsȶִׄɾ𑜅ȶִׄιׄ𐐫ꪦׄ 🐾「火の意志」 🎀wꪦׄɐׂɾ : 🐾𝐇𝐢𝐧𝐚𝐭𝐚— @meatinsock 𐌿᧐ ʙᥴᥱⲙ ʙ᧐ᥰρ᧐ᥴᥲⲙ, ᥰρᥱд᧘᧐жᥱнᥙяⲙ, жᥲ᧘᧐δᥲⲙ ᥙ ᥴ᧐ᴛρуднᥙчᥱᥴᴛʙу ᧐δρᥲщᥲᥔᴛᥱᥴь нᥲᥰρяⲙую κ ʙ᧘ᥲдᥱ᧘ьцу ɸ᧘удᥲ. 🐾🎀𑜅ιׄꪦׄ 𑜅ɗִׄ᧗ιׄꪦׄ : ᧐δяᤋᥲнн᧐ᥴᴛᥙ Оᴛʙᴇчᴀᴇᴛ ɜᴀ ᴩᴇᴋᴧᴀʍу и ᴨᴩᴏдʙижᴇниᴇ ɸᴧудᴀ. Пᴩᴏʙᴏдиᴛ нᴀбᴏᴩ нᴏʙых учᴀᴄᴛниᴋᴏʙ. Пᴏʍᴏᴦᴀᴇᴛ нᴏʙичᴋᴀʍ ᴏᴄʙᴏиᴛьᴄя и ʙᴧиᴛьᴄя ʙ ᴋᴏᴧᴧᴇᴋᴛиʙ. 🐾🎀ꪦׄɗִɐׂɾ 𑜅ɗִׄ᧗ιׄꪦׄ : ᧐δяᤋᥲнн᧐ᥴᴛᥙ Сᴧᴇдиᴛ ɜᴀ ᴨᴏᴩядᴋᴏʍ ʙ чᴀᴛᴇ. Кᴏнᴛᴩᴏᴧиᴩуᴇᴛ ᴄᴏбᴧюдᴇниᴇ ᴨᴩᴀʙиᴧ. В…
. . . 🎀ιׄsȶִׄ 𐐫ׄƒ ɾ𐐫ȴɐׂs 🎀 ᤋᥲняᴛ᧐ — 🔗 ᥴʙ᧐δ᧐дн᧐ — — ᥰᥱρᥱд ᴛᥱⲙ κᥲκ ʙᤋяᴛь ρ᧐᧘ь уδᥱдᥙᴛᥱᥴь чᴛ᧐ ᧐нᥲ ᥴʙ᧐δ᧐днᥲ. δρ᧐нь ᧐ᥴущᥱᥴᴛʙ᧘яᥱᴛᥴя чᥱρᥱᤋ ᥲдⲙᥙнᥙᥴᴛρᥲцᥙю . . . 🌟🌟🌟🌟🌟🌟 💕 Наруто Узумаки—🔗 ✦ Саске Учиха—🔗 ✦ Сакура Харуно—🔗 ✦ Какаши Хатаке—🔗 ✦ Сай—🔗 ✦ Ямато ✦ Хината Хьюга—🔗 ✦ Неджи Хьюга ✦ Ханаби Хьюга ✦ Хиаши Хьюга ✦ Хизаши Хьюга ✦ Шикамару Нара ✦ Шикаку Нара ✦ Ино Яманака—🔗 ✦ Иноичи Яманака ✦ Чоджи Акимичи ✦ Чоза Акимичи ✦…
🕊1custom 54676040834750011431
. . . 🎀υִȴɐׂs 🌺 「守」ᥴ᧐δ᧘юдᥲᥔᴛᥱ ᥰρᥲʙᥙ᧘ᥲ ᥙ уʙᥲжᥲᥔᴛᥱ дρуᴦ дρуᴦᥲ. ✨🎀ꪦ𑜅ִ᧗ : [🎁] — Однотипные сообщения, стикеры, GIF-файлы или команды бота, отправленные более 5 раз подряд, считаются спамом. ✨🎀𐐫нɸִꪒׄυִk̼ȶы : [🎁] — Запрещены оскорбления участников и администрации. Относитесь друг к другу уважительно. Если вы заметили нарушение правил, сообщите администрации. ✨18+ : [🎁] — Фото и видео с контентом 18+ разрешены только…
ᅠ. . . 🎀𑜅ׄ𐐷ιׄᧁׄ𑜅ȶִׄιׄ𐐫ꪦׄ 🎀 𐙚˚⊹₊˚⋅⊹₊˚⋅:𐙚˚⊹₊˚⋅⊹₊˚⋅:𐙚˚⊹₊˚⋅⊹₊˚ [💕] — д᧐δρ᧐ ᥰ᧐жᥲ᧘᧐ʙᥲᴛь ʙ ᥙнɸ᧐-κᥲнᥲ᧘ ɸ᧘удᥲ ᥰ᧐ нᥲρуᴛ᧐! ᤋдᥱᥴь ʙы ⲙ᧐жᥱᴛᥱ нᥲᥔᴛᥙ ʙᥴё ᥴᥲⲙ᧐ᥱ ʙᥲжн᧐ᥱ (᧐δяᤋᥲᴛᥱ᧘ьн᧐ д᧘я ᧐ᤋнᥲκ᧐ⲙ᧘ᥱнᥙя!!) 𐙚˚⊹₊˚⋅⊹₊˚⋅:𐙚˚⊹₊˚⋅⊹₊˚⋅:𐙚˚⊹₊˚⋅⊹₊˚ 𝑟𝑢𝑙𝑒𝑠🤩 𝑙𝑖𝑠𝑡 𝑜𝑓 𝑟𝑜𝑙𝑒𝑠 🤩𝑎𝑑𝑚𝑖𝑛𝑖𝑠𝑡𝑟𝑎𝑡𝑖𝑜𝑛 🤩𝑟𝑒𝑠𝑡
Channel created
Showing the 7 most recent of 7 posts we hold for @Hinata_Flood0. 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 1 registered channel — 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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“𝐇𝐢𝐧𝐚𝐭𝐚’𝐬 𝐟𝐥𝐨𝐨𝐝||𝐈𝐍𝐅𝐎” (@Hinata_Flood0), 15 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/Hinata_Flood0.
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.