No One反馈↑↑↑ 同时【No One 001】以及【CH12306】两大项目暂不售卖,市面上流通的一些低价No One卡,新卡都是更新后补的卡,是真是假 就要你们随缘买了,反正我这边现在不放卡! 今天晚上所有未激活的卡会全部删除!! 新赛季的迷雾3.0看介绍应该难度会比较大,都在准备着新赛季。 现在的私信一概不回复。 新赛季具体什么项目上线 什么项目下线,等通知。
👍2

Channel
@wddk889
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
15,546subscribers
-722 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002431758496 |
|---|---|
| Type | Channel |
| Username | @wddk889 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/wddk889 |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 17 Sept 2026, 16:36 | 15,546 | -33 |
| 15 Sept 2026, 12:16 | 15,579 | -45 |
| 13 Sept 2026, 17:55 | 15,624 | -28 |
| 11 Sept 2026, 22:01 | 15,652 | -66 |
| 9 Sept 2026, 10:38 | 15,718 | -63 |
| 6 Sept 2026, 00:38 | 15,781 | -23 |
| 3 Sept 2026, 18:15 | 15,804 | -19 |
| 2 Sept 2026, 11:08 | 15,823 | -14 |
| 1 Sept 2026, 11:14 | 15,837 | -21 |
| 31 Aug 2026, 13:43 | 15,858 | -24 |
| 30 Aug 2026, 11:08 | 15,882 | -10 |
| 29 Aug 2026, 10:26 | 15,892 | -87 |
| 28 Aug 2026, 09:12 | 15,979 | -61 |
| 27 Aug 2026, 11:55 | 16,040 | -17 |
| 26 Aug 2026, 13:17 | 16,057 | -14 |
| 25 Aug 2026, 10:24 | 16,071 | -7 |
| 24 Aug 2026, 07:13 | 16,078 | -28 |
| 22 Aug 2026, 16:55 | 16,106 | -22 |
| 21 Aug 2026, 09:27 | 16,128 | -6 |
| 20 Aug 2026, 10:45 | 16,134 | first reading |
46 posts held, back to 27 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 47 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 3 September 2026 |
|---|---|
| Posts held | 46 (27 July 2026 – 3 September 2026) |
| Views total | 6,237 |
| Reactions total | 55 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:17 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 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.
212 reactions across 39 posts, in 12 distinct kinds. The most used accounts for 52.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 112 | 52.8% | |
| ❤ | 32 | 15.1% | |
| 🤣 | 30 | 14.2% | |
| 🤡 | 13 | 6.13% | |
| 🤮 | 9 | 4.25% | |
| 👎 | 6 | 2.83% | |
| 🔥 | 3 | 1.42% | |
| 🍌 | 2 | 0.943% | |
| 👏 | 2 | 0.943% | |
| 🌚 | 1 | 0.472% | |
| 🤬 | 1 | 0.472% | |
| 🥰 | 1 | 0.472% |
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 40 of the 46 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 212 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 46 most recent posts we hold, published 27 July 2026 to 3 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.
No One反馈↑↑↑ 同时【No One 001】以及【CH12306】两大项目暂不售卖,市面上流通的一些低价No One卡,新卡都是更新后补的卡,是真是假 就要你们随缘买了,反正我这边现在不放卡! 今天晚上所有未激活的卡会全部删除!! 新赛季的迷雾3.0看介绍应该难度会比较大,都在准备着新赛季。 现在的私信一概不回复。 新赛季具体什么项目上线 什么项目下线,等通知。
👍2
Photo, posted without a caption
❤1
来人测试和平全防适配新赛季 @YUYUMGUI
👍2
CH(12306)反馈↑ 提卡 https://www.kdocs.cn/l/ca8I2WEXd9Vx
👍1👏1
更新算法解密 bug以及反馈联系:@MFBNB9 优化模型漏打解决绘制不流畅降低发热问题 更新算法解密解决闪框问题(只测试爆破模式不闪框)需要等待10-30秒解密完 反馈以及bug联系:@MFBNB9 ## 无畏契约手游-魔法棒公益 算法级坐标解析,稳定呈现每一处关键变化-拒绝闪框-偏框。 目标、技能、道具、陷阱与投射物统一展示, 绘图样式、颜色、范围自由调节; 头甲耐久、技能状态、爆能器进程,实时掌握。 安包、拆包、爆炸倒计时清晰同步, 烟雾、投射物与危险区域及时提示, 让信息更直观,让判断更快一步。 支持触摸与陀螺仪操作, 倍镜、腰射、开镜参数独立调校, 灵敏度、压枪与防抖体验自由适配。断点范围-以及范围大小调节等等 网页雷达-局域网雷达等等功能-支持共享,一人开挂全队共享 稳定|清晰|可调|持续更新 官方频道:@MFBNB6 公益卡密:**@MFBNB66**
❤4
🔥No One(001)更新补偿通知! 所有客户注意查看!
👍3❤1
谁有他的包
👍4
三角洲的udp解密开源 仅供开发使用
👍5
谁有他的包发我一下
👍3👎1
我看这几天也没有稳定的辅助先不回归了
👍4
😃😀😃 我真不想多说了 还是用了市面上最好看的一套源码 DV作者的源码握在手里跟传家宝一样卖都不卖,还市面上最好看的源码 我真不行了 真的有源码悬浮窗都不改一下吗? 我真笑不活了 赶紧避雷柠檬内部。 真没想到DV破解版能活到现在
👍4❤2
抖音直播间 56322024981 去直播间公平 扣无敌暴龙兽 抠十遍截图找我进内部群
👍3
Showing the 12 most recent of 46 posts we hold for @wddk889. 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 1 registered channel — 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“JOJO官方频道” (@wddk889), 15,546 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/wddk889.
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.