Engagement
17 posts held, back to 14 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.
- ERR · 30 days
- 107.7%
- avg views ÷ 68 subscribers
- Avg views / post
- 73.3
- 8 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 9
- of 17 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
9 Aug 2026, 16:47 UTC17 viewsread 10 August 2026 Photo
𝓗ам передали бинго
@serene_bliss
Передаем его ::
https://t.me/meokiflood
https://t.me/miwayakifld
https://t.me/blackoutfl00d
https://t.me/mintrosesfloodinfo
https://t.me/mirl_sinfo
https://t.me/chipsfloodd
https://t.me/greasyyfll
Чистые бинго в коммах ↓
Signed 𐚁ֶָ๋࣭֢
9 Aug 2026, 15:13 UTC22 viewsread 10 August 2026 Sticker
Sticker, posted without a caption
Signed 𐚁ֶָ๋࣭֢
9 Aug 2026, 15:11 UTC21 viewsread 10 August 2026 Forwarded from @serene_blissPhoto
Шипы профилей . . . 🐣
от миллео
Условия :
— сделать репост в свой канал (инфо)
— поставить «+» под постом
— указать аву которую брать
не беру : рж, без авы, совму.
места : 11/20
Signed 𐚁ֶָ๋࣭֢
4 Aug 2026, 20:29 UTC155 viewsread 10 August 2026 в состав Whisper Veil требуются администраторы, желательно админ по нью, админ по этому тгк. все обязанности распишу в лс.
по всем остальным вопросам писать в лс влд @tadaoblouse или @delune67 . ждем любого!
#whisveilrp #сзрп
Signed Tadao Blouse
WhisperVeil Flood — INFO pinned Deleted message
3 Aug 2026, 12:42 UTC60 viewsread 10 August 2026 Forwarded from @greasyyfllPhoto
➖➖➖➖ ➖➖➖➖➖➖
приз - 100 🌟
для участия:
01. рп в свое инфо
02. подписка на наше инфо без дальнейшей отписки
03. скинуть аву и ссылку флуда
— — — — — — — — — — — — — — —
Места 0/???
участвовать могут не только союзы
Signed 𐚁ֶָ๋࣭֢
3 Aug 2026, 09:24 UTC66 viewsread 10 August 2026 Sticker
Sticker, posted without a caption
Signed 𐚁ֶָ๋࣭֢
27 Jul 2026, 11:37 UTC118 viewsread 10 August 2026 Sticker
Sticker, posted without a caption
Signed 𐚁ֶָ๋࣭֢
26 Jul 2026, 21:23 UTC127 viewsread 10 August 2026 Набор открыт. По поводу вступления писать @delune67
Signed 𐚁ֶָ๋࣭֢
15 Dec 2025, 00:48 UTC≈1,380 viewsread 10 August 2026 Photo
. . . 🤩AVIGATION « 🦑 »
01 :: WHISVEIL CHAT || ご飯
‘’ ROLES *-* c; ADMINS’’ 🤩
. . . “~” [🤩]] . . . 雪 — 🤩
. . . RULES & 🫥 クリスマス
ビデオ || our tik tok account :: 02
<🤩> 雪だるま ‘UNION RULES. . .
. . . „DESIGN” LØL ^-•^ 雪だるま 00 🥬 00. . . CLEANING Sea
Signed t’(🦕с;}Ñ0kĽØl
14 Dec 2025, 19:31 UTC≈1,180 viewsread 10 August 2026 . . . DESIGN « 🦑 »
. . . ROLE « 🤍 »
— строчка
14 Dec 2025, 19:24 UTC≈1,120 viewsread 10 August 2026 . . . UNION RULES « 🐬 »
наши правила ::
— в инфо принимаем от 0+ пдп
— делаем сз со всеми фд
— пост с нас / с вас / с обеих сторон
— пост о союзе держим 1-2 дня
и после пересылаем в лайф
— вз подписка 1:1.
— рп с хештегами #сзрп #whisveilrp
— рп пост держим +5 часов
— мы может отказаться от
заключения союза без причины
Разрыв если ::
— если вы конфликтный флуд
— закрытие
— долгий рест
— личная инициатива
…
Showing the 12 most recent of 17 posts we hold for @whisveil. 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 — 722,418 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.
Forward network
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 6 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 10 August 2026 — this
entry's latest reading, not the date you are reading this.
“WhisperVeil Flood — INFO” (@whisveil), 68 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/whisveil.
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.