通知📢:免ROOT雷达补了50张天卡 为了保证服务器稳定性 不定时补卡 最近盗卡偷卡的人很多 各位在填联系方式和密码的时候最好设置的复杂一点 天气转凉注意保暖
👍95❤10🥰3

Channel
@FuzzPD
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
31,448subscribers
+26,299 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1004303764152 |
|---|---|
| Type | Channel |
| Username | @FuzzPD |
| Created | 25 July 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/FuzzPD |
Hacking & security — 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 12 August 2026 and assigned it the closest of 31 fixed categories, at 34% 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 |
|---|---|---|
| 11 Nov 2026, 18:27 | 31,448 | +111 |
| 9 Nov 2026, 19:57 | 31,337 | +133 |
| 8 Nov 2026, 09:48 | 31,204 | +53 |
| 7 Nov 2026, 04:48 | 31,151 | +30 |
| 6 Nov 2026, 07:36 | 31,121 | +47 |
| 5 Nov 2026, 03:36 | 31,074 | +12 |
| 4 Nov 2026, 04:09 | 31,062 | +25 |
| 3 Nov 2026, 01:40 | 31,037 | +38 |
| 2 Nov 2026, 01:11 | 30,999 | +65 |
| 1 Nov 2026, 01:47 | 30,934 | +117 |
| 31 Oct 2026, 04:20 | 30,817 | +99 |
| 30 Oct 2026, 07:19 | 30,718 | +47 |
| 29 Oct 2026, 05:46 | 30,671 | +48 |
| 28 Oct 2026, 06:37 | 30,623 | +68 |
| 27 Oct 2026, 09:27 | 30,555 | +73 |
| 26 Oct 2026, 12:28 | 30,482 | +39 |
| 25 Oct 2026, 16:00 | 30,443 | +144 |
| 24 Oct 2026, 18:31 | 30,299 | +173 |
| 23 Oct 2026, 21:19 | 30,126 | +140 |
| 22 Oct 2026, 20:40 | 29,986 | first reading |
110 posts held, back to 25 July 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 134 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 10 November 2026 |
|---|---|
| Posts held | 110 (25 July 2026 – 10 November 2026) |
| Views total | 259,722 |
| Reactions total | 3,750 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 11:08 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.
9,500 reactions across 109 posts, in 12 distinct kinds. The most used accounts for 66.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 6,343 | 66.8% | |
| ❤ | 1,958 | 20.6% | |
| custom 5427355030116133014 | 367 | 3.86% | |
| custom 5280757505561992066 | 283 | 2.98% | |
| custom 5260565507093849701 | 149 | 1.57% | |
| 🙏 | 135 | 1.42% | |
| 😁 | 109 | 1.15% | |
| 🥰 | 40 | 0.421% | |
| 👏 | 33 | 0.347% | |
| 🔥 | 30 | 0.316% | |
| 🎉 | 28 | 0.295% | |
| 👌 | 25 | 0.263% |
Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 109 of the 110 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 9,500 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 110 most recent posts we hold, published 25 July 2026 to 10 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @FuzzPD. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 110 most recent posts we hold for this entry, published 25 July 2026 to 10 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 10 of 46 posts held from the last 30 days (21.7%) 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).
通知📢:免ROOT雷达补了50张天卡 为了保证服务器稳定性 不定时补卡 最近盗卡偷卡的人很多 各位在填联系方式和密码的时候最好设置的复杂一点 天气转凉注意保暖
👍95❤10🥰3
修复完毕 很抱歉带来不好的体验 已经再次全体加时12H 共加时18H 有问题我们都是第一时间去排查解决 用不了的时间我们都会补
👍49❤3👌2
Fuzz #valorant 🎮 此为apk版本 本次更新为强制更新! 更新日志: - 修复了部分设备解密问题 - 更新了启动自动隐藏辅助 - 修复服务器问题 赞助链接: https://luoye.oopb.cn/shop/fuzz 卡密解绑链接: https://yun.hdelf.com/card.php?appid=10029
👍36❤10
Fuzz #valorant 🎮 此为sh版本 本次更新为强制更新! 更新日志: - 修复了部分设备解密问题 - 更新了启动自动隐藏辅助 - 修复服务器问题 赞助链接: https://luoye.oopb.cn/shop/fuzz 卡密解绑链接: https://yun.hdelf.com/card.php?appid=10029
👍31❤6🙏1
通知📣: 卡网上架了免ROOT雷达 Fuzz雷达 仅支持安卓设备使用 不需要root权限 连接VPN即可 可以分享网页给其他人或者在电脑平板苹果设备上看 使用教程 输入卡密 连接VPN 再启动游戏 进入对局后雷达就会生效 中途断开连接或者中途开启都会无效果 为了保证服务器稳定性 仅出售少量卡 不定时补卡 先到先得
👍50❤13😁2
库存已补
👍89❤1
Fuzz #valorant 🎮 此为sh版本 本次更新为强制更新! 更新日志: - 辅助菜单缩放支持到2.0大小 - 辅助FPS调节支持到185FPS - 优化雷达传输 赞助链接: https://luoye.oopb.cn/shop/fuzz 卡密解绑链接: https://yun.hdelf.com/card.php?appid=10029
👍88❤17🔥3🙏3🥰2
Fuzz #valorant 🎮 此为sh版本 本次更新为强制更新! 更新日志: - 辅助菜单缩放支持到2.0大小 - 辅助FPS调节支持到185FPS - 优化雷达传输 赞助链接: https://luoye.oopb.cn/shop/fuzz 卡密解绑链接: https://yun.hdelf.com/card.php?appid=10029
👍73❤7
有几个人想玩免ROOT雷达的 点个爱心我看看 多的话我去搞一个 太少就算了
❤427👍107🔥3👏2🥰2🎉1👌1😁1
目前支付通道接口出问题了 暂时有额外手续费 预计早上会恢复 可以先买天卡使用
👍28🙏1
Fuzz #valorant 🎮 此为apk版本 本次更新为强制更新! 更新日志: - 适配优化解密性能 解密更加流畅 - 解密4适配更多GPU - 适配最新linyu驱动 赞助链接: https://luoye.oopb.cn/shop/fuzz 卡密解绑链接: https://yun.hdelf.com/card.php?appid=10029
👍73❤14😁2
Fuzz #valorant 🎮 此为sh版本 本次更新为强制更新! 更新日志: - 适配优化解密性能 解密更加流畅 - 解密4适配更多GPU - 适配最新linyu驱动 赞助链接: https://luoye.oopb.cn/shop/fuzz 卡密解绑链接: https://yun.hdelf.com/card.php?appid=10029
👍59❤5😁1
Showing the 12 most recent of 110 posts we hold for @FuzzPD. 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.
@FuzzPD edited 15 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.
We recorded 3 posts on @FuzzPD as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“Fuzz-Valorant” (@FuzzPD), 31,448 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/FuzzPD.
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.