无锡老司机【修车指南】 pinned a photo

Channel
无锡老司机【修车指南】
@WUXILIANGXIQU
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
5,513subscribers
+1,570 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 | -1003062865782 |
|---|---|
| Type | Channel |
| Usernames | @wuxilaosiji @WUXILIANGXIQU |
| Created | Between 1 August 2025 and 10 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/WUXILIANGXIQU |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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 |
|---|---|---|
| 17 Sept 2026, 11:37 | 5,513 | +45 |
| 15 Sept 2026, 22:58 | 5,468 | +85 |
| 13 Sept 2026, 03:55 | 5,383 | +14 |
| 12 Sept 2026, 16:17 | 5,369 | +42 |
| 9 Sept 2026, 12:19 | 5,327 | +20 |
| 8 Sept 2026, 16:41 | 5,307 | +107 |
| 4 Sept 2026, 11:21 | 5,200 | +44 |
| 3 Sept 2026, 12:20 | 5,156 | +103 |
| 1 Sept 2026, 02:08 | 5,053 | +47 |
| 31 Aug 2026, 07:17 | 5,006 | +101 |
| 29 Aug 2026, 09:53 | 4,905 | +49 |
| 28 Aug 2026, 13:17 | 4,856 | +103 |
| 26 Aug 2026, 18:54 | 4,753 | +48 |
| 25 Aug 2026, 19:07 | 4,705 | +70 |
| 24 Aug 2026, 02:33 | 4,635 | +48 |
| 22 Aug 2026, 10:13 | 4,587 | +67 |
| 20 Aug 2026, 19:33 | 4,520 | +83 |
| 19 Aug 2026, 07:58 | 4,437 | +100 |
| 17 Aug 2026, 11:15 | 4,337 | +46 |
| 16 Aug 2026, 18:28 | 4,291 | first reading |
Engagement
9 posts held, back to 10 September 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 5 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 9 posts for this entry, the most recent from 9 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
92 reactions across 2 posts, in 7 distinct kinds. The most used accounts for 80.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 74 | 80.4% | |
| 😁 | 6 | 6.52% | |
| 👍 | 4 | 4.35% | |
| 👏 | 3 | 3.26% | |
| 🔥 | 3 | 3.26% | |
| 👎 | 1 | 1.09% | |
| 🤔 | 1 | 1.09% |
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 2 of the 9 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 92 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 10 September 2025 to 9 July 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
加群入口: https://t.me/+2YPQRGFG4KQzNzY0 开课老师查询 新老师实习榜单 嫩妹榜单 认证优质严选榜 上榜联系 【双向点此】 无锡一键加入 上榜(或商家)直接私聊:@WXDS123 其他问题联系机器人管理:@WXBG_bot 【无锡公开大群】 加群入口: https://t.me/+9rTTT4eT_nVkZWI0 无锡公开榜:https://t.me/wuxigkb 江阴修车交流: https://t.me/Jiangyinxiuchejiaoliu 无锡太湖明珠: @WUXITAIHUMINGZHU 无锡色乐:https://t.me/wuxitandian 联盟友群:https://t.me/TgChinaz/19 江苏友群:https://t.me/CnHuangye
❤11😁1
Channel name was changed to «无锡老司机【食用频道】»
无锡老司机【修车指南】 pinned a photo
无锡老司机【修车指南】 pinned a photo
老司机 提醒 :别忘了关注本群,以防走丢哦! 无锡老司机论坛【主群】 老师开课群【老师开课通告群】 —————以下是频道————— 无锡公开榜 无锡老师候选榜 无锡报告榜 无锡避雷榜 无锡会所榜 无锡江阴 其他资源群:【上榜广告群】 无锡高端 无锡狼友 无锡文叔 ——————分割线—————— 全国友群联盟 无锡色乐 【战神主理】 无锡高端楼凤外围 无锡苏苏家资源 【老牌中介】 进群须知: 1️⃣ 严禁广告,违规者将被联盟封禁。 2️⃣ 禁止使用俄罗斯或阿拉伯文字作为昵称。 3️⃣ 男性用户不得使用女性真人头像。 4️⃣ 谨防诈骗,电报上骗子众多,请务必提高警惕,切勿轻信他人。 如遇封禁需解封,请联系 👉 @WXBG_bot
❤63😁5👍4👏3🔥3👎1🤔1
Channel photo updated
Messages in this channel will no longer be automatically deleted
Messages in this channel will be automatically deleted after 1 day
Showing the 9 most recent of 9 posts we hold for @WUXILIANGXIQU. 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 30 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@huishilig · 42,83519 posts柳州会所95甄选榜
@LZHS0772 · 24,05718 posts无锡老师新榜【候选榜单】
@wuxilaoshi8 · 16,76018 posts贵州联盟
@GuiZhouCN · 16,58114 posts兰州公开榜
@Tg730000_1 · 31,75514 posts江门【免费】资源
@gjmjamg · 27,64611 posts南通公开榜
@ntfpb · 15,12110 posts🏆 𝘽𝙍𝘼𝘽𝙐𝙎®杭州高端资源精选
@BRABUSPremiumHZ · 32,4368 posts常州🌳公开榜【2.0】
@czxlstl9 · 22,1118 posts南京公开榜
@NJGKB111 · 56,1087 posts福建(泉州厦门福州)车友总群公开榜
@Fjxiucheziyuan · 32,4556 posts江西赣州修车公开榜
@ganzhouGB · 11,3256 posts长沙打工人互助协会公开榜
@goupoyx · 18,4286 posts昆明电报群公开榜
@KMDBQGKB · 51,1886 posts南昌修车大队公开榜
@nanchangGA · 11,2696 posts珠海资源总榜
@ZH_ZZY · 35,0246 posts哈尔滨(驻凡学院)公开榜
@hrbylzl · 40,0695 posts成都总群公开
@olddriveGKB · 10,3425 posts三亚陵水老师公开榜 📢
@SanYaGkb · 26,4295 posts报告区《只发出击报告》
@shanshanaini9 · 1025 posts柳州公开资源总榜
@LZGKZB · 1,7002 posts宿州🌙公开榜
@suzhou2024 · 9,9542 posts西安公告榜【新人必读】
@XiAn_BG · 6,6772 posts盐城公告榜
@ycggb2 · 5,4132 posts
Names
Channels on the register whose handles appear in this channel's posts.
@Jiangyinxiuchejiaoliu · 10,6402 posts无锡公开榜
@wuxigkb · 24,7802 posts无锡色乐
@wuxitandian · 15,7092 posts中文电报圈
@CarGodcn · 59,7041 post江苏联盟
@CnHuangye · 14,9471 post江南Style
@JiangnanStyle_1 · 8,6401 postTelegram 中文频道 ❄️
@TgChinaz · 41,5251 post《楚汉阁全拼:@chuhange》全国外围选妃
@WUXIGAODUANXIUCHE · 2,7081 post黑车榜
@wuxiheiche · 2,0171 post无锡禅意·拈花湾
@wuxilangyoujiaoliuzongqun · 19,5241 post无锡老师新榜【候选榜单】
@wuxilaoshi8 · 16,7601 post无锡老师榜【优质严选榜】
@wuxilaoshibang · 14,1321 post无锡老司机报告
@wuxilaosijibaogao · 7,4341 post无锡老司机【个人老师展示群】
@wuxilaosijishangwu · 7,8101 post无锡嫩妹榜
@WUXINENMEIBANG · 3,1211 post《楚汉阁全拼:@chuhange》全国外围选妃
@wuxisusujiagaoduanxuanfei · 251 post无锡太湖明珠【白嫖抽奖】
@WUXITAIHUMINGZHU · 34,2301 post无锡929598等商家展示
@wuxiyushi · 4,0241 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
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@WUXILIANGXIQU 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 8 August 2026 – 9 August 2026
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 September 2026 — this entry's latest reading, not the date you are reading this.
“无锡老司机【修车指南】” (@WUXILIANGXIQU), 5,513 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/WUXILIANGXIQU.
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.