Channel
@cdxcbg1
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,897subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003348397436 |
|---|---|
| Type | Channel |
| Username | @cdxcbg1 |
| Created | Between 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/cdxcbg1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 10:12 | 3,897 | -1 |
| 6 Aug 2026, 20:15 | 3,898 | no change |
| 6 Aug 2026, 20:05 | 3,898 | first reading |
24 posts held, back to 30 July 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 4 pagesof 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. It is computed over the 2 of 23 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 24 (30 July 2026 – 8 August 2026) |
| Views total | 895 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 05:58 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.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 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 2 of the 24 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 30 July 2026 to 8 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.
小蛋挞是邻家感颜值嫩妹，身高165，体重90斤，纯天然无科技，身材高挑苗条，皮肤嫩滑，冷白皮，全身无赘肉，排骨精，大长腿，筷子腿，天然小b凶圆润挺拔，乳头乳晕小，颜色浅，小蝴蝶户型，毛毛浅，颜色浅，内粉，敏感，舔几下就发抖，情绪价值高，会说话不冷场，有陪洗，床上服务虽不多，但是认真体贴，听话，舔凶舔蛋69舌吻都有，爱爱姿势配合，叫声自然，紧，水多，征服感满满。适合嫩妹控，颜值控，蛇蛇精，身材控，大长腿，极品排骨精，感觉控。
Signed 保安
【标签】 #成都 #成都修车 #成都楼凤 #成华区 #态度车 #服务车 #邻家姐妹 #臀浪控 #轻微符文控 【硬件】身高160cm，体重96斤，胸B+，年纪约26岁，毛正常，紧一般，包裹感强 (背、右腿小面积纹身)。 【软件👏👏】鸳鸯浴，🐍吻，无套吹箫，深喉，69，AA、匈莎、指莎、AB漫游。 【课费】6p/60 9pp/90 #6p/9pp (VIP可半价) 【优惠】无 【验证】 报告 1 2 3 4 5 6 【综合评分】：态度/服务: 8.8分 颜值: 8，身材：8，综合: 8.8分。 【新人锐评】 优点: 颜值耐看，去美颜美白人照相符去，细腰臀浪，腰部无赘肉，皮肤润，手感嫩滑紧致Q弹，胸B手感好，乳头米粒带粉，态度好，服务好，技术好，口活厉害，舌头会在牛牛毛量正常，P润水多，包裹感极强，阴道，日感爽翻天，爱爱反馈真实，和声销魂，会聊天，情绪价值极高。 瑕疵: 床不经折腾，嘎吱嘎吱响 …
Signed 保安
一直看老师频道，好评颇多，今天终于约到头课，迫不及待出击，老师在酒店公寓，环境好，颜值不错，服务态度很好，口技过关，态度服务很好，说话温柔，还有战袍可选，非常值得出击，爱爱反馈真实，很有欲望，总的来说性价比不错
Signed 保安
【类型标签】： 【妹子花名】：馨兰 【妹子车牌】：@xinlan771 【验证留名】：九弟 【验证时间】：8月6号 【所在位置】：天府三街 【修车水费】：700p 【是否代聊】：代聊 【身高身材】：175.110 【妹子年龄】: 25左右 【湿度紧度】: 紧，水也多，很烫 【颜值相似】：9分 【凶器罩杯】：c样子 【环境卫生】：干净 【服务内容】：陪洗，口，AB面，很棒 【机车行为】：无 【优点缺点】：优点：态度非常好，身材好 【性价比 】：9分 【推荐程度】：9.5 评分标准 6分为及格，7分为良品（考虑价格可以看一看），8分（值得价格并且建议体验），9分（实为该价位中少见的精品），9分（极品） 【服务详情】：进门看见老师属实有点惊艳，我个人觉得还是挺好看的！很含蓄，很娇羞，就是那种感觉，话不多，但是一个劲的微笑，让人看着很舒服！坐下来之后，先是一顿搂搂抱抱，不得不说，妹子的身材很不错，胸不是很大，但是很挺，屁屁也…
Signed 保安
【标签】 #成都 #成都修车 #成都楼凤 #武侯区 #御姐车 #态度车 #大长腿 #身材车 #御姐 #颜值车 #邻家姐姐 #新疆异域风情 #眼神莎 【硬件】身高约168cm，体重86斤，胸B，年纪约28岁左右，毛正常，紧正常，包裹感强 (无纹身)。 【软件👏👏】 基础按摩，臀莎、指莎、匈莎、无套吹箫，深喉，舔🥚，AA、毒🐲 【课费】700p/50 1000pp/80 #7p/10pp (VIP可半价) 【优惠】无 【验证】 报告 1 2 3 4 5 6 【综合评分】：态度/服务: 8.5分 颜值: 8.5，身材：8.5 ，综合: 8.5分。 【新人锐评】 优点: 颜值韵味御姐，祛美白美颜人照相符合，细腰臀浪，腰部无赘肉，大长腿，皮肤白皙，手感嫩、滑、紧致Q弹，胸B手感好、软，乳头葡萄，态度好，服务好，口活厉害绕舌，舌头在牛牛上跳舞，毛量正常，批正常、水多， B烫 包裹感强，AA反馈真实，美声销魂，…
Signed 保安
根据老师指挥，准时来到教室，老师特意留门，不需要敲门。上下打量老师，颜值不错，没有赘肉，衣着有品，坐沙发上简单交流，交水费开始陪洗。褪去衣服，老师全身皮肤触感丝滑，陪洗过程很仔细，老师比较讲究卫生，自身清洗也很认真。擦净后，老师换上黑色性感吊带，眼前一亮，躺平开始服务，指滑，舔胸，🐍，69，口，一气呵成行云流水，口技很好，时间很久，不喊停不得停，而且舌头会打转，很吸阳气😂，感觉快招架不住了，戴t开始传教士，老师已完全湿润，丝滑进入，小穴很烫，日感很不错，老师开始不停呻吟，换女上来，动作幅度大，二弟全部没入洞里，女上疯狂摇摆，差点弄出来，最后背枪，屁股挺大的，冲击感很强，老师已骚到不行，BB紧致会收缩，有点受不了了，在猛力的冲击中成功交货。趴老师背上慢慢享受这愉快的时光，陪洗后坐沙发聊天，这是为数不多的本狼交货后还愿意留下来聊天的老师，时间差不多了，吻别老师，满意的出击。
Signed 保安
成都星辰楼凤修车群专用报告模板 基础信息 【妹子花名】：#馨兰 【妹子车牌】：@xinlan771 【验证留名】：@berogo_993 【验证时间】：8.5 【所在位置】：中和 【修车水费】：7p/10pp 【是否代聊】： 是 硬件🤤🤤 【身高体重】：身高175cm，体重100 斤，无纹身，皮肤光滑，小腹平坦 【妹子年龄】：28 【湿度紧度昆感】：蝴蝶毛量一般，无异味逼紧适中 【人照相似】：9 分 【颜值打分】：9 分 （6分及格，8分班花，9分 小网红，碰见想要微信那种） 【凶器罩杯】：天然C+胸 乳头中等大小，吊钟奶类型天然柔软 软件❤️❤️ 【环境卫生】：适合打车或者驾车前往，小区出入和停车方便，房间干净整洁 【服务内容】：陪洗，口，无舌，69 ，AB 面 爱爱 【机车行为😓】：无 综合 【优点缺点】：优点: 175 大长腿大奶御姐网红脸高颜值，吊钟原装 C+大奶手感柔软可玩性高，同时小腹平坦皮肤光滑…
Signed 保安
老师去掉美颜就是本人，脸型轮廓，人照8.2分吧，美颜明显，本人稍胖，身高还是比较高了，大大的一只，身材还行，皮肤白嫩细腻，真胸无科技，反馈真实，提前跟代哥约好时间，准时到达，位置还算好找，按照代哥给的房号上楼，进门一看，大大的一只，可能由于我身高比较矮，感觉老师很高，加上高跟鞋，有175左右，一个吊带裙子胸漏在眼前，白花花的，瞬间有感觉了，没聊几句，由于老师爱笑，就自然熟悉了起来，老师提鞋主动一起洗澡，互相洗澡配合默契，洗的仔细，接着躺床上，玩玩老师的大奶子，舔了舔，老师瞬间来感觉了，接着摸了摸下边，老师颤抖不行，由于嫩妹，昨天才过来，基本上没啥服务，折腾了一会儿，几个姿势下来，累的不行，结束。 总结：整体来说，硬件方面老师168的净身高穿着恨天高应该在175左右，体重115，身材凹凸有致，不算胖，胸前有一块小纹身，真大白胸无科技，手感细腻柔软，下面人工白虎，户型蝴蝶柔软粉嫩，软件方面：老师态度没得说，配合度高，一次性卫浴都有…
Signed 保安
【个人发挥👷👷】 今日终得闲出击，几十天前就认识安老师了，当时就200米距离，可惜今日远了不少，不过好在安老师值得，口活好，媚眼如丝，身体软软，配合度高，值得推荐。
Signed 保安
老师去掉美颜就是本人，脸型轮廓，人照8.2分吧，美颜明显，本人稍胖，身高还是比较高了，大大的一只，身材还行，皮肤白嫩细腻，真胸无科技，反馈真实，提前跟代哥约好时间，准时到达，位置还算好找，按照代哥给的房号上楼，进门一看，大大的一只，可能由于我身高比较矮，感觉老师很高，加上高跟鞋，有175左右，一个吊带裙子胸漏在眼前，白花花的，瞬间有感觉了，没聊几句，由于老师爱笑，就自然熟悉了起来，老师提鞋主动一起洗澡，互相洗澡配合默契，洗的仔细，接着躺床上，玩玩老师的大奶子，舔了舔，老师瞬间来感觉了，接着摸了摸下边，老师颤抖不行，由于嫩妹，昨天才过来，基本上没啥服务，折腾了一会儿，几个姿势下来，累的不行，结束。 总结：整体来说，硬件方面老师168的净身高穿着恨天高应该在175左右，体重115，身材凹凸有致，不算胖，胸前有一块小纹身，真大白胸无科技，手感细腻柔软，下面人工白虎，户型蝴蝶柔软粉嫩，软件方面：老师态度没得说，配合度高，一次性卫浴都有…
Signed 保安
基础信息 【妹子花名】：#奶酥 【妹子车牌】：@ns851 【验证留名】：#柠檬水 【验证时间】：7月 【所在位置】：#武侯区 #高升桥 【修车水费】：#7P #12PP 【是否代聊】：#代聊 【本报告是否为返现报告】：否 硬件评价 【妹子年龄】：20 【身材皮肤】：身高160，体重46kg，身材不错，肤色偏白，皮肤手感还可以 【胸器信息】：奶子b+，奶头花生米，肉肉有弹性 【鲍鱼信息】：蝴蝶型，颜色浅，外褐里粉，毛少，水多润滑有包裹感 【颜值相似】：人照8.5分，眼睛妹，文艺范 【颜值打分】：8.5分（6分及格，7分小美，8分班花，9分小网红，10分女神） 软件评价 【环境卫生】：交通方便，房间整洁干净 【服务内容】：陪洗，调情，口活，舌吻，爱爱 【机车行为】：无 综合评价 【优点缺点】：优点：眼睛妹很有文艺范，态度超级好，一直笑呵呵，颜值也不错，身材很有诱惑力，主动大蟒蛇，调情也非常听话，下面水多润滑，包裹感强…
Signed 保安
成都星辰楼凤修车群专用报告模板 基础信息 【妹子花名】：#安安 【妹子车牌】：@ananmmya 【验证留名】：@yifan_c 【验证时间】：8.3 【所在位置】：昭觉寺 【修车水费】：7p/12pp 【是否代聊】： 是 硬件🤤🤤 【身高体重】：身高160cm，体重102斤，年纪20岁，无纹身，皮肤光滑 【妹子年龄】：20 【湿度紧度昆感】：蝴蝶户型外褐内粉，毛量偏多，敏感炫批无异味，逼紧水多 【人照相似】：8分， （窗前那张） 【颜值打分】：8分 （6分及格，8分班花，9分 小网红，碰见想要微信那种） 【凶器罩杯】：天然C胸 乳头很小偏粉嫩，胸型圆润挺拔 软件❤️❤️ 【环境卫生】：交通一般，距离地铁1000米左右，适合打车或者驾车前往，小区出入方便，房间干净 【服务内容】：陪洗，口，舌吻，69 ，爱爱 【机车行为😓】：无 综合 【优点缺点】：优点: 大胸嫩妹，皮肤嫩滑，胸C手感好，乳头很小粉嫩，态度好…
Signed 保安
Showing the 12 most recent of 24 posts we hold for @cdxcbg1. 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.
Citation-graph rank — 290,688 of 1,169,250entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 2 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“成都星辰报告” (@cdxcbg1), 3,897 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/cdxcbg1.
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.