Channel
@chengduhaiwangxiuchecheku1
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
9,377subscribers
+6,699 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002076586391 |
|---|---|
| Type | Channel |
| Username | @chengduhaiwangxiuchecheku1 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/chengduhaiwangxiuchecheku1 |
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 72% 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 |
|---|---|---|
| 17 Sept 2026, 14:40 | 9,377 | +97 |
| 13 Sept 2026, 05:18 | 9,280 | +1,277 |
| 9 Sept 2026, 11:42 | 8,003 | +2,502 |
| 3 Sept 2026, 22:37 | 5,501 | +201 |
| 31 Aug 2026, 03:17 | 5,300 | +2,553 |
| 27 Aug 2026, 22:36 | 2,747 | +69 |
| 27 Aug 2026, 10:15 | 2,678 | no change |
| 27 Aug 2026, 10:00 | 2,678 | first reading |
6 posts held, back to 26 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.
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 27 August 2026 |
|---|---|
| Posts held | 6 (26 August 2026 – 27 August 2026) |
| Views total | 291 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Aug 2026, 10:15 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.
Measured directly from 1 video 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.
4 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 4 | 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 6 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 26 August 2026 to 27 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.
🎰 🎉沈清梨的红包又来咯，快来抢 📮 参与条件： 🛡️ 必须设置用户名 🎫 加入-沈清梨的小圈圈😘 🎫 加入-成都回寝的诱惑（复活版） └🎟️ 发言数大于 3 条 🎫 加入-成都海王修车社区车库（新） 🎫 加入-成都海王修车社区 └🎟️ 发言数大于 3 条 🎫 加入-成都大话修车已验证车库 🎫 加入-成都大话修车群 └🎟️ 发言数大于 3 条 🎁 奖品内容： 💰️ 现金红包100 x 1 💰️ 现金红包50 x 2 💰️ 100元优惠券 x 3 💰️ 海王积分500 x 2 💫 鸿运加成：x 8 规则 ⚠️ 抽奖说明： 1.本次该奖品优惠券不可折现、不可转让、不可买卖；因炸号，退群，注销账号、恶意刷发言发送123字母、非正常聊天，找不到聊天记录等原因，超时未兑换等原的，不予兑奖！ 2.本次活动优惠劵兑奖有效期为开奖后5天内，现金为开奖后2天内，逾期作废。 3·为避免小号、协议号、广告号，需有抽奖期间…
【成都海王修车】 花名: #慧儿 车牌: @zzz1478963 地址: #锦江区 #东大路 价格: p398 硬件：年龄30+，160cm 90斤 身材苗条，胸b-，身材高挑，全身无无赘肉，会聊天,手法专业 优惠情况：暂无 ⭐️类型: #御姐 #态度车 #排骨精 #抓龙筋 #锦江区 总结：态度很好，会聊天，手法专业，会传授相关保养知识！手法专业，态度好，抓龙筋抓的你爽歪歪 https://t.me/chengduhaiwangxiuche
【成都海王修车】 花名:#洋洋 车牌: @qiqitun1 地址: #锦江区 #王府井 价格: 600P/900pp 硬件：24岁左右，167cm 90斤 身材苗条，胸c，身材高挑，全身无无赘肉，没有小肚子，毛毛不多没味道，水水多，会聊天 优惠情况：暂无 ⭐️类型: #御姐 #态度车 #排骨精 #6P #舌吻 #锦江区 总结：态度很好，会聊天，奶子也不错，颜值可以，蟒蛇69管够！身材好，大蟒蛇管饱，会聊天会叫老公，姿势配合，6米还是很不错 https://t.me/chengduhaiwangxiuche
【成都海王修车】 花名: #sala 车牌: @dxlisa 地址: #成华区 价格: 900P/1200pp 硬件：23最岁左右，167cm 110斤 身材苗条，胸B+或C的样子，奶头微褐，全身无明显赘肉，下面一线天，小蝴蝶。 优惠情况：暂无 ⭐️类型: #嫩妹 #感觉车 #9P #代聊 #洋马 #异域风情 推荐理由：颜值高，纯洋马，皮肤不错，爱爱反馈真实。服务不多，无舌无69，价格偏软。情绪价值有待提高！23岁左右的颜值纯洋马车，想体验一下外国妞的狼友可以打卡，不是牙签塞大缸。 https://t.me/chengduhaiwangxiuche
👍4
【成都海王修车】 花名: #喜儿 车牌: @xy3658 地址: #成华区 #理工大 价格: 500P/700PP 硬件：#调情#水中箫#毒龙#69#猴子偷桃#深喉 优惠情况：暂无 ⭐️类型: #少女车 #颜值车 #感觉车 #6P #自聊 #冷白皮 #舌吻 #女友感 推荐理由：服务热情.态度超好.身材很好.不赘肉！老师活泼大方.骚气十足.服务到位.屁股大.后入式真爽 https://t.me/chengduhaiwangxiuche
【成都海王修车】 花名: #毛毛 车牌: @maomao0238 地址: #武侯区 价格: 500P/900pp 硬件：19岁左右，165cm 94斤 身材苗条，胸B，身材高挑，全身无无赘肉，户型正常，水多逼紧。女友感强，情绪价值高。 优惠情况：暂无 ⭐️类型: #嫩妹 #态度车 #排骨精 #5P #代聊 优点：态度很好，听话。自助服务配合度拉满，女友感强，爱爱反馈真实。身材好，大蟒蛇管饱，情绪价值高，配合度拉满。嫩妹车中性价比 比较高，值得回锅那种！ https://t.me/chengduhaiwangxiuche
Showing the 6 most recent of 6 posts we hold for @chengduhaiwangxiuchecheku1. 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.
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.
Named by 3 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“成都海王修车社区已验车库” (@chengduhaiwangxiuchecheku1), 9,377 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/chengduhaiwangxiuchecheku1.
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.