Channel
@buzzlove_flood
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
170subscribers
+3 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002092028180 |
|---|---|
| Type | Channel |
| Username | @buzzlove_flood |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 27 August 2026 |
| On Telegram | t.me/buzzlove_flood |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 20 Aug 2026, 12:53 | 170 | +2 |
| 14 Aug 2026, 06:58 | 168 | +1 |
| 13 Aug 2026, 00:16 | 167 | first reading |
20 posts held, back to 10 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 page of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 2 of 3 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 20 (10 January 2026 – 11 August 2026) |
| Views total | 268 |
| Reactions total | 43 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 00:16 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
247 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 23.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5357198036416102644 | 59 | 23.9% | |
| custom 5397901248206765167 | 44 | 17.8% | |
| custom 5395821161185577822 | 37 | 15.0% | |
| custom 5395560289166988007 | 27 | 10.9% | |
| custom 5397930664437775036 | 22 | 8.91% | |
| custom 5404356901880236088 | 17 | 6.88% | |
| custom 5379685162328031180 | 15 | 6.07% | |
| custom 5379913014638048970 | 12 | 4.86% | |
| custom 5472027199710192660 | 8 | 3.24% | |
| custom 5397693002422451852 | 6 | 2.43% |
Custom emoji. Every row above is a 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 12 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 247 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 10 January 2026 to 11 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @buzzlove_flood. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 10 January 2026 to 11 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
🌟Набор пока щто закрыт, нас 69, а это уже секс❤️ 🌟Откроем с нью эрой
custom 54720271997101926608custom 53571980364161026446custom 53958211611855778226custom 53979306644377750365
Signed kanibalas
Sticker, posted without a caption
Signed kanibalas
Posted without readable text
custom 53571980364161026445custom 53979306644377750364custom 53958211611855778223custom 53979012482067651673custom 53955602891669880072custom 54043569018802360881
Signed kanibalas
Sticker, posted without a caption
Signed Poyoyo ᵉᶰᵍᵉᶰᵉ
Всем привет, баззлав закрывается как флуд, я ухожу из флуд км Чат будет существовать как общалка без норм, но новых людей мы уже никогда не примем Все старые участники, которые хотят вернуться, вы можете это сделать, написав мне на этот акк: @blame_cupid. Я пущу только людей, в которых буду уверена. Надеюсь, нас запомнят как самый охуенный, активный и интересный флуд с оригинальными идеями и лучшими людьми ❤️ Расп…
custom 535719803641610264413custom 53958211611855778225custom 54043569018802360885custom 53796851623280311803custom 53976930024224518523custom 53955602891669880072custom 53979012482067651672custom 53979306644377750362
Signed ﹙𝟪-𝟩𝟩﹚𖥻𝖬𝖴𝖱𝖠𝖳𝖠 ᵇᵘᶻᶻˡⁱᵏ
Sticker, posted without a caption
Signed ﹙𝟪-𝟩𝟩﹚𖥻𝖬𝖴𝖱𝖠𝖳𝖠
23.02.24 — 23.02.26. 🎀ᴴᴮᴰ ᴮᵁᶻᶻᴸᴼⱽᴱ 𝗅𝗈𝗏𝖾 𝗒𝗈𝗎 𝗆𝗈𝗋𝖾 🌟🎀
custom 53571980364161026448custom 53979012482067651674custom 53979306644377750363custom 53955602891669880072custom 53958211611855778221
Signed ﹙𝟪-𝟩𝟩﹚𖥻𝖬𝖴𝖱𝖠𝖳𝖠
𝘽𝙪𝙯𝙯.𝙇𝙤𝙫𝙚⁸-⁷⁷ᡣ𐭩 pinned Deleted message
🌟🎀 ❛ ⚫️⚫️⚫️⚫️⚫️ .’ ⌕ ་ .’ 🇰🇬 𓍼 🎀🪄🪄🪄🪄🎀 ➿🎀 𝓦 ᥆w ‹ › 𓂃 🎀🎀𓍯 🌟🌟список баззликов, 🌟🌟играющих в разные 🌟🌟мобилки 🌟🌟чтобы вас добавили 🌟🌟в список, писать влд ❤️. кто играет · V ㅤ( 🌟 Роблокс ) 解決 : Соул Сону Мока 🌟 Ни-Ки Фума Хосок Сынкван Стелла Тэмин Чону Джемин Минги Джэхён Тэн Ченлэ Цзяхао & ( 🌟 Бравл старс ) 解決 : Джэхен Сон…
custom 53979012482067651675custom 53799130146380489703custom 53955602891669880073custom 53976930024224518521custom 53979306644377750361
Signed ﹙𝟪-𝟩𝟩﹚𖥻𝖬𝖴𝖱𝖠𝖳𝖠
Sticker, posted without a caption
Signed ﹙𝟪-𝟩𝟩﹚𖥻𝖬𝖴𝖱𝖠𝖳𝖠
😀😀😀😀😀😀 😀😀😀😀😀😀 😀😀😀😀😀😀 😀😀😀😀😀😀 😀😀😀😀😀😀 😀😀😀😀😀😀
custom 53571980364161026447custom 53958211611855778227custom 53979012482067651676custom 53799130146380489703custom 53955602891669880072
Signed ﹙𝟪-𝟩𝟩﹚ 𖥻𝖬𝖴𝖱𝖠𝖳𝖠
File, posted without a caption
custom 53955602891669880074custom 53958211611855778223custom 53979012482067651673custom 53979306644377750362custom 53571980364161026441custom 53796851623280311801custom 53799130146380489701
Signed ﹙𝟪-𝟩𝟩﹚ 𖥻𝖬𝖴𝖱𝖠𝖳𝖠
Showing the 12 most recent of 20 posts we hold for @buzzlove_flood. 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 — 487,708 of 1,629,518 entries 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.
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 20 August 2026 — this entry's latest reading, not the date you are reading this.
“(𝟴-𝟳𝟳) 𝗕𝗨𝗭𝗭.𝗟𝗢𝗩𝗘 𝗙𝗔𝗠𝗜𝗟𝗬” (@buzzlove_flood), 170 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/buzzlove_flood.
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.