Channel
@wanxigghh
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1,541subscribers
+115 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003892798912 |
|---|---|
| Type | Channel |
| Username | @wanxigghh |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/wanxigghh |
Adult — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 |
|---|---|---|
| 18 Sept 2026, 06:16 | 1,541 | +1 |
| 10 Sept 2026, 05:40 | 1,540 | +10 |
| 5 Sept 2026, 08:39 | 1,530 | +27 |
| 1 Sept 2026, 22:56 | 1,503 | +60 |
| 30 Aug 2026, 06:52 | 1,443 | +23 |
| 26 Aug 2026, 21:47 | 1,420 | -4 |
| 23 Aug 2026, 23:09 | 1,424 | -11 |
| 20 Aug 2026, 00:06 | 1,435 | -5 |
| 16 Aug 2026, 15:56 | 1,440 | -4 |
| 12 Aug 2026, 22:14 | 1,444 | +15 |
| 10 Aug 2026, 04:41 | 1,429 | +3 |
| 9 Aug 2026, 15:16 | 1,426 | first reading |
12 posts held, back to 1 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 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 12 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
🥐艺名: 万茜 🤗年龄: 23身高 : 170体重 :48 熊:E 📍位置: 闵行 💸价格: 1000p/50min 1700pp/90min 👩🎓标签：无套口#胸推#吞蛋#口爆#丝袜制服#舌吻#毒龙#吹箫 🥂联系老师: @wanxi9999 💓老师频道: https://t.me/wanxigghh 韩信上海备用榜：https://t.me/shhxyxb 韩信上海优选榜：@hxshyx 韩信上海精选榜：@hxshjxb 上海外围大⭕️：@ccxkshww
已🈵
【时间】：2026-08-07 【老师】：万茜 【留名】：匿名 【人照】：9 【颜值】：9 【身材】：9 【服务】：9 【态度】：9 【环境】：9 【综合】：9 【过程】：老师很耐看，热情健谈，服务细节拉满，情绪价值到位，制服诱惑加黑丝，相当有感觉，过程非常投入 ，很不错的体验，还会复刷 【狼友大队】：点击入群
起床了
https://t.me/moduguangmingding2/24473?single
可约
🈳了
https://t.me/yuputuan1989/1860
可🈷️
每月红包、抽奖、半价、白嫖各种福利 上海大群（广告混合群） https://t.me/+TWOk2tNhl0xlMDY1 上海频道（选妃频道） https://t.me/+1pnOFefrdSM1YjVl 评价频道（评价总频道） https://t.me/+EbWEgRAWO000ZDc1 上海狼友小分队（红包白嫖各种福利） https://t.me/+xQ2RwMOlgYs5MDE1
【时间】：2026-08-01 【老师】：万茜 【留名】：匿名 【人照】：9 【颜值】：9 【身材】：9 【服务】：9 【态度】：9 【环境】：9 【综合】：9 【过程】：简单交流了发现老师好性感，服务环节,和老师玩了撕丝袜，真是性欲高涨，鸡吧硬炸了，戴套后老师开始了进攻模式，倒挂金钩等招式使得十分娴熟，值得一提是服务态度很认真，下面夹得我飘飘欲仙，爽的让我缴了械，没完够只能下次再来了 【狼友大队】：点击入群
元气满满的一天
Showing the 12 most recent of 12 posts we hold for @wanxigghh. 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.
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 2 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“万茜茜 资料” (@wanxigghh), 1,541 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/wanxigghh.
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.