和平雷达无法连接可以卸载重装试试
👍32

Channel
@yuenhpdd
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
16,159subscribers
+15,840 since we began measuring on 28 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1004449132819 |
|---|---|
| Type | Channel |
| Username | @yuenhpdd |
| Created | 28 September 2026 — measured — dated from the channel’s first post |
| First recorded | 28 September 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/yuenhpdd |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 2026 and assigned it the closest of 31 fixed categories, at 91% 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 |
|---|---|---|
| 14 Nov 2026, 10:49 | 16,159 | +2,744 |
| 11 Nov 2026, 11:11 | 13,415 | +993 |
| 9 Nov 2026, 13:07 | 12,422 | +536 |
| 8 Nov 2026, 02:59 | 11,886 | -24 |
| 6 Nov 2026, 20:21 | 11,910 | -19 |
| 5 Nov 2026, 17:19 | 11,929 | +11 |
| 4 Nov 2026, 19:31 | 11,918 | -4 |
| 3 Nov 2026, 20:08 | 11,922 | -18 |
| 1 Nov 2026, 14:55 | 11,940 | -1 |
| 31 Oct 2026, 15:54 | 11,941 | +8 |
| 30 Oct 2026, 18:09 | 11,933 | -3 |
| 29 Oct 2026, 16:28 | 11,936 | +5 |
| 28 Oct 2026, 17:11 | 11,931 | +3 |
| 27 Oct 2026, 14:05 | 11,928 | +18 |
| 26 Oct 2026, 13:40 | 11,910 | +38 |
| 25 Oct 2026, 13:34 | 11,872 | +213 |
| 24 Oct 2026, 14:06 | 11,659 | +374 |
| 23 Oct 2026, 11:44 | 11,285 | +331 |
| 22 Oct 2026, 09:06 | 10,954 | +315 |
| 21 Oct 2026, 01:06 | 10,639 | first reading |
50 posts held, back to 28 September 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 25 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 14 November 2026 |
|---|---|
| Posts held | 50 (28 September 2026 – 14 November 2026) |
| Views total | 575,684 |
| Reactions total | 3,146 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 20:49 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 14 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.
3,177 reactions across 48 posts, in 16 distinct kinds. The most used accounts for 87.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2,774 | 87.3% | |
| ❤ | 259 | 8.15% | |
| 🤔 | 37 | 1.16% | |
| 🤮 | 24 | 0.755% | |
| 🍌 | 11 | 0.346% | |
| 🤗 | 11 | 0.346% | |
| 🤩 | 11 | 0.346% | |
| 🐳 | 10 | 0.315% | |
| 🥴 | 8 | 0.252% | |
| 🕊 | 7 | 0.22% | |
| 🔥 | 6 | 0.189% | |
| ❤🔥 | 5 | 0.157% | |
| 🌭 | 5 | 0.157% | |
| 💯 | 4 | 0.126% | |
| 🦄 | 3 | 0.094% | |
| 🤓 | 2 | 0.063% |
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 48 of the 50 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 3,177 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 50 most recent posts we hold, published 28 September 2026 to 14 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: 17 of 46 posts held from the last 30 days (37.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).
和平雷达无法连接可以卸载重装试试
👍32
🎮和平精英公益免root网页雷达 纯网络路由读取坐标100%不封号无视行为1,3,7各种封号 ✔️手机端只需要安装一个加速器即可,不需要电脑,不需要开热点,不需要root权限,纯网络读取 ✔️支持安卓,鸿蒙全系统,只要你的设备可以正常联网即可(网络获取坐标),不需root权限,不需要电脑,不需要解bl,手机联网即可绘制 ✅高级物资,人物职业,头甲包,名字信息,血量状态,全部可以显示,效果堪比内核,并且比内核更加稳定 本地内核绘制全部信息都要在本地游戏内存里面读取,非常容易封号封一天或者三天,甚至十年,而我们所有坐标都是在网络中获取 目前程序完全免费,卡密随便输入即可 ✔️更新内容 适配超体模式 团队竞技的图书馆和仓库 适配大部分主题活动场景人物信息解析 新增悬浮小地图雷达功能 可以直接在连接服务器的设备上看到实时雷达 有问题可反馈至 评论区 最好带上相关截图或者视频 房间号 具体的问题内容和时间 公益雷达频道: h…
👍36
云更新 修复天机处理器无法使用模拟执行解密的问题
👍106❤2
三角洲❤️公益算法解密内核 🎮真正的算法解密,不动任何内存,绝对安全的程序 📲APP启动器不依赖mt管理器,完美规避终端检测 ✅物资显示,过滤高价值物资,精确寻包 🐱人物骨骼,射线,头甲显示 完全公益免费,卡密随便输入即可 全网真正的三角洲公益算法解密,不收取任何费用,无任何套路 ✨更新时间:2026年11月23日 ✅栖月 Kernel公益运营团队 栖月频道: https://t.me/yuenhpdd 有问题的手动下载不要覆盖安装
👍115❤13🤔2
栖月内核服务器已恢复,重启APP即可正常使用
👍112❤2
更新服务器已恢复,重启APP即可正常更新使用
👍86🐳2🔥1🤔1
三角洲❤️公益算法解密内核 🎮真正的算法解密,不动任何内存,绝对安全的程序 📲APP启动器不依赖mt管理器,完美规避终端检测 ✅物资显示,过滤高价值物资,精确寻包 🐱人物骨骼,射线,头甲显示 完全公益免费,卡密随便输入即可 全网真正的三角洲公益算法解密,不收取任何费用,无任何套路 ✨更新时间:2026年11月23日 ✅栖月 Kernel公益运营团队 栖月频道: https://t.me/yuenhpdd 有问题的手动下载不要覆盖安装
👍95❤6
云更新 修复root超时
👍86🤔3💯1
派发UDP大厅开启 其他解密均局内开启
👍109❤3🤔1
云更新 更新两个模拟解密 更新猪猪侠驱动 两个模拟仅限猪猪侠驱动 请重启刷新驱动
👍113❤6
三角洲子弹追踪 美化 是危险功能,不建议大号使用,小号娱乐可以 这两个功能都是动内存的,其他功能不会动内存,解密也不会动内存
👍74❤12
三角洲公益使用教程 1.派发密钥UDP解密需要大厅开启进入游戏 整局不关闭使用 2.模拟执行解密 模拟执行UDP解密仅限猪猪侠驱动使用 其他驱动无法使用 2.内存表UDP解密 无法全适配 简单来说 猪猪侠驱动可以使用模拟执行解密和模拟执行UDP解密 其他驱动可以使用派发密钥UDP解密 但是要大厅开启
👍71❤12
Showing the 12 most recent of 50 posts we hold for @yuenhpdd. 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.
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 31 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 24 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.
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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“栖月公益内核” (@yuenhpdd), 16,159 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/yuenhpdd.
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.