Telegram RegisterThe public register of Telegram
Telegram profile photo for 【万象】曝光频道

Channel

【万象】曝光频道

@wanxiangbg

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

43subscribers

-4 since we began measuring on 31 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002451589784
TypeChannel
Username@wanxiangbg
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded31 August 2026
Last confirmed live22 October 2026
Measurements held4
Confirmed unchanged3 times, most recently 22 October 2026
On Telegramt.me/wanxiangbg

Topic

Hacking & security — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 43% 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.

Growth

43474531 August 2026 — 47 subscribers31 August 2026 — 47 subscribers28 September 2026 — 44 subscribers8 October 2026 — 43 subscribers31 August 20268 October 2026
4 measurements spanning 37 days, net -4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 42–48 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 02:1843-1
28 Sept 2026, 09:5844-3
31 Aug 2026, 15:1547no change
31 Aug 2026, 15:0147first reading

Engagement

6 posts held, back to 3 June 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 1 page 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 6 posts for this entry, the most recent from 6 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Jun 2026, 15:38 UTC37 viewsread 31 August 2026
Photo

混料曝光 启航 这家公司 跑bc 混料出几十万 赔付几万都赔不起 各位商户 自己注意下 这种商户 人家说了曝光没什么用随便爆 你给他通道玩 就准备好 自己出血 有卡到钱 的 随便卡 我茶楼给你做保 随便吃他钱 有需要混料的 去玩他通道也行 反正不用赔 👤 6634184612 👦🏻 富—富 🌐 @qihang_888888 🇨🇳 Chinese 🕑 最後同步時間 28/05/2026 👤 954804069 👦🏻 村头在逃公主 🌐 @qh_min 🕑 最後同步時間 04/06/2026 👤 8015804010 👦🏻 悲伤kitty猫 🌐 @qh_kitty 🕑 最後同步時間 06/02/2026 👤 7207151713 👦🏻 村头公主 👪 前夫 🌐 @Crystal9527 🕑 最後同步時間 05/05/2026 👤 7849912474 👦🏻 富一富(备用) 🌐 @qh_fuyifu

6 Jun 2026, 10:45 UTC25 viewsread 31 August 2026
Photo

最近很多模仿的 在各大公群发广告 大家核对清楚 不要给这群杂种 有机可乘 未与我司确认造成损失 我司 概不负责 骗子频道:https://t.me/ionfpay 👤 8042946649 👦🏻 4w4 🌐 @eommmmmmmmmmmmpayuRd 🕑 最後同步時間 06/06/2026

6 Jun 2026, 06:10 UTC19 viewsread 31 August 2026
Photo

曝光一下这几个骗子, 招群业务员 说好七天结一次账 350u 他妈的 7天之后在线信息不回 350u都跑路的狗 👤 8709689825 👦🏻 丽 👪 娜 (招🚗 业务员) 🌐 @lina9807 🕑 最後同步時間 22/05/2026 ​👤 8792599450 👦🏻 平凡(资金往来语音确认) 🌐 @ping246822 🕑 最後同步時間 29/05/2026 ​👤 8769647195 👦🏻 王木生(备用) 🌐 @amusheng284 🕑 最後同步時間 23/05/2026 ​👤 7980709537 👦🏻 王木生 🌐 @amusheng283 🕑 最後同步時間 23/05/2026

4 Jun 2026, 20:09 UTC18 viewsread 31 August 2026
Photo

曝光这家公户承兑。跑路四万多块钱。不理人了喂狗了大家注意。他家地址TNTPujmfUyAFJ3s9GtC1GKgXHx2rDB5Scn 🆔ID: 5624127828 👤名称: 零度 🌐用户名: @lingdu01 📱手机号: 🆔ID: 8338667819 👤名称: 一池春色 🌐用户名:@zjjyuzhong 📱手机号: 🆔ID: 8162060004 👤名称: 香港仔 🌐用户名: @xianggangzai889 📱手机号:

4 Jun 2026, 03:21 UTC17 viewsread 31 August 2026
Photo

买Trx 不到账 说兑换失败,还给链接去跳转钱包输入钱包密码 死骗子 退款也不退 注意了 👤 828281543 👦🏻 (在线客服)2TRX能量USDT波场靓号地址(接定制) 🌐 @trx888888trx 🕑 最後同步時間 11/03/2026

3 Jun 2026, 18:31 UTC15 viewsread 31 August 2026
Photo

最新垃圾套路兄弟们,找他要两三天后开群,让你搬砖AB隔断,复制几条信息就行,每天50U-70U,一定要1个星期才给你结款,这种群一般都是一次拉好几十个受害者一起开群,撒网模式,一般的人看到群里跑分利润那么高,都会去私聊想办法自己也加入进去干,然后叫你直押,不走担保,等你U打过去那就等着哭吧。会找各种借口叫你加押,把你吸干。这一天50-70U的工资也不会给你打的。就是等你去找他聊天,然后帮你带进去做,把你吸干。 晒出地址:TUtnKM4QMK8xTDKseNDhzxVfWecvnaRtnU 晒出地址:TEx7QBRx76xEyQX1dbWjrzCcjUQYTxYHNH 👤 7774665873 👦🏻 A8🚂 🌐 @qian8888A 🕑 最後同步時間 15/05/2026 👤 8769647195 👦🏻 王木生(备用) 🌐 @amusheng284 🕑 最後同步時間 23/05/2026 👤 8792599450 👦🏻 平凡…

Showing the 6 most recent of 6 posts we hold for @wanxiangbg. 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.

Mentions

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.

Cite this entry

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 8 October 2026 — this entry's latest reading, not the date you are reading this.

“【万象】曝光频道” (@wanxiangbg), 43 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/wanxiangbg.

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.