😃深圳全区《金牌🥇娱乐》 #94水会《金牌🥇水会》 #95口爆《金牌🥇会所》 #98全套《一条🐉服务》 无套💋爆~花式毒🐉~ 吃🥚舔🥚~真🈳调情~ 👅尖环游~🐻推全身~ 冰🔥两重~舔🦪摸🦪~ 69式互💋~爆👄👄里~ 💸#94价格480-498(60分钟可出两次) 💸#95价格580-598(60分钟口一手一) 💸#96价格798左右(70分钟口两次) 💸#98价格1000起步(全套一条龙🐉服务) 微信QQ:只预约发位置、不聊项目、不聊敏感话题、非诚勿扰 选择佳丽:不提供相片、到店去挑选、不满意可以换、安排满意为止、🤝🤝 🔑电报联系:@fg20268 🤖双向联系:@haoge88bot 😄微信联系:aa22138278 😎QQ联系:2996069374 🔗频道群:https://t.me/a22138278 🔗交流群:https://t.me/hg202488 😀深圳修车联盟会报告 😀深圳修车联盟会资料榜 😀深圳修车联盟会

Channel
深圳修车联盟会公开榜🥇
@Szxiuchehui
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
43,065subscribers
+2,056 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1003020870405 |
|---|---|
| Type | Channel |
| Usernames | @Szxiuchehui @ycx500 |
| Description | 💥 欢迎来到深圳修车联盟会🥇 本群上榜老师和商家都经过严格审核 兄弟们放心出击 群组: @a1688d 榜单: @ycx500 报告: @zeyig 上榜或任何问题联系群主: @xclmh 报告提交: @xclmh / @Xclmh2_bot |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 117 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/Szxiuchehui |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 6 Nov 2026, 16:49 | 43,065 | no change |
| 6 Nov 2026, 15:59 | 43,065 | -308 |
| 5 Nov 2026, 13:35 | 43,373 | no change |
| 5 Nov 2026, 13:20 | 43,373 | -411 |
| 4 Nov 2026, 17:01 | 43,784 | no change |
| 4 Nov 2026, 14:28 | 43,784 | -487 |
| 3 Nov 2026, 16:28 | 44,271 | -34 |
| 3 Nov 2026, 10:54 | 44,305 | -150 |
| 2 Nov 2026, 17:35 | 44,455 | -6 |
| 2 Nov 2026, 08:01 | 44,461 | -29 |
| 1 Nov 2026, 19:48 | 44,490 | -109 |
| 1 Nov 2026, 05:50 | 44,599 | -49 |
| 31 Oct 2026, 16:28 | 44,648 | -67 |
| 31 Oct 2026, 02:50 | 44,715 | -33 |
| 30 Oct 2026, 18:31 | 44,748 | -111 |
| 29 Oct 2026, 23:46 | 44,859 | -5 |
| 29 Oct 2026, 18:19 | 44,864 | -103 |
| 28 Oct 2026, 22:35 | 44,967 | no change |
| 28 Oct 2026, 16:07 | 44,967 | -75 |
| 27 Oct 2026, 18:19 | 45,042 | first reading |
Engagement
146 posts held, back to 6 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 176 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.58%
- avg views ÷ 43,065 subscribers
- Avg views / post
- 1,110
- 52 posts measured
- Reaction rate
- 0.062%
- reactions ÷ views · ER floor
- Posts in window
- 52
- of 146 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. It is computed over the 3 of 52 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 November 2026 |
|---|---|
| Posts held | 146 (6 August 2026 – 6 November 2026) |
| Views total | 57,808 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 01:25 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,680
- Videos
- ≈283
- Links
- ≈393
Lifetime counters from Telegram’s own channel header, read 7 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
- 12m 54s
- Average length
- 11s
Measured directly from 70 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
18 reactions across 17 posts, in 4 distinct kinds. The most used accounts for 77.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14 | 77.8% | |
| 🔥 | 2 | 11.1% | |
| 🎉 | 1 | 5.56% | |
| 🤮 | 1 | 5.56% |
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 19 of the 146 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 18 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 146 most recent posts we hold, published 6 August 2026 to 6 November 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
Telegram’s own ‘edited’ marker: 1 of 52 posts held from the last 30 days (1.92%) 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).
📱艺名:#大茜茜 😃位置:#龙华 💸课费:#800p #1400pp ✏️资料:#身高165 #胸围36C 🔑电报:@xixi1066 ⚙️双向:@xixi1066_bot 🥺频道:https://t.me/Szfey 🟡标签:#鸳鸯浴 #无套吹箫 #六九 #波推 #制服诱惑 😀深圳修车联盟会交流群 😀深圳修车联盟会公开榜 😀深圳修车联盟会报告榜
深圳 罗湖 岚姐 个人 熟女 兼职 找年轻的请绕行 亲亲 不要在这里和我聊,我这个飞机没声音 也不经常在线 麻烦你加我其他联系方式 说电报里面看到的 与你号 ww1985 ww600619 电报号 @ww1371522 QQ号 3183161733 QQ号 2169107388 频道 @frewqz 双向机器人 @langlang5201314love_bot 电话 19924551061 地址罗湖九号线人民南B出口 价格 3张起(看上面课表图) 自带课室 方便停车 不管加了微信和QQ说在飞机上看到的 说了优先通过 不要问 可不可无套 内射 扣逼 颜射 问了也不回复 亲亲 到频道里看照片,看课表如约课的话还是加其他的联系方式,这里没声音也不经常在 如发信息不回,请打电话。不约就不要打扰 😀深圳修车联盟会交流群 😀深圳修车联盟会公开榜 😀深圳修车联盟会报告榜
#深圳 #罗湖 深圳 姓名艳艳 年龄:32 身高:164 体重:105 胸围:36C 服务内容:鸳鸯浴,吹箫、69调情、丝袜诱惑,高跟鞋,情趣内衣,制服,水中潇、🐍吻、全套服务收费标准一节课30分钟三章.两节课60分钟六章!特色服务: 毒龙,添丹丹,磨棒,深喉,口爆,潮吹,按摩,冰火两重天,角色扮演特色服务收费标准,一节课50分钟五章两节课100分钟九章,上门收费标准一节课50分钟七章,两节课100分钟十二章,酌情加路费,叶课时间12点到早八点1200不限次数,上门叶课1500酌情加路费,以上的项目和叶课后花园都是另外加两章,sm项目做爱,各种体位,轻度捆绑,轻度鞭打,制度,丝袜,蒙眼堵嘴,手铐脚镣,情趣挑逗,自慰,震动棒,假阳具,口爆,颜射,69,车震,角色扮演。肛交,三通,深喉,宠物调教,遛狗,滴蜡,侍浴,毒龙,虐肛,耳光,语言羞辱。器具折磨,舔足,潮吹,sm收费标准3000服务时间两个小时,叶课4000 服务时间11点…
📱艺名:#草莓 😃位置:#南山 💸课费:#800P #1500PP #夜3000 ✏️资料:#芳龄20 #身高172 #体重52kg #胸38D 🔑电报:@gzkkbb ⚙️双向:@kekebbbot 🥺频道:https://t.me/dingliucm 🟡标签:#蛇吻 #六九 #制服 #角色扮演 #cos剧情 #口爆 #毒龙 😀深圳修车联盟会交流群 😀深圳修车联盟会公开榜 😀深圳修车联盟会报告榜
📱艺名:#大蜜蜜 😃位置:#龙岗 💸课费:#700p #1300pp ✏️资料:#身高163 #胸围C+ #芳龄22 #体重56kg 🔑电报:@MIMIoo2 🥺频道:https://t.me/MIMI99897 🟡标签:#无套口 #舔蛋蛋 #水中萧 #角色扮演 😀深圳修车联盟会交流群 😀深圳修车联盟会公开榜 😀深圳修车联盟会报告榜
📱艺名: #甜妹兔 😃位置:#南山 💸课费:#14P #26PP ✏️资料:#芳龄21 #身高167 #体重50kg #胸D 🔑电报:@mingqwer ⚙️双向:@tuya1122_bot 🥺频道:https://t.me/+a2FXLr66Im5lYjRl 🟡标签: #制服 #六九 #嫩妹 #大冲 #亲吻 #共浴 #上门 😀深圳修车联盟会交流群 😀深圳修车联盟会公开榜 😀深圳修车联盟会报告榜
📱艺名:依琳😊 😃位置: #龙华 💸课费:#1300P #2300PP 🔑电报:@blbl444 ⚙️双向:@YLYL008bot 🥺频道:@YLYL444 🟡标签:#平面模特 #舌吻 😀深圳修车联盟会交流群 😀深圳修车联盟会公开榜 😀深圳修车联盟会报告榜
📱艺名:#李晨曦 😃位置:#南山 💸课费:#900P #1700PP ✏️资料:#芳龄19 #身高165 #体重49kg #胸C 🔑电报:@chenxi520 ⚙️双向:@cxfc77_bot 🥺频道:https://t.me/chenxi55011 🟡标签:#嫩妹 #舌吻 #六九 😀深圳修车联盟会交流群 😀深圳修车联盟会公开榜 😀深圳修车联盟会报告榜
📱艺名:#冉冉 😃位置:#南山 💸课费:#900P #1700PP ✏️资料:#芳龄22 #身高165 #胸围C 🔑电报:@ranran948 ⚙️双向:@qt6857_bot 🥺频道:https://t.me/qyr5455 🟡标签:#鸳鸯浴 #制服诱惑 #指滑 #高跟丝袜角色扮演 #胸推 #无套口 #六九 #激情爱爱 #舌吻kiss #倒挂金钩 #365度旋转吹箫 😀深圳修车联盟会交流群 😀深圳修车联盟会公开榜 😀深圳修车联盟会报告榜
❤1
📱艺名:#念念 😃位置:#深圳 #南山 💸课费:#1400P #2200PP ✏️资料:#芳龄19 #身高165cm #体重45kg #胸围C 🔑电报:@nian5207 ⚙️双向:@nian5270bot 🥺频道:https://t.me/+ovEsXZ_LvPBmZDJk 🟡标签:#指滑 #六九 #丝袜诱惑 #激情做爱 #姿势随意 #配合好 #情绪价值给足 😀深圳修车联盟会交流群 😀深圳修车联盟会公开榜 😀深圳修车联盟会报告榜
📱艺名:西施 😃位置:#深圳 #南山 💸课费:#800P #1500PP ✏️资料:#芳龄21 #身高170 #体重 46kg #胸围38D 🔑电报:@jiajials04 ⚙️双向:@jiajia5210bot 🥺频道:https://t.me/wanghongxishi 🟡标签:#🐍吻 #六九 #制服 #SM调教 #毒龙 #深喉 #水中萧 #配合度非常高 😀深圳修车联盟会交流群 😀深圳修车联盟会公开榜 😀深圳修车联盟会报告榜
Showing the 12 most recent of 146 posts we hold for @Szxiuchehui. 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 4 posts on @Szxiuchehui 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
- 9 August 2026
- Most recent seen missing
- 25 October 2026
- Median time before seen missing
- 34 hours
- Seen missing in the last 30 days
- 1
Mentions
Named by 5 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.
@Szxiuchehui0755 · 36,365133 posts深圳修车联盟会报告榜🥇
@zeyig · 16,882127 posts深圳修车会资料榜
@g1688x · 3,16777 posts深圳南山浅吟&半裸疗愈释放抓龙筋
@qyspa2026 · 5,3467 posts🎁免费抽奖助手🎁
@tgLotteryuw8bot · 13,0177 postsTelegram抽奖活动
@xiu8che · 99,4347 posts深圳94-95《金牌🥇会所》
@a22138278 · 4,6126 posts深圳94-95《出击交流群》
@hg202488 · 4,8686 posts南山栖栖里 · sex疗愈丝足抓龙筋 SPA
@Yyepm · 5,3634 posts巨乳紫苏-SM-户外-剧情演绎-东京浴-COS-3P
@zisu969696 · 18,9264 posts南山 初音· あんじ 疗愈私密抓龙筋SPA
@ggs66633 · 12,6523 posts深圳(莉莉)抓龙经前高潮.抚触疗愈.脱敏.龟责,女王调教
@hu124567 · 7,3333 posts深圳专业抓龙筋,前高 丝足 龟责 女王(福田莉莉)
@hu990108 · 3683 posts娇娇 SPA抓龙筋 个人工作室 (深圳福田)
@jiao599 · 5,8753 posts罗湖糖糖.水床🌷
@luohushushu · 1,4453 posts梦梦G奶深圳波霸
@mengmeng198198198 · 4,8313 posts深圳朵朵 SPA按摩抓龙筋
@mimi02251 · 5,1973 posts荷花:深圳会所推荐官
@SZYY5683 · 5,3383 posts深圳南山网红38D西施💕
@wanghongxishi · 4,8443 posts南山樱花🌸境·疗愈セクシー抓龙筋SPA
@yhuajzlj88 · 8,4653 posts深圳东莞按摩聊天吹水
@z2728822 · 8793 posts福田名师·しよう 疗愈抓龙筋交流群
@cc66889886 · 1,4352 posts罗湖MM岚岚姐
@frewqz · 9062 posts极搜🔍资源搜索@JISOU
@jisou2 · 2,457,7282 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.
Handles this channel named that no longer answer
- Dead references
- 3
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 3
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@Szxiuchehui named 3 handles 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, 8 August 2026 – 10 September 2026 · confirmed gone 1 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 4 September 2026 – 4 September 2026 · confirmed gone 4 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 31 August 2026 – 31 August 2026 · confirmed gone 5 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“深圳修车联盟会公开榜🥇” (@Szxiuchehui), 43,065 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/Szxiuchehui.
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.