Channel
@CDPC168
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,381subscribers
+207 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004413063144 |
|---|---|
| Type | Channel |
| Username | @CDPC168 |
| Created | Between 1 June 2026 and 19 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/CDPC168 |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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 |
|---|---|---|
| 18 Sept 2026, 02:40 | 1,381 | +21 |
| 14 Sept 2026, 07:57 | 1,360 | +24 |
| 11 Sept 2026, 02:01 | 1,336 | +38 |
| 6 Sept 2026, 05:19 | 1,298 | +19 |
| 1 Sept 2026, 20:26 | 1,279 | +26 |
| 29 Aug 2026, 12:53 | 1,253 | +15 |
| 26 Aug 2026, 20:54 | 1,238 | +19 |
| 24 Aug 2026, 00:23 | 1,219 | +34 |
| 20 Aug 2026, 02:17 | 1,185 | +11 |
| 19 Aug 2026, 13:15 | 1,174 | no change |
| 19 Aug 2026, 13:00 | 1,174 | first reading |
9 posts held, back to 19 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.
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 19 August 2026. An engagement rate over an empty window would be a number about nothing.
高质量00后全套💥💥💥优惠价 998爱爱1️⃣🔥，70分钟 1098爱爱2️⃣🔥，90分钟 1398爱爱2️⃣🔥，90分钟+丝袜制服+毒🐉 位置：熊猫采采耳·可视采耳馆(奥园店) 四川省成都市成华区万年场街道崔家店南路147号 ❗️❗️❗️位置每天更新，过来之前请提前预约，避免跑空 #成华区 #东门 #全套 #奥园广场 #工作室 预约联系： @akpl0314 双向联系： @cdxl168_bot
半套💥💥💥优惠价 550👄1️⃣，70分钟半裸 700👄1️⃣，90分钟全裸 位置：蒙顶黄芽 四川省成都市武侯区二环路南一段一号1栋 ❗️❗️❗️位置每天更新，过来之前请提前预约，避免跑空 #武侯区 #南门 #会所 #半套 预约联系： @akpl0314 双向联系： @cdxl168_bot
半套💥💥💥优惠价 550👄1️⃣，70分钟半裸 700👄2️⃣，90分钟全裸 全套💥💥💥优惠价 998爱爱1️⃣🔥，70分钟 1198爱爱2️⃣🔥，90分钟 1398爱爱2️⃣🔥，90分钟+丝袜制服+毒🐉 位置：成都琥珀阳光酒店 四川省成都市双流区九江街道五桐路13号11栋201号 ❗️❗️❗️位置每天更新，过来之前请提前告知，避免跑空 #双流区 #会所 #全套 #半套 预约联系： @akpl0314 双向联系： @cdxl168_bot
🈶泡澡🛀🏻 半套💥💥💥优惠价 600👄1️⃣，70分钟半裸 700👄2️⃣，90分钟全裸 位置：时尚嚞里 四川省成都市双流区新通大道777号(新通大道地铁站A口步行420米) ❗️❗️❗️位置每天更新，过来之前请提前告知，避免跑空 #双流区 #会所 #半套 预约联系： @akpl0314 双向联系： @cdxl168_bot
半套💥💥💥优惠价 550👄1️⃣，70分钟半裸 700👄2️⃣，90分钟全裸 全套💥💥💥优惠价 998爱爱1️⃣🔥，70分钟 1198爱爱2️⃣🔥，90分钟 1398爱爱2️⃣🔥，90分钟+丝袜制服+毒🐉 位置：兰汀茶馆(桐梓林店) 四川省成都市武侯区火车南站街道航空路7号锦官新城华尔兹广场2楼7号 ❗️❗️❗️位置每天更新，过来之前请提前告知，避免跑空 #南门 #南站 #桐梓林 #全套 #半套 #工作室 预约联系： @akpl0314 双向联系： @cdxl168_bot
半套💥💥💥优惠价 550👄1️⃣，70分钟半裸 全套💥💥💥优惠价 898爱爱1️⃣🔥，70分钟 1098爱爱2️⃣🔥，90分钟 1298爱爱2️⃣🔥，90分钟+丝袜制服+毒🐉 位置：皓玟口腔 四川省成都市新都区保利广场2栋停车场入口处 ❗️❗️❗️位置每天更新，过来之前请提前告知，避免跑空 #新都区 #工作室 #全套 #半套 #大丰 预约联系： @akpl0314 双向联系： @cdxl168_bot
半套💥💥💥优惠价 500👄1️⃣，70分钟半裸 630👄2️⃣，90分钟全裸 全套💥💥💥优惠价 898爱爱1️⃣🔥，70分钟 1098爱爱2️⃣🔥，90分钟 1298爱爱2️⃣🔥，90分钟+丝袜制服+毒🐉 位置：兴潮手机维修 四川省成都市新都区蓉都大道南四段传化·国际新城东侧约290米 ❗️❗️❗️位置每天更新，过来之前请提前告知，避免跑空 #新都区 #工作室 #全套 #半套 预约联系： @akpl0314 双向联系： @cdxl168_bot
海选全套💥💥💥优惠价 1198爱爱1️⃣🔥，70分钟 1398爱爱2️⃣🔥，90分钟 位置：蓝润·华府春天-西北门 四川省成都市双流区西航港街道蓝润·华府春天 位置每天更新，过来之前请提前告知，避免跑空 #双流区 #海选 #全套 #会所 预约联系： @akpl0314 双向联系： @cdxl168_bot
全套💥💥💥优惠价 998爱爱1️⃣🔥，70分钟 1198爱爱2️⃣🔥，90分钟 1398爱爱2️⃣🔥，90分钟+丝袜制服+毒🐉 位置：熊猫采采耳·可视采耳馆(奥园店) 四川省成都市成华区万年场街道崔家店南路147号 ❗️❗️❗️位置每天更新，过来之前请提前告知，避免跑空 #成华区 #东门 #全套 #奥园广场 #工作室 预约联系： @akpl0314 双向联系： @cdxl168_bot
Showing the 9 most recent of 9 posts we hold for @CDPC168. 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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“【成都半套】【成都全套】95、98成都会所｜一手资源｜🔥🔥🔥” (@CDPC168), 1,381 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/CDPC168.
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.