Channel
@WYGwhww
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
555subscribers
+4 since we began measuring on 1 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002494985067 |
|---|---|
| Type | Channel |
| Username | @WYGwhww |
| Created | Between 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 October 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/WYGwhww |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 00:41 | 555 | +4 |
| 1 Oct 2026, 15:22 | 551 | no change |
| 1 Oct 2026, 14:47 | 551 | first reading |
4 posts held, back to 16 February 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.
| Window | Rolling 30 days · latest post in window 12 September 2026 |
|---|---|
| Posts held | 4 (16 February 2026 – 12 September 2026) |
| Views total | 101 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 1 Oct 2026, 15:22 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.
Measured directly from 3 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 of the 4 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 16 February 2026 to 12 September 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.
首开极品大圈 — 冰冰 前凸后翘 极品身材 五官精致 打扮时尚 水嫩肌肤筷子腿腼腆女友害羞脸，女友情绪价值，沉浸式女友体验。 情趣装备齐全 皮肤雪白细腻 顶级身材比例 见课如男友 真实身高➡️净168 体重➡️45KG 年龄➡️04 🐻➡️D➕ 纯天然真实不下锤 叫床一流 一碰就出💦 服务➡️ 🉑👄 🉑🚗 🉑🐍 69🉑🐻 🉑鸳鸯浴🛀 🉑调情 🉑丝袜情趣诱惑😍 主要是:全自动 调情 听话懂事 性欲超级强烈 私密敏感 清秀甜美 叫床声动听 温柔体贴 各种姿势 配合的高 态度及好 待课如男友 友情提示❗️❗️❗️禁止假冒 主打口碑 初次下海 完美约会 所见君所得，定不负君心💗
极品网红气质主播 温婉 （🈲挂社交平台） ▪ 气质谈吐优雅 着装洋气 𝙄 𝙨𝙪𝙛𝙛𝙞𝙘𝙞𝙚𝙣𝙩𝙡𝙮 𝙢𝙖𝙩𝙘𝙝 𝙬𝙞𝙩𝙝 𝙮𝙤𝙪 ‰ 茫茫人海 期待与您邂逅 𝓈𝑜𝓂𝑒𝓉𝒽𝒾𝓃𝑔 ◡̈♥︎ Age/21岁 𝐇𝐞𝐢𝐠𝐡𝐭身高/165cm▪𝐖𝐞𝐢𝐠𝐡𝐭体重/45KG Bust/🐻C 🉑kiss 🉑69🉑口🉑🛁🉑漫游 🉑🚗震S袜情趣自带.性格开放 情绪价值拉满 服务类型 会照顾人好评多多 主动热情、咪咪敏感、一摸就出水.主动温柔. 会夹会吸. 配合度极高. 叫床上动听、 气质出众.谈吐文雅 会打扮、态度好、有耐心、不事逼.待课如初恋！
琪雅 05″ 天然C杯 纯情女大 小甜妹 身高1.68 天然🐻c 🍃双手掌握🍑活好粘人 水多不粘手 🍃甜度严重超标 想被哥哥抱起来doi 🍃女友般体验 只接待素质援助 🉑🐍🉑69🉑口，丝袜情趣自带 🌸待客热情 身体柔软 配合度高💯 🌸不催不事 乖巧听话 🌸实力喜神 好评神 🌼不可错过的女友体验 🌼皮肤白嫩，小蛮腰.水💦多多 🌼性格温柔会聊天，高素质不催不事！ 🌼敏感体质，小哥哥不要错过哦 风格百变 ❍❍❍ 妳想要的样子我都有 ▶▷ 我希望如约而至的不止秋天还有你💌
🔥烟火起，照人间，服务永在线。 感谢大家的支持，[忘忧宫]春节不打烊。 愿我的坚守，能为你的新年增添一份便利与欢喜。 新年快乐，万事胜意！ 👉客服：@wygwer888 （经理李慕碗） 👉双向：@wanerjxr_bot
❤1
Showing the 4 most recent of 4 posts we hold for @WYGwhww. 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.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“武汉外围【忘忧宫】” (@WYGwhww), 555 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/WYGwhww.
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.