Channel photo removed
Channel
🔒 Sweet flood | info — S39
@sweetfloodinfov
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
115subscribers
-1 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002238804470 |
|---|---|
| Type | Channel |
| Username | @sweetfloodinfov |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/sweetfloodinfov |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 20:54 | 115 | -1 |
| 13 Aug 2026, 19:49 | 116 | first reading |
Engagement
20 posts held, back to 24 January 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 20 posts for this entry, the most recent from 22 June 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 42s
- Average length
- 21s
Measured directly from 2 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
98 reactions across 10 posts, in 16 distinct kinds. The most used accounts for 16.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5339462926744973781 | 16 | 16.3% | |
| custom 5192830741804767130 | 14 | 14.3% | |
| custom 5848425626586848000 | 13 | 13.3% | |
| custom 5337191623484799364 | 9 | 9.18% | |
| custom 5467877282049719102 | 9 | 9.18% | |
| custom 5845845034141751915 | 8 | 8.16% | |
| custom 5337185554696009190 | 5 | 5.10% | |
| custom 5848009371241422009 | 5 | 5.10% | |
| custom 5339165994180963362 | 4 | 4.08% | |
| custom 5348584118726718040 | 4 | 4.08% | |
| custom 5215283422078978061 | 3 | 3.06% | |
| 😭 | 3 | 3.06% | |
| 💔 | 2 | 2.04% | |
| custom 5210940046206584724 | 1 | 1.02% | |
| custom 5350290204290732646 | 1 | 1.02% | |
| custom 5456611733156157825 | 1 | 1.02% |
Custom emoji. 14 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 areTelegram’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 10 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 98reactions 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 24 January 2026 to 22 June 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
флуд официально закрыт, всем спасибо за этот год и 11 месяцев!!
😭3💔2
Channel name was changed to «🔒 Sweet flood | info — S39»
🔤сем здравствуйте, дорогие зрители нашего инфо! Как думаете, это конец?❤️ 🔤умаю, что нет. Я долго размышляла. Как вы знаете, наш флуд в ресте уже почти месяц, и мне не хочется выходить из него. Я понимаю, что долго этот проект вряд ли протянет, если мы вернёмся сейчас и думаю, вы все того же мнения.🙂 🔤 не буду говорить, что флуд закрывается навсегда, но, как минимум до лета, мы будем на паузе. Принимать новых участ…
custom 584842562658684800010custom 53394629267449737816custom 53391659941809633623custom 54678772820497191023custom 53371855546960091901
Sticker, posted without a caption
🔤.овое видео! ‘’Sweet flood роняют Запад,,🇺🇸 Id: Наша cr: Джису 🤩 это видео заблокировали в тик токе и дали нам за него замечание на аккаунт, поэтому пусть побудет тут
custom 51928307418047671306custom 53394629267449737815custom 54678772820497191024custom 52152834220789780612custom 58480093712414220092custom 53371855546960091901custom 58484256265868480001
🔒 Sweet flood | info — S39 pinned a photo
➿🔤оброго времени суток, подписчики нашего инфо, сегодня у нас был перенабор и вылетело очень много участников, теперь нас очень мало и набор наконец-то открыт. ➿➿➿➿➿➿➿➿➿➿➿ ➿🔤отела бы предложить вступить в наш флуд, тем более сейчас в чате как никогда легко влиться, будем рады вам и вашим друзьям!! ➿🔤о поводу вступления писать: @GIKWAV #сзрп
custom 51928307418047671303custom 53391659941809633621custom 54678772820497191021custom 58480093712414220091custom 58484256265868480001
🔤дравствуйте, сегодня у меня новости для союзников (для кого-то плохие, для кого-то нейтральные). 🔤 сегодняшнего дня наш флуд будет заключать союзы только со знакомыми флудами (с которыми мы находимся в хороших отношениях). Заранее извиняюсь перед союзами, которые попали в список "разрыв", было приятно с вами сотрудничать. ✅🔤аши союзы: ➫atlant ➫phoenix dust ➫flamer ➫suncrise ➫flash mob ➫cute ➫desmal ➫news df ❌🔤азрыв…
custom 53394629267449737813
🤩🤩🤩🤩 🤩🤩🤩🤩🤩🤩 ➿➿➿➿➿➿➿➿➿➿➿ для участия: 🔤подписка на канал без дальнейшей отписки - покинули канал после проигрыша бан навсегда ➿➿➿➿➿➿➿➿➿ 🔤переслать этот пост в инфо флуда 🔤 прислать скрин репоста и аву флуда ➿➿➿➿➿➿➿➿➿➿➿ 3/8. начало: когда наберутся приз 50🤎
🔤егодня у нас прошла чистка и вот итоги: ❌кик: Юн Чона Кан Бит На Юри Ок Чанми Чо Юри Ли Дам Линь Юйцзинь ✅пред: Ли Юми Со Мин Пувин
custom 53371855546960091901custom 53394629267449737811
🎀🎀🎀 🎀🎀🎀🎀🎀 Сегодня два прекрасных флуда заключили союз: 8 февраля 2026 года 🎀Sweet Flood & Cute Flood🎀 💜надеемся на долгую и крепкую дружбу!! ➫Owner Sweet Flood - Юн Джису {@GIKWAV} ➫Owner Cute Flood - Гойя {@wwqexzc}
custom 53394629267449737811custom 54678772820497191021custom 58484256265868480001
Showing the 12 most recent of 20 posts we hold for @sweetfloodinfov. 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 — 736,204 of 1,481,243entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
Names
Channels on the register whose handles appear in this channel's posts.
@cute_floodds · 4433 postsЗАКРЫТ 𝗮𝘁𝗹ant › › IN𝗙𝗢 ( O7 )
@atlantflood · 2892 postsD13 INFØ DESMAL ׁ ׅ ׁ
@desmalflood · 1222 postsл
@flamerflood · 32 posts𝙁𝙇𝘼𝙎𝙃 𝙈𝙊𝘽ᶦᶰᶠᵒ
@flasnMod_flood · 722 postsЗАКРЫТ ˒ 𝗡𝐸𝗪𝐒 𝐷𝐅
@NewsDff · 8592 posts『他』ׅ 𝑪h𝗲𝗿𝗶𝘀𝗵 ۫
@cherishflood1 · 4871 post𝗸𝗶𝗹𝗹𝘀𑄜ׄū𝗹 💚 `𝗸𝟰
@killsoulfloodinfo · 2171 postрест !! 𝓀𝒶𝓃𝓃ℴ𝓊𝓁𝓎 ( 🍨 ) KØ7
@knlflood · 2691 post⋆ 𝙋𝙤𝙨𝙝𝙎𝙩𝙧𝙚𝙚𝙩ᶦᶰᶠᵒ {`𝗣𝟮𝟵']
@lifePoshStreet · 981 postПривет закрыты
@MD1CNE · 2451 postrush haze!.info🌫️/закрыты
@rushhaze · 291 postsheril
@wwqexzc · 141 post
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@sweetfloodinfov named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“🔒 Sweet flood | info — S39” (@sweetfloodinfov), 115 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/sweetfloodinfov.
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.