同意
👍45

Channel
@WWNB111
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
21,993subscribers
+11,507 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003978313019 |
|---|---|
| Type | Channel |
| Username | @WWNB111 |
| Description | 频道项目一切皆为公益 其余皆为自愿捐赠 开发者不会主动联系你 本项目仅供逆向学习研究 下载者的任何行为与作者无关 若有侵权违法行为,请联系我删除内容 请在24小时内删除本应用 |
| Created | Between 1 April 2026 and 14 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/WWNB111 |
Other / unclassifiable — 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 66% 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 |
|---|---|---|
| 3 Oct 2026, 14:57 | 21,993 | +1,888 |
| 24 Sept 2026, 21:58 | 20,105 | +1,346 |
| 18 Sept 2026, 19:57 | 18,759 | +1,172 |
| 16 Sept 2026, 08:00 | 17,587 | +180 |
| 14 Sept 2026, 14:38 | 17,407 | +353 |
| 13 Sept 2026, 03:20 | 17,054 | +575 |
| 11 Sept 2026, 08:16 | 16,479 | +422 |
| 8 Sept 2026, 10:41 | 16,057 | +680 |
| 5 Sept 2026, 01:56 | 15,377 | +347 |
| 3 Sept 2026, 08:39 | 15,030 | +248 |
| 1 Sept 2026, 23:25 | 14,782 | +163 |
| 31 Aug 2026, 23:18 | 14,619 | +143 |
| 30 Aug 2026, 19:16 | 14,476 | +173 |
| 29 Aug 2026, 21:15 | 14,303 | +212 |
| 28 Aug 2026, 17:53 | 14,091 | +270 |
| 27 Aug 2026, 18:23 | 13,821 | +501 |
| 26 Aug 2026, 16:02 | 13,320 | +629 |
| 25 Aug 2026, 14:02 | 12,691 | +314 |
| 24 Aug 2026, 17:18 | 12,377 | +490 |
| 23 Aug 2026, 00:17 | 11,887 | first reading |
98 posts held, back to 14 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 36 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 5 October 2026 |
|---|---|
| Posts held | 98 (14 August 2026 – 5 October 2026) |
| Views total | 52,679 |
| Reactions total | 636 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Oct 2026, 14: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 5 October 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 8 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.
3,548 reactions across 97 posts, in 28 distinct kinds. The most used accounts for 70.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2,483 | 70.0% | |
| ❤ | 428 | 12.1% | |
| 😭 | 178 | 5.02% | |
| 🤡 | 164 | 4.62% | |
| 😡 | 64 | 1.80% | |
| 🤯 | 45 | 1.27% | |
| 🫡 | 30 | 0.846% | |
| 😍 | 24 | 0.676% | |
| 🗿 | 23 | 0.648% | |
| 🔥 | 16 | 0.451% | |
| 🥰 | 15 | 0.423% | |
| 😁 | 14 | 0.395% | |
| 🤩 | 14 | 0.395% | |
| 👏 | 11 | 0.31% | |
| 🍌 | 8 | 0.225% | |
| 🕊 | 5 | 0.141% | |
| 🤷♀ | 5 | 0.141% | |
| 🎉 | 3 | 0.085% | |
| 😇 | 3 | 0.085% | |
| 🤪 | 3 | 0.085% | |
| 8 further kinds | 12 | 0.338% |
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 97 of the 98 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,548 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 98 most recent posts we hold, published 14 August 2026 to 5 October 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.
同意
👍45
国庆结束后回去更新好东西 公益的免root的注入 还有一些解密
👍58🤯5❤2
说点大事
👍83❤4
🎮瓦瓦内部v2收费独家驱动稳定中 ✅赞助https://d.jiajintech.com/tkku7u ♾反馈 @fenz6
👍43❤6
uc是unicorn映射指令到自己虚拟CPU中跑 纯算法解密 不动内存 也是现在三角洲和王者常见的解密 只是现在瓦没人使用unicorn来进行解密 因为瓦下发的shellcode只有帧同步 所以常用都是扫内存或者换坐标
👍63🗿8❤3🥴2😁2
这两天听过最大的笑话,uc解密是内存,瓦瓦公益内核早就没加密了,自己看看就知道了
👍56❤8😁6
瓦瓦公益内核新赛季稳定中 反馈问题 @fenz6
👍63❤3
😙瓦瓦内部版v2内测用户已满将在10.7号国庆假期结束停止售卖 但内部版服务器不会关闭以后之后依旧可以使用但是只提供于10.7之前购买的用户 大家抓紧时间下单内部版 从此专心更新公益 https://d.jiajintech.com/tkku7u
👍56❤9🗿7
😙解答一下你们的问题: 1️⃣驱动就在软件里直接刷入驱动就行,如果重启的话,就换驱动。 2️⃣网页雷达在软件主页里往下拉就能看到。 3️⃣解密没效果的手机重启看看,如果还没效果,你就来回换解密试试。 4️⃣自瞄没效果,大退游戏和wawa重新进,或者换驱动 5️⃣驱动刷入崩溃,或者是显示没有链接上,从MT管理器里面手动刷入。 6️⃣如果感觉UC解密没有效果,换其他的加密,证明你的账号没有下发。 7️⃣掩体有问题,请使用实时渲染,不要再使用本地模型。 8️⃣自瞄有问题概率也是掩体问题 ⚠️本公告根据你们反馈的问题进行调整的回复
👍47❤11
新赛季瓦瓦内部v2付费稳定中 赞助地址 https://d.jiajintech.com/tkku7u
👍33❤13
🌟瓦瓦内核神话暴力炸反馈,感谢兄弟们的一路陪伴主频道已突破1.5w人了,可惜我也没什么能送给大家的,总之谢谢兄弟们了😭
👍17❤2
瓦瓦公益主频道 pinned a file
Showing the 12 most recent of 98 posts we hold for @WWNB111. 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.
@WWNB111 edited 1 post 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.
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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“瓦瓦公益主频道” (@WWNB111), 21,993 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/WWNB111.
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.