🍀已售后完毕!客服一直在,持续为您的账号保驾护航🔥 📱TG售后: @DDTYH8
👍2

Channel
@YWHNBT
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Handles named that no longer answer · Cite this entry
8,248subscribers
-2,199 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003568386037 |
|---|---|
| Type | Channel |
| Username | @YWHNBT |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/YWHNBT |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 04:09 | 8,248 | -190 |
| 29 Aug 2026, 01:04 | 8,438 | -125 |
| 26 Aug 2026, 01:02 | 8,563 | -795 |
| 23 Aug 2026, 06:28 | 9,358 | -483 |
| 19 Aug 2026, 20:51 | 9,841 | -91 |
| 16 Aug 2026, 17:36 | 9,932 | -72 |
| 14 Aug 2026, 23:47 | 10,004 | -126 |
| 13 Aug 2026, 13:35 | 10,130 | -10 |
| 12 Aug 2026, 14:45 | 10,140 | +3 |
| 11 Aug 2026, 13:12 | 10,137 | -65 |
| 10 Aug 2026, 12:52 | 10,202 | -52 |
| 9 Aug 2026, 15:33 | 10,254 | +41 |
| 8 Aug 2026, 12:33 | 10,213 | -78 |
| 7 Aug 2026, 11:31 | 10,291 | -141 |
| 6 Aug 2026, 10:51 | 10,432 | -15 |
| 6 Aug 2026, 04:02 | 10,447 | first reading |
211 posts held, back to 4 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 37 pages 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 190 of 202 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 211 (4 August 2026 – 28 August 2026) |
| Views total | 33,182 |
| Reactions total | 1,300 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 16:58 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 1 video 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,220 reactions across 175 posts, in 26 distinct kinds. The most used accounts for 76.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 933 | 76.5% | |
| ❤ | 104 | 8.52% | |
| 🥰 | 46 | 3.77% | |
| 😍 | 44 | 3.61% | |
| 🔥 | 12 | 0.984% | |
| 😘 | 12 | 0.984% | |
| 🏆 | 10 | 0.82% | |
| 💯 | 8 | 0.656% | |
| ❤🔥 | 7 | 0.574% | |
| 👌 | 5 | 0.41% | |
| 😭 | 5 | 0.41% | |
| 🎄 | 4 | 0.328% | |
| 💩 | 4 | 0.328% | |
| 🤩 | 4 | 0.328% | |
| 😢 | 3 | 0.246% | |
| 🤡 | 3 | 0.246% | |
| 🤮 | 3 | 0.246% | |
| 💋 | 2 | 0.164% | |
| 😱 | 2 | 0.164% | |
| 🤣 | 2 | 0.164% | |
| 6 further kinds | 7 | 0.574% |
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 195 of the 211 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,332 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 211 most recent posts we hold, published 4 August 2026 to 28 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.
🍀已售后完毕!客服一直在,持续为您的账号保驾护航🔥 📱TG售后: @DDTYH8
👍2
😂HP不冻结地铁无限授权号已补货😂 🥰100%没有冻结情况 库存不多有需要的兄弟可以入手 🥰卡网链接: https://mall.682fk.cn/shop/L9DKQO9J
👍2
轰炸领20级授权号13663144871
👍2
云鹤数据号【免费数据号】 pinned «📣云鹤数据号官方导航🌈 🎮数据号/无限授权/直登号已补货 🎮无畏契约高质量数据号已补货 🛰️新上架微区去扫码授权号 👑购买高质量数据号卡网点我 😂零成本躺平日赚百对接教程 🫶查看如何申请售后点我前往 👻下载数据号上号器点我前往 🔥每天发送500个数据号点我 🔗做任务白嫖免费授权号点我 🤝数据号售后客服:@DDTYH8»
HP授权地铁号已补货
👍4
Q直登号V扫码号库存已补🌹长期永久使用推荐🔥
👍9
🍀已售后完毕!客服一直在,持续为您的账号保驾护航🔥 📱TG售后: @DDTYH8
👍6💋1😘1
😂HP不冻结地铁无限授权号已补货😂 🥰100%没有冻结情况 库存不多有需要的兄弟可以入手 🥰卡网链接: https://mall.682fk.cn/shop/L9DKQO9J
👍8❤4
🫥全网最高质量瓦手数据号 😙每天都是现货人工直播抓号 🤑不存在二卖圈钱跑路行为 😀😀😀😀😀😀😀😀 账号如有问题请联系卡网客服售后 🥰购买地址 https://mall.682fk.cn/shop/L9DKQO9J
👍7❤2🥰2
Photo, posted without a caption
👍8❤2
太质量了
👍7❤3
牛逼
👍7❤3
Showing the 12 most recent of 211 posts we hold for @YWHNBT. 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.
@YWHNBT edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
有多少人人?
The shares total 105%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
一个人投一票 我看看有多少活人
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 211 most recent posts we hold, published 4 August 2026 to 28 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
Named by 4 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.
@YWHNBT 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“云鹤数据号【免费数据号】” (@YWHNBT), 8,248 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/YWHNBT.
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.