29 Dec 2025, 18:39 UTC104 views0 reactionsread 13 August 2026
Админы🥺 🌟овладелец : @kkkkkkkkkk444444
Channel
fucking flood ☠️🩶
@fukingflood
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
4subscribers
+0 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 | -1003405313465 |
|---|---|
| Type | Channel |
| Username | @fukingflood |
| Created | 29 December 2025 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/fukingflood |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 05:02 | 4 | no change |
| 10 Aug 2026, 06:01 | 4 | first reading |
Engagement
7 posts held, back to 29 December 2025 — 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 7 posts for this entry, the most recent from 29 December 2025. 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
29 Dec 2025, 18:28 UTC104 viewsread 13 August 2026
• которые написаны—занятые роли) •Актёры Ли Джун ен Хон Минги Пак Джи хун Пак гу ен Ли хери •Мы все мертвы Пак ми чжин •Игра в кальмара 456 246 •Слабый герой Шиын Сухо • я знаю, но Ю на би •учебная группа Минхван •забронированы—🌟 • насчет свободных обращайтесь к администрации Если сложно определиться с ролью то обязательно пишите администраторам! 🥺
29 Dec 2025, 18:28 UTC84 viewsread 13 August 2026
Норма🌟🌟🌟🌟🌟🌟🌟 🩸 ✨орма для участника в неделю 70 сообщений,если ты не набираешь норму в первый раз-варн,во второй или третий-бан ----------------- 🤩 ✨орма для нью 15 сообщений в неделю,если ты не набрана норма-варн нью освобождаются от нормы в первые 5 дней ------------------ 🤩 ✨орма для рестников 15 сообщений в неделю ( необязательно )
29 Dec 2025, 18:28 UTC78 viewsread 13 August 2026
🤩🤩 🌟🌟🌟🌟🌟 правила флуда, люди соблюдайте плис… 1. Запрещено выкладывать что-либо связанное с 18+, за это бан. 2. Более 5-6 одинаковых сообщений — мут на 30 минут и варн. 3. Нельзя рекламировать что-либо без разрешения влд или совлд, сразу варн. 4. Нельзя добавлять ботов, если вы не админ. 5. Слушаться админов: если сделали замечание — послушать, а не игнорировать; если не понимаете с первой попытки — варн. 6. Де…
29 Dec 2025, 18:27 UTC66 viewsread 13 August 2026
😜😜😜😜😜😜😜😜😜😜😜😜😜😜😜😜😜😜😜😜😜😜 1.норма 70 в неделю,чистки будут проходить по субботам,если вы ньюшка то ваша норма 15 2.если вы набрали 3 варна-бан 3.не актив больше 5 дней-вылет Люди набирайте плиз я не хочу вас терять
29 Dec 2025, 18:27 UTC68 viewsread 13 August 2026
🌟навигации 🌟✨ 🤍🤍🤍🤍 roster rules norma administration
29 Dec 2025, 17:43 UTCviews —
Channel created
Showing the 7 most recent of 7 posts we hold for @fukingflood. 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 — 1,325,249 of 1,350,102entries 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 3 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.
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.
“fucking flood ☠️🩶” (@fukingflood), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/fukingflood.
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.