昵称:蓉蓉 【看上的名字发我 确定时间 遥控上楼】 地址: #梁溪区星汇天地 料理表: 参照以上料理卡服务 料金:1200P 2000PP 🌎预约私聊妲己🌎 限制私聊: @WUXIDAJI_bot 点击查看总资料合集 🖥 ‼️验证报告合集‼️ ❤️一键关注所有资源 ❤️

Channel
无锡高端甄选【已验证】
@wuxibantao
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
5,012subscribers
+190 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001742959989 |
|---|---|
| Type | Channel |
| Username | @wuxibantao |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/wuxibantao |
Topic
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 23:55 | 5,012 | +5 |
| 14 Sept 2026, 23:16 | 5,007 | +1 |
| 11 Sept 2026, 10:41 | 5,006 | +15 |
| 6 Sept 2026, 06:59 | 4,991 | +10 |
| 1 Sept 2026, 13:54 | 4,981 | +31 |
| 29 Aug 2026, 10:48 | 4,950 | +26 |
| 26 Aug 2026, 14:44 | 4,924 | +16 |
| 23 Aug 2026, 18:04 | 4,908 | +35 |
| 20 Aug 2026, 07:25 | 4,873 | +7 |
| 17 Aug 2026, 14:06 | 4,866 | +3 |
| 14 Aug 2026, 00:17 | 4,863 | +19 |
| 11 Aug 2026, 00:24 | 4,844 | +17 |
| 7 Aug 2026, 16:36 | 4,827 | +5 |
| 7 Aug 2026, 04:17 | 4,822 | first reading |
Engagement
20 posts held, back to 7 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 2m 56s
- Average length
- 13s
Measured directly from 14 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.
Reaction mix
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 of the 20 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 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 7 August 2026 to 12 August 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.
Recent posts
⭐️昵称:兮兮(可✌️) 【看上的名字发我 确定时间 遥控上楼】 地址: #梁溪区星汇天地 料理表: 参照以上料理卡服务 料金:1200P 2000PP 🌎预约私聊妲己🌎 限制私聊: @WUXIDAJI_bot 点击查看总资料合集 🖥 ‼️验证报告合集‼️ ❤️一键关注所有资源 ❤️ 🔥验证报告A: https://t.me/WUXIYH/32380
昵称:夏日 【看上的名字发我 确定时间 遥控上楼】 地址: #梁溪区东岭锡上 料理表: 参照以上料理卡服务 料金:1200P 2000PP 🌎预约私聊妲己🌎 限制私聊: @WUXIDAJI_bot 点击查看总资料合集 🖥 ‼️验证报告合集‼️ ❤️一键关注所有资源 ❤️
昵称:鹿小漫(可上🚪 ✌️) 【看上的名字发我 确定时间 遥控上楼】 地址: #梁溪区南长街 料理表: 参照以上料理卡服务 料金:1200P 2000PP 🌎预约私聊妲己🌎 限制私聊: @WUXIDAJI_bot 点击查看总资料合集 🖥 ‼️验证报告合集‼️ ❤️一键关注所有资源 ❤️
上新一对双胞胎 皮肤雪白 无锡市仅此一对 货真价实
昵称:小叮当(可✌️) 【看上的名字发我 确定时间 遥控上楼】 地址: #梁溪区星汇天地 料理表: 参照以上料理卡服务 料金:1200P 2000PP 🌎预约私聊妲己🌎 限制私聊: @WUXIDAJI_bot 点击查看总资料合集 🖥 ‼️验证报告合集‼️ ❤️一键关注所有资源 ❤️
❤1
昵称:蓉蓉 【看上的名字发我 确定时间 遥控上楼】 地址: #梁溪区星汇天地 料理表: 参照以上料理卡服务 料金:1200P 2000PP 🌎预约私聊妲己🌎 限制私聊: @WUXIDAJI_bot 点击查看总资料合集 🖥 ‼️验证报告合集‼️ ❤️一键关注所有资源 ❤️
昵称:小桃仙(可上🚪) 【看上的名字发我 确定时间 遥控上楼】 地址: #梁溪区金轮星空间 料理表: 参照以上料理卡服务 料金:1200P 2000PP 🌎预约私聊妲己🌎 限制私聊: @WUXIDAJI_bot 点击查看总资料合集 🖥 ‼️验证报告合集‼️ ❤️一键关注所有资源 ❤️
昵称:权恩菲 【看上的名字发我 确定时间 遥控上楼】 地址: #梁溪区嘉悦阁 料理表: 参照以上料理卡服务 料金:1200P 2000PP 🌎预约私聊妲己🌎 限制私聊: @WUXIDAJI_bot 点击查看总资料合集 🖥 ‼️验证报告合集‼️ ❤️一键关注所有资源 ❤️
昵称:西西 【看上的名字发我 确定时间 遥控上楼】 地址: #梁溪区东岭锡上 料理表: 参照以上料理卡服务 料金:1200P 2000PP 🌎预约私聊妲己🌎 限制私聊: @WUXIDAJI_bot 点击查看总资料合集 🖥 ‼️验证报告合集‼️ ❤️一键关注所有资源 ❤️
⭐️昵称:萝莉猫 【看上的名字发我 确定时间 遥控上楼】 地址: #梁溪区东岭锡上 料理表: 参照以上料理卡服务 料金:1200P 2000PP 🌎预约私聊妲己🌎 限制私聊: @WUXIDAJI_bot 点击查看总资料合集 🖥 ‼️验证报告合集‼️ ❤️一键关注所有资源 🔥验证报告A: https://t.me/WUXIXIUCHECEPING/62 🔥验证报告B: https://t.me/WUXIXIUCHECEPING/66
独家招聘,明天无锡首开
Showing the 12 most recent of 20 posts we hold for @wuxibantao. 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
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“无锡高端甄选【已验证】” (@wuxibantao), 5,012 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/wuxibantao.
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.