装载机测试完毕携带神秘功能即将更新
❤2😍1
Signed 制裁

Channel
@DYZZNB
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
182,416subscribers
+225 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1002152037846 |
|---|---|
| Type | Channel |
| Username | @DYZZNB |
| Description | 唯一正版频道,其他都是假冒 ------------------------------ 关联频道: @HP02MH @DYFK88 |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/DYZZNB |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 78% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 05:24 | 182,416 | +43 |
| 12 Aug 2026, 01:53 | 182,373 | +106 |
| 10 Aug 2026, 23:05 | 182,267 | +88 |
| 9 Aug 2026, 21:52 | 182,179 | -14 |
| 8 Aug 2026, 20:28 | 182,193 | -22 |
| 7 Aug 2026, 22:17 | 182,215 | +24 |
| 7 Aug 2026, 14:03 | 182,191 | first reading |
39 posts held, back to 2 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 19 pagesof 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 August 2026 |
|---|---|
| Posts held | 39 (2 August 2026 – 13 August 2026) |
| Views total | 298,090 |
| Reactions total | 2,173 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 19:23 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 August 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.
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.
2,173 reactions across 39 posts, in 14 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,450 | 66.7% | |
| ❤ | 366 | 16.8% | |
| 🍌 | 123 | 5.66% | |
| 😍 | 72 | 3.31% | |
| 🤓 | 50 | 2.30% | |
| 😱 | 31 | 1.43% | |
| 🔥 | 27 | 1.24% | |
| 🤩 | 17 | 0.782% | |
| 🥰 | 14 | 0.644% | |
| 🙈 | 8 | 0.368% | |
| 👏 | 6 | 0.276% | |
| 😘 | 5 | 0.23% | |
| 🎉 | 3 | 0.138% | |
| 🥴 | 1 | 0.046% |
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 39 of the 39 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 2,173reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 39 most recent posts we hold, published 2 August 2026 to 13 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.
装载机测试完毕携带神秘功能即将更新
❤2😍1
Signed 制裁
即将更新所有注入/装载机
👍71😍7❤3🍌3
Signed 制裁
✅冰澜高质量数据号授权号源头✅ 🥇全网唯一100%不冻结无限授权1️⃣ 📣无限授权号正式回归📣 ✔️老品牌高信誉秒售后✔️ 😃😃一手号商/无限授权源头 😃😃不鉴别、不人脸、不冻结 🔥和平精英数据号已补货 🔥王者荣耀数据号已补货 🔥火影忍者数据号已补货 🔥失控进化直登号已补货 👑所有账号问题都包售后✅ 👍👍👍购买链接: https://shop.lffm.cn/shop/3Q29LRL8 https://shop.lffm.cn/shop/3Q29LRL8 https://shop.lffm.cn/shop/3Q29LRL8 ✔️授权地址: auth.prolua.pro ❤️冰澜官方通知频道:@BLNBMB888 咱们的数据号都是人工验号无异常上架卡网的 ✅一手货源✅三年老店✅售后质保 我们的优点:✅诚信✅低价✅质量✅便宜✅好用✅服务好✅售后好 🐼专为学生党打造放心购买 😀😀😀😀😀😀 🧦👍客服联系:@SHNBMB888
👍36❤1🍌1😱1
✔️橘子高质量无限授权源头自营✔️ ➡️😃😃退游号😃😃退游号 ➡️😃😃😃😃 源头直营最低价格 ➡️😃😃不鉴别、无人脸、不冻结 🥇一年诚信经营,三年售后兜底 ❗️请在购买付款时开启录屏❗️ 😙😍😗😋😝🙃😜🤨😜 👍👍购买链接:https://new.818fka.com/shop/SQSZN ✅无限授权网址:http://154.36.166.77/ 🤩备用无限授权网址:https://juzi.20i7.com/ 😐上号器下载: https://wwazi.lanzoue.com/b00hrxm2ve ❤️橘子官方频道: @SQSZN ✅所有账号问题都包售后✅ ✅无限授权最低1块钱✅ 👑全新自动去鉴别上号器👑 🔥一手号商、无敌售后😁 😙【全网最低价不信你来看看】 AX授权号源头无冻结,无鉴权全网最低价 📣点我免费领取数据号/授权号 😀😀😀😀😀😀 🔥全天在线客服联系:@lbsjh69 进入每周免费发放100+数…
👍42❤5🔥2🥰1
✅劳模高质量无限授权源头自营✔️ ➡️😃😃退游号😃😃退游号 ➡️😃😃😃😃 源头直营最低价格 ➡️😃😃不鉴别、无人脸、不冻结 🥇一年诚信经营,三年售后兜底 😙😍😗😋😝🙃😜🤨😜 👍👍购买链接: lm.ioens.cn 🔗卡网: https://fkli.cc/9Ma 🔗卡网: https://luoye.chyidc.cn/shop/RY9XESV1 😐上号器下载/使用教程: https://www.ilanzou.com/s/sndXEyyn 🔥劳模官方频道: @lm2239 ✅所有账号问题都包售后✅ 👑全新自动去鉴别上号器👑 🔥一手号商、无敌售后😁 ✨点我免费领取数据号/授权号 😀😀😀😀😀😀 🔥全天在线客服联系:@lm8882 月广到期时间9.14
👍36❤4😱1
落叶公益内核回归更新新频道功能齐全自瞄打火箭都没问题 加入频道 https://t.me/luoyenb521 😀😃😀点击此处跳转落叶官方指定卡网 周广到期时间8.20
👍41❤3
🌈DY数据号自营官方唯一店铺 高等级授权号 直等号 地铁刷刀号 自行开发的授权号包质量 HP授权号全网超低价格兄弟们 快点冲数量有限,高质量秒售后 从付款页面带着录屏证明号有问题找售后秒补,没有任何争议,100%售后不会圈 不会骗,目前市场真正做到售后的很少很少,基本都是圈钱跑路骗你再买第二个号 😂目前低价精品大促销😂 🌟官方卡网点我跳转🌟
👍29❤5🍌1
🎮虫二数据号【质量】🙈 售后24小时在线 (服务拉满!) 主营:『和平Q安卓数据号』『和平Q无限授权号』 🔗24小时自助下单链接🔗 ‼️请在购买付款时开启录屏‼️ 👍👍👍1号购买链接(优先购买这个卡网全网高质皮肤多): https://new.kxtrl.cn/shop/C3CRL50Y 👍👍👍2号卡网购买链接: https://fh10.zmfaka.cn/shop/18DHL2WP 【全网最低价不信你来看看】 🤘售后范围登录失败5✅ 设备脸✅ 鉴权失败✅封号十年✅ 炸弹脸✅ 安全隔离期✅禁网✅ ⭐保证大家买到的就是商品描述的那样 ‼️二卖出门被车撞死‼️ ‼️圈钱出门被车撞死‼️ 🌈一号链接没库存请去二号链接购买! 🛫客服 @pmnb2 点击进入频道领取免费数据号 点击进入频道领取免费数据号 点击进入频道领取免费数据号 点击进入频道领取免费数据号 月广到期时间9.13
👍38❤5🍌1🎉1🔥1
Sticker, posted without a caption
👍136🍌67😍30❤14😱12🤓6🤩4🎉1
Signed YOU游
服务器更换完成
👍124🍌13❤11🔥7
🌟1.37.11 02公益裸奔美化 公益卡密: 随便输入 兼容: ROOT✔️ 虚拟机✔️ 版本: 版本 v19.0 配置: 自定义配置 ------------------------------------------ [功能介绍] 播报美化 计数器美化 自定义LOGO美化 载具美化 投掷物美化 手持特效 爆炸特效 双生切换 适配所有枪械美化 播报美化 检视美化 适配所有皮肤美化 经典模式✓ 地铁模式✓ ------------------------------------------ [更新内容] 1.修复闪退问题 2.兼容与DY追踪一起使用(需要先启动dy追踪) 3.重构部分内容 ⚠️注意事项:配置文件.cfg必须更换压缩包最新版 ------------------------------------------ 你们的宣传是对我们的最大支持!!! 本项目由DY追踪代理更新 美化通知频道:@HP02MH …
👍52❤30🤩11🍌4🥰2
👉星巴克授权号【全网价格最低】😫 👑授权号,直登号源头❤️ 🤬 全网首发HP/PRO无限授权🤬 ‼️不冻结‼️不冻结‼️ 不冻结‼️ 🎮【各种极品授权号低至1元】🎮 99%都是高质量皮肤套装 100%不鉴别/不人脸/不封号 每个账号包首次登录所有问题 ✅介绍:和平直登号/数据号/授权号 ‼️下单前请打开录屏‼️ ♥️24小时自助提卡网: https://fh10.zmfaka.cn/shop/pdx 👍唯一售后客服 @xbk00123 🤝 📱唯一频道: @XBKSJH6 🔥进入每天免费发放1000+数据号频道 🔥进入每天免费发放1000+数据号频道 🌈点我免费领取数据号 价格😃😃最低,不低随便喷😃😀😀 ⚠️二卖出门被车撞死⚠️ ⚠️跑路出门被车撞死⚠️ 📱数据号通知频道【务必加入】 https://t.me/XBKSJH6 月广补发
👍25❤13😍2🍌1🔥1🥰1
Showing the 12 most recent of 39 posts we hold for @DYZZNB. 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 — 261,385 of 1,176,251entries 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.
Named by 3 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“DY追踪通知频道” (@DYZZNB), 182,416 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/DYZZNB.
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.