🌟瓦瓦内核更新公告🪧 1️⃣修复掩体 2️⃣加入模型显示绘制 3️⃣修复VK不显示模型 4️⃣修复游戏退出悬浮窗不显示 5️⃣更新天堂驱动 6️⃣更新RT驱动 7️⃣修复解密偏和漏人 😙赞助地址https://www.jiajintech.com/shop/NJVZ679R 🎮问题反馈 @yjttkxbot
👍51🤬3❤2🔥1😁1

Channel
@WWGFPD
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
16,618subscribers
+11,984 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1004494558750 |
|---|---|
| Type | Channel |
| Username | @WWGFPD |
| Description | 讨论群 https://t.me/WWJL41 问题反馈 @yjttkxbot |
| Created | Between 1 June 2026 and 14 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 37 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/WWGFPD |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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 |
|---|---|---|
| 5 Nov 2026, 05:56 | 16,618 | +29 |
| 4 Nov 2026, 01:47 | 16,589 | +18 |
| 3 Nov 2026, 03:31 | 16,571 | +50 |
| 2 Nov 2026, 05:48 | 16,521 | +62 |
| 1 Nov 2026, 08:55 | 16,459 | +250 |
| 31 Oct 2026, 05:40 | 16,209 | +250 |
| 30 Oct 2026, 02:07 | 15,959 | +141 |
| 29 Oct 2026, 05:17 | 15,818 | +189 |
| 28 Oct 2026, 02:26 | 15,629 | +357 |
| 26 Oct 2026, 22:51 | 15,272 | +481 |
| 26 Oct 2026, 01:47 | 14,791 | +1,203 |
| 25 Oct 2026, 02:07 | 13,588 | +640 |
| 24 Oct 2026, 01:58 | 12,948 | +165 |
| 23 Oct 2026, 02:20 | 12,783 | +125 |
| 22 Oct 2026, 01:21 | 12,658 | +63 |
| 20 Oct 2026, 17:35 | 12,595 | +69 |
| 19 Oct 2026, 19:58 | 12,526 | +76 |
| 18 Oct 2026, 21:39 | 12,450 | +111 |
| 17 Oct 2026, 23:38 | 12,339 | +118 |
| 16 Oct 2026, 22:47 | 12,221 | first reading |
33 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 8 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 4 November 2026 |
|---|---|
| Posts held | 33 (14 August 2026 – 4 November 2026) |
| Views total | 65,250 |
| Reactions total | 1,068 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 17:20 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 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.
Measured directly from 2 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.
1,159 reactions across 32 posts, in 14 distinct kinds. The most used accounts for 85.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 996 | 85.9% | |
| ❤ | 94 | 8.11% | |
| 🤬 | 35 | 3.02% | |
| 👎 | 10 | 0.863% | |
| 🤔 | 5 | 0.431% | |
| 🍌 | 4 | 0.345% | |
| 💩 | 4 | 0.345% | |
| 😁 | 3 | 0.259% | |
| 👀 | 2 | 0.173% | |
| 😘 | 2 | 0.173% | |
| 🔥 | 1 | 0.086% | |
| 🕊 | 1 | 0.086% | |
| 😍 | 1 | 0.086% | |
| 🤮 | 1 | 0.086% |
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 33 of the 33 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 1,159 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 33 most recent posts we hold, published 14 August 2026 to 4 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: 9 of 18 posts held from the last 30 days (50.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).
🌟瓦瓦内核更新公告🪧 1️⃣修复掩体 2️⃣加入模型显示绘制 3️⃣修复VK不显示模型 4️⃣修复游戏退出悬浮窗不显示 5️⃣更新天堂驱动 6️⃣更新RT驱动 7️⃣修复解密偏和漏人 😙赞助地址https://www.jiajintech.com/shop/NJVZ679R 🎮问题反馈 @yjttkxbot
👍51🤬3❤2🔥1😁1
履行公益诺言 保持公益初心 内核雷达即将在11.10号进行公益模式 雷达已经取消售卖月卡 感谢各位对瓦瓦项目的支持 我们一直以来都看在眼里记在心里🥰
👍62🤬6❤3
🌟瓦瓦用户反馈
👍30❤3😘1
🌟一些瓦瓦用户反馈 🎮赞助地址https://www.jiajintech.com/shop/NJVZ679R 👊质量反馈加时长 @yjttkxbot
👍52❤4
😙免root雷达已进行云更新 1️⃣安卓网页雷达 2️⃣修复了隐藏死亡人物头像 3️⃣修复人物武器显示 4️⃣IOS网页雷达 5️⃣修复了隐藏死亡人物头像 6️⃣修复人物武器显示 7️⃣修复中断问题 网盘🔗下载:https://wwbju.lanzn.com/b0188mytqf 密码:wawa 😙提卡地址:https://www.jiajintech.com/shop/NJVZ679R 免费雷达服务器关闭
👍59👎9❤6👀2🤬1
关于iOS免越狱雷达,打几个回合就掉了的情况,在优化更新中,等待更新会给你们加时长的
👍34❤3
🌟一些瓦瓦用户的反馈 质量反馈加时联系 @yjttkxbot 提卡🔗地址:https://www.jiajintech.com/shop/NJVZ679R
👍29❤4
🌟瓦瓦内核更新公告🪧 1️⃣新增LS驱动触摸悬浮窗选择(配置中开启) 2️⃣修复漏手模式 3️⃣修复悬浮窗仅游戏内可调用 4️⃣修复爆能器面板 5️⃣优化小地图雷达(可映射在地图中) 6️⃣调整悬浮窗布局(功能较多需自行探索) 👊赞助地址https://www.jiajintech.com/shop/NJVZ679R 👉问题/Bug反馈/改密码/忘记密码/ 请发邮件至: [email protected]
👍42❤10🤬3
ios新增 IOS专用服务器 浙江地区 http://110.42.59.108:10046/ios http://110.42.59.108:10046/<房间号> (登录后页面上有带钥匙的完整地址)
👍44🤬3❤1
🎮你的瓦瓦男友暴力炸 提卡地址https://www.jiajintech.com/shop/NJVZ679R 😌反馈问题 @yjttkxbot
👍3
请注意开了雷达让绿玩打不演也会行为7/10 这游戏的AI行为检测很强的 别忘了绿玩时常也误封十年 所以请演戏
👍63❤4
演不演决定你走多远
👍79❤5
Showing the 12 most recent of 33 posts we hold for @WWGFPD. 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.
We recorded 1 post on @WWGFPD 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 4 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“瓦瓦通知频道” (@WWGFPD), 16,618 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/WWGFPD.
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.