【无锡老司机验证】 @WUXI_LAOSIJI 艺名: #小小 联系:@ntxb123 频道:https://t.me/ntxb1234 💰水费: 6P 12PP 标签: #梁溪区 #自聊 #少妇 #态度车 #服务车 #身材车 #6P 活动优惠:出击分兑换白嫖 积分抽奖 无锡老师榜: @wuxilaoshibang 无锡全知道: @wuxilaosiji 报告递交开课查询:@CHAXUNJIRIREN_bot

Channel
无锡老师新榜【候选榜单】
@wuxilaoshi8
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
17,201subscribers
+873 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002744449117 |
|---|---|
| Type | Channel |
| Username | @wuxilaoshi8 |
| Description | 老师榜单! |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/wuxilaoshi8 |
Topic
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 16:34 | 17,201 | +28 |
| 14 Nov 2026, 08:06 | 17,173 | +68 |
| 11 Nov 2026, 08:46 | 17,105 | +48 |
| 9 Nov 2026, 11:40 | 17,057 | +9 |
| 8 Nov 2026, 00:37 | 17,048 | +5 |
| 6 Nov 2026, 23:36 | 17,043 | +23 |
| 6 Nov 2026, 00:26 | 17,020 | +25 |
| 4 Nov 2026, 20:56 | 16,995 | +13 |
| 3 Nov 2026, 20:07 | 16,982 | +13 |
| 2 Nov 2026, 21:35 | 16,969 | +20 |
| 1 Nov 2026, 23:54 | 16,949 | -5 |
| 1 Nov 2026, 01:49 | 16,954 | +9 |
| 31 Oct 2026, 03:18 | 16,945 | +2 |
| 30 Oct 2026, 04:48 | 16,943 | +8 |
| 29 Oct 2026, 01:57 | 16,935 | +10 |
| 27 Oct 2026, 22:47 | 16,925 | -12 |
| 26 Oct 2026, 19:59 | 16,937 | +6 |
| 25 Oct 2026, 23:27 | 16,931 | -5 |
| 24 Oct 2026, 20:17 | 16,936 | -4 |
| 23 Oct 2026, 22:21 | 16,940 | first reading |
Engagement
87 posts held, back to 5 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 86 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 6.80%
- avg views ÷ 17,201 subscribers
- Avg views / post
- 1,170
- 36 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 36
- of 87 held
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 17 November 2026 |
|---|---|
| Posts held | 87 (5 August 2026 – 17 November 2026) |
| Views total | 42,107 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 17:50 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.
What this channel posts
- Photos
- ≈1,040
- Videos
- ≈273
- Links
- ≈197
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 10m 16s
- Average length
- 10s
Measured directly from 61 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 36 posts held from the last 30 days (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).
加群入口: 无锡老司机【加群入口】 开课老师查询 新老师实习榜单 嫩妹榜单 认证优质严选榜 上榜联系 【双向点此】 无锡一键加入 浅浅:@RoseRic520 频道:https://t.me/yoyoy131520 验证报告发布: @CHAXUNJIRIREN_bot
【无锡老司机验证】 @WUXI_LAOSIJI 艺名: #旺仔 联系:@wangzaibby 频道:https://t.me/qweasdzxcnihao00 双向机器人:@jjkkoplnn_bot 💰水费: 700P 1400PP 标签: #梁溪区 #自聊 #性感御姐 #态度车 #服务车 #身材车 #7P 活动优惠:出击分兑换白嫖 积分抽奖 无锡老师榜: @wuxilaoshibang 无锡全知道: @wuxilaosiji 报告递交开课查询:@CHAXUNJIRIREN_bot
加群入口: 无锡老司机【加群入口】 开课老师查询 新老师实习榜单 嫩妹榜单 认证优质严选榜 上榜联系 【双向点此】 无锡一键加入 月月老师:@kele1421 老师频道:@wuxiyueyue 验证报告发布: @CHAXUNJIRIREN_bot #惠山区 #陪浴 #胸推 #包时 #巨乳 #舌吻 #六九 #情趣丝袜
【无锡老司机验证】 @WUXI_LAOSIJI 艺名: #于婷婷 联系:@yiyaoyy 频道:https://t.me/yiyaoaoao 💰水费: 600P 1100PP 标签: #新吴区 #自聊 #嫩妹 #态度车 #服务车 #身材车 #6P 活动优惠:出击分兑换白嫖 积分抽奖 无锡老师榜: @wuxilaoshibang 无锡全知道: @wuxilaosiji 报告递交开课查询:@CHAXUNJIRIREN_bot
【无锡老司机验证】 @WUXI_LAOSIJI 艺名: #草莓 联系:@WUXI_YAOYAO 频道:https://t.me/WUXIaaaaa 💰水费: 4P 标签: #梁溪区 #自聊 #少妇 #态度车 #服务车 #身材车 #4P 活动优惠:出击分兑换白嫖 积分抽奖 无锡老师榜: @wuxilaoshibang 无锡全知道: @wuxilaosiji 报告递交开课查询:@CHAXUNJIRIREN_bot
【无锡老司机验证】 @WUXI_LAOSIJI 艺名: #茜茜 联系:@QIanbaoq 频道:@byh2i 💰水费: 6P 12PP 标签: #梁溪区 #自聊 #少妇 #态度车 #服务车 #身材车 #6P 活动优惠:出击分兑换白嫖 积分抽奖 无锡老师榜: @wuxilaoshibang 无锡全知道: @wuxilaosiji 报告递交开课查询:@CHAXUNJIRIREN_bot
【无锡老司机认证】 花名: #莫妮卡 车牌: @monikaaccc 车费: #600p #1200pp 位置: #梁溪区 标签: #梁溪区 #F胸, #69,#毒龙,#口爆,#丝袜,#制服,#上门 注: 【我是莫妮卡,来自于山东,服务齐全,态度至上!会用心服务好每一位选择我的宝贝】 优惠情况:群内可使用积分兑换出击优惠 🟢无锡老司机大群: https://t.me/+9rTTT4eT_nVkZWI0 🟢无锡其他资源群: @WUXILAOSIJI 📝 给老师写评价 🔍 查看老师所有评价
无锡老司机【聊天群】 开课老师查询 新老师实习榜单 嫩妹榜单 认证优质严选榜 上榜联系 小兰老师: @wx_cc33 价位:600P 1200PP 频道: https://t.me/wuxixiaolan #新吴区 #69 #舌吻 #大长腿 # 性感御姐 #情趣丝袜 验证报告发布: @CHAXUNJIRIREN_bot
【无锡老司机验证】 @WUXI_LAOSIJI 艺名: #念念 联系:@niaobao1 频道: https://t.me/nianba1 💰水费: 600P /1200PP 800P/1600PP 标签: #梁溪区 #自聊 #嫩妹 #态度车 #服务车 #身材车 #6P 活动优惠:出击分兑换白嫖 积分抽奖 无锡老师榜: @wuxilaoshibang 无锡全知道: @wuxilaosiji 报告递交开课查询:@CHAXUNJIRIREN_bot
【无锡老司机验证】 @WUXI_LAOSIJI 艺名: #小晗 联系:@xiaohan520z 频道: https://t.me/xiaohan520xi 💰水费: 500P 1000PP 标签: #新吴区 #自聊 #嫩妹 #态度车 #服务车 #身材车 #5P 活动优惠:出击分兑换白嫖 积分抽奖 无锡老师榜: @wuxilaoshibang 无锡全知道: @wuxilaosiji 报告递交开课查询:@CHAXUNJIRIREN_bot
加群入口: 无锡老司机【加群入口】 开课老师查询 新老师实习榜单 嫩妹榜单 认证优质严选榜 上榜联系 【双向点此】 无锡一键加入 老师: #芸溪 @xff085211 老师频道:@IRAI27Kio0A1OGQ1 验证报告发布: @CHAXUNJIRIREN_bot #口推💋 #臀推❤️ #漫游指划❤️ #花式吹箫💋 #陪浴🥡 #69式💋 #内射🍑#阴推🌿 #毒🐉 #添🥚 #冰🔥 #情趣👗
Showing the 12 most recent of 87 posts we hold for @wuxilaoshi8. 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.
Posts recorded as deleted after publishing
We recorded 2 posts on @wuxilaoshi8 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.
- First seen missing
- 20 August 2026
- Most recent seen missing
- 27 August 2026
- Median time before seen missing
- 2 days
- Seen missing in the last 30 days
- 0
Forward network
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.
Mentions
Named by 8 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.
@WUXILIANGXIQU · 7,2508 posts无锡嫩妹榜
@WUXINENMEIBANG · 3,5664 posts江阴公开榜
@JIANGYINGONGKAIBANG · 5,9172 posts无锡老师榜【优质严选榜】
@wuxilaoshibang · 14,5162 posts是你的奶茶妹妹🥤
@naichameimei77 · 1,1871 post小馒头
@WUXIWENQUAN · 5761 post170车模丁丁~服务齐全
@xhcjfudjdbdjsjdjjjjj · 1,0631 post宜兴在榜老师
@yixingmeizi · 1,0901 post
Names
Channels on the register whose handles appear in this channel's posts.
@wuxilaoshibang · 14,51665 posts无锡老司机【修车指南】
@WUXILIANGXIQU · 7,25050 posts无锡嫩妹榜
@WUXINENMEIBANG · 3,56637 posts无锡老司机
@WUXI_LAOSIJI · 39,19336 posts团子的朋友圈
@bz998800 · 1,5583 posts摇摇95/98/🉑上门
@hihwji · 5723 posts170岚心自聊
@lanxin8898 · 2,4143 posts咪宝的私宅
@byh2i · 162 posts摇摇/95/98🉑上门
@coiolniojmj999 · 3522 posts无锡-芸溪老师个人频道
@IRAI27Kio0A1OGQ1 · 5712 posts九黎的vip
@jiuli55555 · 2,1092 posts米粒🍑的🏠
@mili888618613 · 4792 posts萍萍抓龙筋
@pingping9090 · 2,5862 posts小兰花🌺
@wuxixiaolan · 1,3742 posts吉吉🐰的大草原
@wxjjt1234 · 3632 posts小晗的家庭🏠
@xiaohan520xi · 1,3912 posts安然大⭕️御姐 (火爆营业中)🔥
@anran05367 · 7671 post莉莉的后花园
@mxx1166 · 1,5221 post红豆的日常
@tang628314 · 731 post(爱跳舞的姗姗)
@wuxigerenlaoshi · 3,9371 post初初的喵喵屋
@WUXILAOSIJI15 · 1,8631 post柒柒的小屋🛖
@wuximiaomiao · 1,0971 post浅浅后宫
@xinqianqian123 · 3751 post瑶瑶(06个人美术生兼职)
@yy07886 · 6011 post
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@wuxilaoshi8 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.
Evidenced gone
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.
named in 2 posts, 10 August 2026 – 11 August 2026 · confirmed gone 15 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“无锡老师新榜【候选榜单】” (@wuxilaoshi8), 17,201 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/wuxilaoshi8.
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.