🔤🔤🔤🔤 全网独一家 ⬇️手机号定位 ⬇️支付宝码反 ⬇️电百 联通 移动反 ❄️补齐身份证/手机号 ❄️个人大头 ❄️真/假地址 🛡手机号反姓名 🛡全国常用号 🛡v反/Q反三件套 🖥刑侦全户 🖥短信轰炸 📱无违规永久思路 🛰️无违规概率永久思路 🖥新增几个功能:ai脱换衣,破解梯子大全,酒店摄像直播,照片人脸扫描,精准模糊猎魔... 点我进入频道获取卡密 点我进入频道获取卡密
👍16
Signed ZEROBOT

Channel
@ZEROPD
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry
76,688subscribers
+1,361 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002986963745 |
|---|---|
| Type | Channel |
| Username | @ZEROPD |
| Created | 17 August 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/ZEROPD |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 01:35 | 76,688 | +29 |
| 1 Sept 2026, 23:05 | 76,659 | +17 |
| 31 Aug 2026, 20:08 | 76,642 | +5 |
| 30 Aug 2026, 17:08 | 76,637 | +72 |
| 29 Aug 2026, 19:24 | 76,565 | +82 |
| 28 Aug 2026, 16:17 | 76,483 | -50 |
| 27 Aug 2026, 18:30 | 76,533 | +43 |
| 26 Aug 2026, 17:45 | 76,490 | +48 |
| 25 Aug 2026, 14:45 | 76,442 | +50 |
| 24 Aug 2026, 14:13 | 76,392 | +18 |
| 22 Aug 2026, 18:26 | 76,374 | +10 |
| 21 Aug 2026, 12:06 | 76,364 | +56 |
| 20 Aug 2026, 12:34 | 76,308 | +47 |
| 19 Aug 2026, 11:35 | 76,261 | +28 |
| 18 Aug 2026, 14:55 | 76,233 | +57 |
| 17 Aug 2026, 17:26 | 76,176 | +860 |
| 16 Aug 2026, 09:07 | 75,316 | +10 |
| 13 Aug 2026, 13:36 | 75,306 | -89 |
| 12 Aug 2026, 11:05 | 75,395 | -10 |
| 11 Aug 2026, 09:04 | 75,405 | first reading |
299 posts held, back to 17 August 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 54 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 291 of 292 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 1 September 2026 |
|---|---|
| Posts held | 299 (17 August 2025 – 1 September 2026) |
| Views total | 215,503 |
| Reactions total | 4,934 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 1 Sept 2026, 15:03 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 46 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.
5,793 reactions across 297 posts, in 27 distinct kinds. The most used accounts for 81.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 4,711 | 81.3% | |
| ❤ | 448 | 7.73% | |
| 👎 | 119 | 2.05% | |
| 🤔 | 117 | 2.02% | |
| 🤓 | 56 | 0.967% | |
| 🤬 | 54 | 0.932% | |
| 👏 | 38 | 0.656% | |
| 🖕 | 35 | 0.604% | |
| 🌭 | 33 | 0.57% | |
| 🔥 | 27 | 0.466% | |
| 🥰 | 22 | 0.38% | |
| 💩 | 20 | 0.345% | |
| 🤡 | 20 | 0.345% | |
| 😱 | 19 | 0.328% | |
| 😨 | 17 | 0.293% | |
| 😍 | 11 | 0.19% | |
| 😡 | 10 | 0.173% | |
| 😭 | 9 | 0.155% | |
| 🍌 | 5 | 0.086% | |
| 😁 | 5 | 0.086% | |
| 7 further kinds | 17 | 0.293% |
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 297 of the 299 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 5,793 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 299 most recent posts we hold, published 17 August 2025 to 1 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.
🔤🔤🔤🔤 全网独一家 ⬇️手机号定位 ⬇️支付宝码反 ⬇️电百 联通 移动反 ❄️补齐身份证/手机号 ❄️个人大头 ❄️真/假地址 🛡手机号反姓名 🛡全国常用号 🛡v反/Q反三件套 🖥刑侦全户 🖥短信轰炸 📱无违规永久思路 🛰️无违规概率永久思路 🖥新增几个功能:ai脱换衣,破解梯子大全,酒店摄像直播,照片人脸扫描,精准模糊猎魔... 点我进入频道获取卡密 点我进入频道获取卡密
👍16
Signed ZEROBOT
📱⚠️主推开柯基账户购买😂 📩💵✔️购买网址✔️📩💵 https://aoa.aacu.cn/shop/V5YPKDEA 官网频道 @WGSJH888 秒回售后在线客服 @WGSJH520 👇上号器+上号视频之类的👇 https://wwass.lanzoub.com/iE9qi3qm0v3g
👍20
Signed ZEROBOT
😀今天我整合了挂圈各大热门频道! 以下频道是挂圈热门频道大合集 库洛米公益频道 enen内核频道 林羽内核频道 小雪内核频道 狗头公益破解频道 光头强工艺内核频道 雪花工艺内核频道 TP工艺内核频道 葫芦娃工艺频道 互推日进500+参与联系负责人 @didb431 全网收广告位出的直接私信我 ------------------------------------- 点我一键加入全部频道 点我一键加入全部频道 点我一键加入全部频道
👍16
Signed ZEROBOT
新鲜出炉 护航仔9/1日玩家反馈图 ⭐三角洲国服—护航仔⭐ ❤️ 支持设备:安卓 ROOT ❤️ 支持内核:5.x - 6.x 全系 ❤️支持天机/骁龙 处理器 ❤️支持区服:国服 功能说明🎚 ✅方框 ✅骨骼 ✅干员 ✅血量 ✅距离 ✅手持 ✅头甲 ✅物资 🟢大地图雷达/小地图雷达 🟢全图模型漏打/掩体变色 ✅自瞄配置:陀螺仪自瞄+触摸自瞄 ✅购买地址 下载 解绑地址 ❤️独家纯算法解密/独家驱动 ❤️护航仔打单俱乐部 纯算法解密不动内存,欢迎大牛验包打假 官方承诺 封禁十年:退款 无法使用:退款 描述不符:退款 收代理 批卡联系客服 接合作 🌟🙃🌟➡️ @xuehuabox 交流群:https://t.me/hhzjlq
👍6
Signed ZEROBOT
❤️三角洲算法解密UDP解包内核 可以无视三角洲加密坐标更新 通过解析网络数据包提取玩家数据坐标 ,无需配置任何参数 可过全部查桂机构,隐私与安全性里面的开发者数据包也无法读取到任何获取痕迹全程0写入 不动任何游戏数据! 更新日志 1.优化性能占用 2.适配安卓17,修复低版本安卓系统启动失败 卡网下单: https://luoye.yjsfk.cn/shop/V8ACPC1H 客服售后: https://t.me/jjbnkl ✅ 内核陀螺仪+漏打自瞄随意裸奔 ✅ 内核模型/掩体变色+自研驱动 ✅ 内置云更新,游戏更新最快跟进 超低内存占用,稳定运行,欢迎体验 ❤️➡️频道: @dujnh 免root解包3d模型网页雷达下载点我
👍6
Signed ZEROBOT
❗️❗️❗️❗️❤️三角洲行动 T1纯算法解密强悍上市 🌸顶尖内部独家思路 完美算法解密 😙无视版本更新 备用算法版本储备 一套更比一套强 ⚡️ 适配新赛季 无视赛季加密 ⚡️工作室专用 护航专用 内部项目 👉T1三角洲行动支持国服 👉全天开放交流群 欢迎进来看看 24小时客服在线售后 ✅ 不闪框 ✅不偏框 ✅不漏人 💙人物/物资绘制 💙内核自瞄/模型漏打 🛜大/小地图雷达 ⚙顶级菜单/丝滑自瞄 🔨物资过滤🔨密码门显示🔨骨骼漏打 收代理 批卡联系客服 合作 ❗️❗️➡️点击进入官方频道 ❗️❗️➡️点击进入官方聊天频道
👍10❤1
Signed ZEROBOT
😂菠萝全网最低价数据号😂 👍和平/三角洲/瓦/香肠派对👍 🍍全网售后最好且质量数据号🍍 🔥全网最低价只为做口碑不多赚一分钱🔥 ✅价格低 质量高 售后快 永不跑路✅ ✅人工验号保障账号质量100%✅ 不为多赚利润只为客户玩的稳定用着放心 用着安心只为长久口碑·稳定可靠HP游戏号样式多 ⭐菠萝数据号购买链接⭐: https://wkaiw.oqzgb.com/shop/BLSJH 😙购买账号时请点开录屏😙 ✈️菠萝数据号官方通知频道: https://t.me/菠萝数据号 https://t.me/菠萝数据号 https://t.me/菠萝数据号 ✔️所有账号全部包售后✔️ ‼️一定要有全程录屏没有全程录屏否则无售后‼️ ✅唯一售后客服 @BLKF886 ✅
👍14
Signed ZEROBOT
🚀 New Update #Game和平 Game和平 Update: ✔️修复绘制闪烁卡顿问题,创建屏幕镜像掉帧问题,安卓17适配问题 此版本为临时测试版 有问题反馈至评论 公益卡密:@luoyenb521 更新网盘: https://wwbll.lanzoul.com/b0188jmrwj 密码:6666 tips:可以一键获取配置,还有一些其他的可玩性功能你们可以自行研究如迫击炮落点 落叶数据号 luoye.yjsfk.cn/shop/luoye 频道 @luoyenb521
👍8❤2
Signed ZEROBOT
统一更新:❤️三角洲,🎮和平精英,🎮无畏契约,🎮PUBG统一APP启动 本程序永久公益免费,禁止任何人,任何平台,私下倒卖此程序进行盈利 仅供参考交流学习,禁止在中国大陆内传播本程序 目前葫芦娃已适配PUBG4.5🎮最新四服,和平精英🎮,无畏契约🎮,三角洲❤️四款游戏,网页雷达共享,软件雷达共享都已公益免费使用,卡密随便输入,以及免root模型AI吸附自瞄 山东省用户禁止安装,省得被打电话,给叔叔找麻烦 葫芦娃频道 @HLWNHNB 聊天群 @hulwjlq
👍9❤1
Signed ZEROBOT
库洛米 V15 更新内容如下(展开查看): 1.修复本地模型以及漏打没有效果,已适配加载全部模型 2.修复自瞄不准,优化自瞄以及压枪算法,ai 自适应所有枪械倍镜配件,无需自己调节 3.优化漏打算法、优化自瞄算法 4.优化 CPU 占用,优化模型占用,开了和没开一样,特别流畅 5.修复物资所有问题 6.修复部分用户登录不上问题 7.修复部分设备三方问题 8.修复部分安卓 17 无法打开悬浮窗 9.修复解密 3 部分人时有时无 10.修复陀螺仪存在的问题 库洛米 V15 版本是发布以来最强大的版本,是最流畅、最稳定、自瞄漏打最好用的版本 解密算法以及驱动接口全部重构,比公益稳几个版本,防止特征 🤩点我查看v15版本自瞄丝滑操作 提卡链接🔗: https://luoye.yjsfk.cn/shop/kuluomi886 🌟🙃🌟➡️ @kuluomi886 ✅卡密点我解绑 ✅代理批卡点我
👍10👎2
Signed ZEROBOT
Like解密项目 8月29日最新版 欢迎来拆包真实我打假我 ❗️❗️❗️❗️❗️❗️ 纯算法解密,全机型适配解密,不闪框不漏人不遁地 可以无视三角洲加密坐标更新 通过解析网络数据包提取玩家数据坐标 ,无需配置任何参数 可过全部查桂机构,隐私与安全性里面的开发者数据包也无法读取到任何获取痕迹全程0写入 不动任何游戏数据! ✅AI自动压枪(识别图层+传感器调整,比自瞄更好演戏) ✅内核陀螺仪+漏打自瞄随意裸奔 ✅内核模型/掩体变色+自研驱动 ✅网页雷达+局域网雷达双端协同 ✅ 内置云更新,游戏更新最快跟进 超低内存占用,稳定运行,欢迎体验 解密支持 udp/纯算法版本⭐ 提卡地址 http://154.8.211.40 反馈批卡联系 @linki520 官方频道 @Likenb667 交流群 @Likenb789
👍18😱1
Signed ZEROBOT
⭐三角洲国服—护航仔⭐ ❤️ 支持设备:安卓 ROOT ❤️ 支持内核:5.x - 6.x 全系 ❤️支持天机/骁龙 处理器 ❤️支持区服:国服 功能说明🎚 ✅方框 ✅骨骼 ✅干员 ✅血量 ✅距离 ✅手持 ✅头甲 ✅物资 🟢大地图雷达/小地图雷达 🟢全图模型漏打/掩体变色 ✅自瞄配置:陀螺仪自瞄+触摸自瞄 ✅购买地址 下载 解绑地址 ❤️独家纯算法解密/独家驱动 ❤️护航仔打单俱乐部 纯算法解密不动内存,欢迎大牛验包打假 官方承诺 封禁十年:退款 无法使用:退款 描述不符:退款 收代理 批卡联系客服 接合作 🌟🙃🌟➡️ @xuehuabox 交流群:https://t.me/hhzjlq
👍18😱1
Signed ZEROBOT
Showing the 12 most recent of 299 posts we hold for @ZEROPD. 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 — 97,278 of 1,629,808 entries 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.
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 8 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.
@ZEROPD 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.
10 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“ZERO公益频道” (@ZEROPD), 76,688 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/ZEROPD.
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.