宇辞hosts拦截😍 防人脸 防黑屋 防扫码 防禁网 防高风险 防客户端 防行为检测 支持全火 可搭配DY乱杀 需要联系:@wdrbb666 白嫖请勿扰
👍20
Signed 宇辞(有事留言)

Channel
@ycnb666
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,952subscribers
+699 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004347799781 |
|---|---|
| Type | Channel |
| Usernames | @hynb6886 @ycnb666 |
| Created | 23 July 2026 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 28 |
| On Telegram | t.me/ycnb666 |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 48% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Nov 2026, 15:22 | 1,952 | +15 |
| 10 Nov 2026, 20:46 | 1,937 | +19 |
| 3 Nov 2026, 23:59 | 1,918 | -7 |
| 1 Nov 2026, 07:37 | 1,925 | +75 |
| 29 Oct 2026, 12:07 | 1,850 | -4 |
| 26 Oct 2026, 06:31 | 1,854 | +57 |
| 23 Oct 2026, 00:18 | 1,797 | +13 |
| 20 Oct 2026, 05:46 | 1,784 | +48 |
| 17 Oct 2026, 10:55 | 1,736 | +30 |
| 14 Oct 2026, 11:11 | 1,706 | +31 |
| 11 Oct 2026, 05:21 | 1,675 | +60 |
| 4 Oct 2026, 18:18 | 1,615 | +271 |
| 24 Sept 2026, 23:59 | 1,344 | -26 |
| 16 Sept 2026, 20:18 | 1,370 | -16 |
| 13 Sept 2026, 09:37 | 1,386 | +33 |
| 9 Sept 2026, 02:14 | 1,353 | -63 |
| 4 Sept 2026, 02:38 | 1,416 | -8 |
| 31 Aug 2026, 18:18 | 1,424 | +18 |
| 28 Aug 2026, 16:43 | 1,406 | +36 |
| 25 Aug 2026, 07:16 | 1,370 | first reading |
27 posts held, back to 23 July 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 2 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.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 27 (23 July 2026 – 13 November 2026) |
| Views total | 671 |
| Reactions total | 103 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 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.
Lifetime counters from Telegram’s own channel header, read 13 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
103 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 98.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 101 | 98.1% | |
| 🤣 | 2 | 1.94% |
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 7 of the 27 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 103 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 23 July 2026 to 13 November 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.
Telegram’s own ‘edited’ marker: 0 of 6 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
宇辞hosts拦截😍 防人脸 防黑屋 防扫码 防禁网 防高风险 防客户端 防行为检测 支持全火 可搭配DY乱杀 需要联系:@wdrbb666 白嫖请勿扰
👍20
Signed 宇辞(有事留言)
你们拿去开户吧😏😏😏
👍15
Signed 宇辞(有事留言)
File, posted without a caption
👍15
Signed 宇辞(有事留言)
宇辞官方提卡网:https://qy.71ywl.com/shop/45I2UVDM
👍15🤣2
Signed 宇辞(有事留言)
晚点发自动注入
👍18
Signed 宇辞(有事留言)
宇辞动态拦截.zip
👍18
Signed 宇辞(有事留言)
🌟 小昼互推 接纳各种小频道 请不要删除此信息否则取消互推资格 1. 熬夜 2. 和平78\REX直装官方频道 3. 王者荣耀小土豆直装 4. 七夜改文件官方频道🇨🇳 5. AS cheat MOD 🇨🇳 4\.5 6. RKR直装官方频道 7. 厚焰数据号\(不定期送号\) 8. 李宁公益官方🇨🇳 9. 无缘公益项目频道 10. 秋雨账号 和平账号 其他账号 11. 川少\(免费数据号\) 12. AS 弥海砂脸书主频道 13. 思泪的根据地 14. 右法\-cheat 15. PAS直装主频道 📌 共 71 个频道加入互推 📄 第 1/5 页
进入频道送全国头 进入频道送全国头 进入频道送全国头 进入频道送全国头
反馈
有没有人玩我的世界JAVA 地址是 XZOVO.TOP 长期服已经开一年多了
活动一直在
全网最良心的无限授权号 https://yun.023yjs.com/shop/L2JCXSS9 售后 @wuyuannb 上号器之类的在卡网 网页授权 👉 https://www.wysjh.com/wh/ 👈 无限授权全面升级,无需搭配防冻结 授权号99.9%无问题,大家可以放心购买,所有小黑屋、冻结问题都过滤了🦢🦢 无法授权丢给客服售后 授权系统天天抽风 ‼️请在购买付款时开启录屏‼️ 以下任务领取奖励联系➡️ @zsynb1z 1.在快手搜索数据号 在评论区每个作品评论5次 评论十个作品 带上截图找客服领一个十级以上无限授权号 评论内容:主包女朋友 @hynb6886 2.收快手收剪辑师 登录游戏遇到被禁玩的,自己去手动解一下 https://www.wysjh.com/jw/ 售后完整格式 023开头订单号手动复制发给我 023订单号截图 用文字描述遇到的问题 必须时请发完整录屏 售后联系…
Showing the 12 most recent of 27 posts we hold for @ycnb666. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 48 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. The 16 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
@ycnb666 named 10 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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“宇辞拦截/自动注入官方频道” (@ycnb666), 1,952 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/ycnb666.
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.