Telegram RegisterThe public register of Telegram

Channel

成都修车总群已验车库

@cdswxcck

On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

16,430subscribers

+312 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001367018559
TypeChannel
Username@cdswxcck
Description总群 https://t.me/caotangbiji
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/cdswxcck

Growth

16,11816,43016,2746 August 2026 — 16,118 subscribers6 August 2026 — 16,118 subscribers7 August 2026 — 16,159 subscribers8 August 2026 — 16,242 subscribers9 August 2026 — 16,300 subscribers10 August 2026 — 16,340 subscribers11 August 2026 — 16,375 subscribers12 August 2026 — 16,404 subscribers14 August 2026 — 16,430 subscribers6 August 202614 August 2026
9 measurements spanning 7 days, net +312. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 16,071–16,477 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 00:5716,430+26
12 Aug 2026, 16:2416,404+29
11 Aug 2026, 16:0816,375+35
10 Aug 2026, 13:1216,340+40
9 Aug 2026, 10:1116,300+58
8 Aug 2026, 09:3016,242+83
7 Aug 2026, 08:5316,159+41
6 Aug 2026, 20:1516,118no change
6 Aug 2026, 20:0516,118first reading

Engagement

6 posts held, back to 3 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
7.00%
avg views ÷ 16,430 subscribers
Avg views / post
1,150
6 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
6
of 6 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held6 (3 August 202612 August 2026)
Views total6,903
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 15:54 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
954
Videos
66
Links
210

Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
15s
Average length
15s

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.

Recent posts

12 Aug 2026, 11:29 UTC564 viewsread 14 August 2026
Photo

📊 0条车评 写报告 好评 0% | 人照 | 服务 中评 0% | 颜值 | 态度 差评 0% | 身材 | 环境 花名:#朵朵 编号:150 车牌:@duoduo566 课时费: #5/8 标签:#少妇车 #态度车 #身材车 #服务车 地址:#南门 优惠:无 锐评:温柔少妇,服务很好,皮肤很滑很白,态度好,胸C+手感不错,软件服务很好,喜欢服务车的可以一试。 🦋萝卜青菜,各有所爱🦋 聊天交流 https://t.me/caotangbiji 报告:https://t.me/yinggoubaogao

9 Aug 2026, 07:39 UTC≈1,150 viewsread 14 August 2026
Photo

📊 0条车评 写报告 好评 0% | 人照 | 服务 中评 0% | 颜值 | 态度 差评 0% | 身材 | 环境 花名:#穗穗 编号:179 车牌:@suisuiai520 课时费: #4P/6PP 标签:#少妇车 #态度车 #身材车 #服务车 地址:#东郊记忆 优惠:无 锐评:服务很好,皮肤很滑很白,态度好,胸C+手感不错,软件服务很好,喜欢服务车的可以一试。 🦋萝卜青菜,各有所爱🦋 聊天交流 https://t.me/caotangbiji 报告:https://t.me/yinggoubaogao

6 Aug 2026, 03:01 UTC≈1,590 viewsread 14 August 2026
Photo

📊 0条车评 写报告 好评 0% | 人照 | 服务 中评 0% | 颜值 | 态度 差评 0% | 身材 | 环境 花名:#馨兰 编号:178 车牌: @xinlan771 课时费: #7P 标签:#御姐车 #态度车 #身材车 #颜值车 #模特 #大长腿 地址:#天府三街 优惠:无 锐评:身高175极品身材,腿很长很直很白很细,颜值高皮肤也白,服务多态度好,胸C+手感一般,硬件很顶,软件服务也很好,喜欢大长腿的强烈推荐。 🦋萝卜青菜,各有所爱🦋 聊天交流 https://t.me/caotangbiji 报告:https://t.me/yinggoubaogao

5 Aug 2026, 05:35 UTC≈1,490 viewsread 14 August 2026
Photo

花名:#菲儿 编号:177 车牌: @feier5212 课时费: #5P 标签:#嫩妹车 #态度车 #感觉车 #SM #大蟒蛇 地址:#成华区 优惠: 锐评:19岁的嫩妹进门都是大蟒蛇,妹妹比较敏感反应很自然比较容易到高潮。5p很值得回锅 🦋萝卜青菜,各有所爱🦋 聊天交流 https://t.me/caotangbiji 报告:https://t.me/yinggoubaogao

3 Aug 2026, 17:01 UTC≈1,260 viewsread 12 August 2026
Photo

花名:#馨儿 编号:176 车牌: @xiner66778 课时费: #6p/10pp 标签:#嫩妹 #颜值车 #三点粉嫩 地址:#昭觉寺 优惠:无 锐评:颜值好,上下三点粉嫩!内向听话,很有女友力,6p值得体验 🦋萝卜青菜,各有所爱🦋 聊天交流 https://t.me/caotangbiji 报告:https://t.me/yinggoubaogao

3 Aug 2026, 10:41 UTC849 viewsread 9 August 2026
Photo

📊 0条车评 写报告 好评 0% | 人照 | 服务 中评 0% | 颜值 | 态度 差评 0% | 身材 | 环境 花名:#梦小萱 编号:175 车牌: @mengxiaoxuan22 课时费: #380 标签:#半套 #少妇车 #武侯区 地址:#神仙树 优惠: 锐评:少妇半套车,会所毕业,停车方便,出击累了的兄弟可以去体验体验不一样的出货方式 🦋萝卜青菜,各有所爱🦋 聊天交流 https://t.me/caotangbiji 报告:https://t.me/yinggoubaogao

Showing the 6 most recent of 6 posts we hold for @cdswxcck. 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 edited after publishing

@cdswxcck edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
13 August 2026
Most recent edit
13 August 2026

Citation-graph rank

Citation-graph rank — 963,102 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — 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.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“成都修车总群已验车库” (@cdswxcck), 16,430 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/cdswxcck.

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.