Engagement
18 posts held, back to 7 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 21.9%
- avg views ÷ 102 subscribers
- Avg views / post
- 22.4
- 16 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 18
- of 18 held
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.
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.
Recent posts
8 Aug 2026, 21:04 UTC11 viewsread 9 August 2026 Forwarded from @sakura_flood01Photo
ЧИСТКА СОЮЗОВ ( знаю, что мы не проводим, но я запуталась, поэтому я вынуждена это сделать)
как отмечаться:
инфо :
след ( если есть доп , его тоже):
пдп :
отметились:
https://t.me/jenlisflood
https://t.me/yamahana_flood
https://t.me/mirael_flood
https://t.me/vellum_flood
https://t.me/lamourame
https://t.me/noemiflood
https://t.me/mulifs
https://t.me/flood_cakes
https://t.me/burmalda_flood67
https://t.me/luckyhubinf…
8 Aug 2026, 11:14 UTC17 viewsread 9 August 2026 Forwarded from @sakura_flood01Photo
А𑀝𑀝𐌏ЦИАЦИИ
Ф𐌡УД𐌏В
ʙᥱдущᥙᥔ : #йеджи
ᴛᥱⲙᥲ : ᥴᥱκρᥱᴛ
𐌿РАВИ𐌡А :
① быᴛь ᴨᴏдᴨиᴄᴀныʍ нᴀ инɸᴏ бᴇɜ дᴀᴧьнᴇйɯᴇй ᴏᴛᴨиᴄᴋи
② ᴩᴨ ʙ инɸᴏ(ᴄᴋᴩин ʙ ᴋᴏʍʍ|ᴄɜ нᴇ ᴏбьяɜᴀᴛᴇᴧьнᴏ)
③ ᴨᴏᴄᴛᴀʙиᴛь ᴩᴇᴀᴋ
④ ᴀʙᴀᴛᴀᴩᴋᴀ и юɜ ʙ ᴋᴏʍʍ
учᴀᴄᴛниᴋи 𝟣/𝟣𝟧
#sakuraрп #сзрп
РЕСТ ВЛД𓍼quᴀliᴛ ⁱⁿ𝖿𝗈 🎶໒꒱ pinned «Дорогие союзы, я беру рест на неделю, хочу немного отдохнуть от рп. Но важные скидывайте мне в лс. После реста я не буду скидывать старые рп, будут только новые. #qualitrp #сзрп»
7 Aug 2026, 21:24 UTC15 viewsread 9 August 2026 Forwarded from @SunFlooodikPhoto
🔤 этσт прекрасный солнҽчный день мы искали сочнσе, красноᥱ и насыщҽнное яблочко так мы и встретились с вαми
🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀
Надеемся на долгое сотрудничество! 🎁
Channel name was changed to «РЕСТ ВЛД𓍼quᴀliᴛ ⁱⁿ𝖿𝗈 🎶໒꒱»
7 Aug 2026, 20:38 UTC181 viewsread 9 August 2026 Дорогие союзы, я беру рест на неделю, хочу немного отдохнуть от рп. Но важные скидывайте мне в лс. После реста я не буду скидывать старые рп, будут только новые.
#qualitrp #сзрп
7 Aug 2026, 20:38 UTC14 viewsread 9 August 2026 Sticker
Sticker, posted without a caption
7 Aug 2026, 20:38 UTC13 viewsread 9 August 2026 Sticker
Sticker, posted without a caption
7 Aug 2026, 20:38 UTC13 viewsread 9 August 2026 Sticker
Sticker, posted without a caption
7 Aug 2026, 20:34 UTC13 viewsread 9 August 2026 Конец
Начало
7 Aug 2026, 20:33 UTC9 viewsread 9 August 2026 Forwarded from @sakura_flood01File
🧊🎀🧊Ищем админов🧊🎀🧊
➿➿➿➿➿➿➿➿➿➿➿➿
⭐️ совладелец: 1/1
⭐️ старший админ: 1/1
⭐️ младший админ: 1/1
⭐️ админ по чату: 0/1
⭐️ админ по нью: 0/1
⭐️ монтажёр: 2/2
➿➿➿➿➿➿➿➿➿➿➿➿
писать — @FFIL53HX @qwewerxxt
#сзрп
7 Aug 2026, 20:33 UTC8 viewsread 9 August 2026 Forwarded from @sakura_flood01File
🧊🎀🧊Ищем нью🧊🎀🧊
➿➿➿➿➿➿➿➿➿➿➿➿
💦... красивых нью в чат
🎇правила
🎇много свободных ролей
🎇связь — @FFIL53HX @qwewerxxt
#сзрп
Showing the 12 most recent of 18 posts we hold for @qualitflood06. 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 — 303,859 of 1,183,361entries 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 7 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 9 August 2026 — this
entry's latest reading, not the date you are reading this.
“РЕСТ ВЛД𓍼quᴀliᴛ ⁱⁿ𝖿𝗈 🎶໒꒱” (@qualitflood06), 102 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/qualitflood06.
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.
