#安全 #在手10天 登录邮箱加手机号(可换) 价格288 pm @GYTGUY
Signed 峰峰

Channel
@wanbai886
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
6,718subscribers
-324 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001919550600 |
|---|---|
| Type | Channel |
| Username | @wanbai886 |
| Created | 3 October 2023 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 29 October 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 29 October 2026 |
| On Telegram | t.me/wanbai886 |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 |
|---|---|---|
| 29 Oct 2026, 19:20 | 6,718 | -15 |
| 26 Oct 2026, 09:36 | 6,733 | -2 |
| 22 Oct 2026, 23:38 | 6,735 | -24 |
| 20 Oct 2026, 05:30 | 6,759 | -12 |
| 17 Oct 2026, 12:28 | 6,771 | -16 |
| 14 Oct 2026, 13:35 | 6,787 | -5 |
| 11 Oct 2026, 02:54 | 6,792 | -5 |
| 5 Oct 2026, 05:56 | 6,797 | -25 |
| 27 Sept 2026, 02:18 | 6,822 | -46 |
| 15 Sept 2026, 14:59 | 6,868 | +1 |
| 11 Sept 2026, 19:18 | 6,867 | -26 |
| 7 Sept 2026, 04:39 | 6,893 | -27 |
| 2 Sept 2026, 10:04 | 6,920 | -23 |
| 30 Aug 2026, 12:47 | 6,943 | -18 |
| 27 Aug 2026, 21:25 | 6,961 | -5 |
| 24 Aug 2026, 16:19 | 6,966 | -24 |
| 20 Aug 2026, 16:48 | 6,990 | -5 |
| 17 Aug 2026, 19:06 | 6,995 | -26 |
| 14 Aug 2026, 18:27 | 7,021 | -6 |
| 11 Aug 2026, 02:01 | 7,027 | first reading |
26 posts held, back to 3 October 2023 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 14 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 26 posts for this entry, the most recent from 20 August 2026. An engagement rate over an empty window would be a number about nothing.
#安全 #在手10天 登录邮箱加手机号(可换) 价格288 pm @GYTGUY
Signed 峰峰
66级谷歌邮箱一体 苍龙4级 详情看图 价格75 联系 @YNDFX
Signed ͛饼干代付丶中介丶父 𝐒𝐒𝐒₆ ₆ ₆
1141条小易6月份石油国家和中东国家结果 我才开几百条就回本了,剩下的准备开学了懒得开 价格888 pm @GYTGUY
Signed 峰峰
Photo, posted without a caption
Signed ͛饼干代付丶中介丶父 𝐒𝐒𝐒₆ ₆ ₆
Sticker, posted without a caption
Signed 晚白
安全账号 #质保7天 登陆:邮箱➕手机号 剩下的自己看 价格50 @xbzlpfh666
Signed X B
永久保修 登录谷歌➕邮箱我的数据(完成重制) 价格128 联系 @XXNB996 双向 @xxnb996bot
Signed 晓兮(不回复傻逼) 🇨🇳
经典61级 安全 无退款 登录我的邮箱 脸书封禁 号主不怎么玩 头盔背包好看 套装不错 红装好看 💰30 联系人 @WANBAIYYDSNB
Signed 晚白
73级邮箱手机号登录 双马尾欧洲脸 详情看图 价格128 联系 @YNDFX
Signed ͛饼干代付丶中介丶父 𝐒𝐒𝐒₆ ₆ ₆
80级谷歌登录 手机号死了无记录 冰霜6级 详情看图 价格138 联系 @YNDFX
Signed ͛饼干代付丶中介丶父 𝐒𝐒𝐒₆ ₆ ₆
60💰
Signed 晚白
https://t.me/wanbai887 此频道收两位管理员 💰88一个月 联系人@wanbaiyydsnb
Signed 晚白
Showing the 12 most recent of 26 posts we hold for @wanbai886. 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.
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.
@wanbai886 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 29 October 2026 — this entry's latest reading, not the date you are reading this.
“晚白皮肤号ᖰ⌯'▾'⌯ᖳ丶𝔭𝔲𝔟𝔤𝔪” (@wanbai886), 6,718 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/wanbai886.
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.