18 Jun 2026, 13:18 UTC44 viewsread 13 August 2026
☆Союзы: 🌟🌟🌟🌟🌟🌟🌟🌟 https://t.me/+qiRoVpy7l8Q0OWZi https://t.me/one_flyg09 🌟🌟🌟🌟🌟🌟🌟🌟
Channel
INFO—"FLOOD STILL"
@INFO_FLOOD_STILL
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
4subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003966732171 |
|---|---|
| Type | Channel |
| Username | @INFO_FLOOD_STILL |
| Created | Between 1 April 2026 and 24 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/INFO_FLOOD_STILL |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 05:16 | 4 | no change |
| 11 Aug 2026, 17:16 | 4 | first reading |
Engagement
5 posts held, back to 24 April 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 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 5 posts for this entry, the most recent from 18 June 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 13 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.
Recent posts
16 May 2026, 13:35 UTC72 viewsread 13 August 2026
Норма сообщений: 70 (на данный момент 0) Чистка каждую воскресенье
25 Apr 2026, 08:49 UTC77 viewsread 13 August 2026
ᥲдⲙᥙны: ʙ᧘ᥲдᥱ᧘ᥱц— @STILLXNG (Драгон) Роль: Следит за чатом, общается ^^ ᥴ᧐ʙ᧘ᥲдᥱ᧘ᥱц— @A1anami (Нами) Роль: Следит за чатом (без неё флуда не было) ⲙ᧘. ᥲдⲙᥙн— @Ewekix (Ямато) Роль: делает рекламу, следит за чатом, делает тики токи и ведёт лаиф Старший модератор— @mlqw3sd (Луффи) Роль: делает рекламу флуда ведёт канал лаиф, делает тики токи как и Ямато
24 Apr 2026, 18:40 UTC57 viewsread 13 August 2026
#ROLES ☠️ 𑀝ʙ᧐δ᧐дᥱн – Зᥲняᴛ – 🍗 Бρ᧐нь – 🏴☠️ 𐋏уждᥲᥱⲙᥴя – ✊ . 𝘇 𐰁 ׄ ☠️ ︵ !! 𐌑уᴦᥙʙᥲρы: 𐌑уᴦᥙʙᥲρᥲ 𐌡уɸɸᥙ – 𐋏ᥲⲙᥙ – 🍗 Вᥙнᥴⲙ᧐уκ 𑀝ᥲнджᥙ – 🍗 Р᧐ρ᧐н᧐ᥲ З᧐ρ᧐ – Уᥴ᧐ᥰᥰ – 🍗 Фρᥱнκᥙ – ✊ Р᧐δᥙн – ✊ Կ᧐ᥰᥰᥱρ – 🍗 Джᥙⲙδᥱᥔ – ✊ Бρуκ – ✊ 𐌿ᥙρᥲᴛы ρыжᥱʙ᧐᧘᧐ᥴ᧐ᴦ᧐: Шᥲнκᥴ – Бᥱнн Бᥱκⲙᥲн – Яᥴ᧐ᥰᥰ – 𐌡ᥲκᥙ Ру – 𐌿ᥙρᥲᴛы δᥱ᧘᧐ᥔ δ᧐ρ᧐ды: Эдʙᥲρд 𐋏ьюᴦᥱᥔᴛ – 𐌑ᥲρκ᧐ – 𐌿᧐ρᴛᴦᥲᥴ Эᥔᥴ – Иᤋ᧐ – 𐌿ᥙρᥲᴛы δ᧐᧘ьɯ᧐ᥔ ⲙᥲⲙ᧐чκᥙ: Шᥲρ᧘᧐ᴛᴛᥲ 𐌡ᥙн᧘ᥙн – 𐌺ᥲᴛᥲκуρᥙ – 𐌿…
24 Apr 2026, 18:20 UTC61 viewsread 13 August 2026
𐌿ρᥲʙᥙ᧘ᥲ ᥰ᧐ʙᥱдᥱнᥙя ʙ᧐ ɸ᧘удᥱ ﹋﹋﹋﹋﹋﹋𓍯﹋﹋﹋﹋﹋ #Rules 1 : — Ссора Если начинается ссора и комфорт чата явно понижается то те кто начали ссору получают оба варн( варн 2 дня ) 2 : — Спам сообщениями Никакого спама если есть более четырёх однотипных сообщений то администрация в праве дать ( Мут / варн) 3 : — булинг Осуждения, булинг в сторону участников администрации и ТД запрещено ( варн/ мут) 4 : — Стикеры/фото/ви…
Showing the 5 most recent of 5 posts we hold for @INFO_FLOOD_STILL. 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.
Citation-graph rank
Citation-graph rank — 196,160 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“INFO—"FLOOD STILL"” (@INFO_FLOOD_STILL), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/INFO_FLOOD_STILL.
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.