Telegram 中文圈搜索引擎,积木 JIMU 帮你查询任何您想要的群组、频道(不论公开与私密) 🧩 积木:@jimu · @jimux · @jimuxx 👉 所有入口都能助力提升排名🚀

Channel
成都楼凤阁丨车库
@cdrbl
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
35,024subscribers
+9,989 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001996773094 |
|---|---|
| Type | Channel |
| Username | @cdrbl |
| Description | 本群唯一客服 @lfgcgn1_bot 成都日不落:https://t.me/chendurbl 成都楼凤阁 https://t.me/cdlfls 楼凤阁频道 https://t.me/cdrbl 日不落频道 https://t.me/cdrblck |
| Created | Between 1 October 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 58 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/cdrbl |
Topic
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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 |
|---|---|---|
| 16 Nov 2026, 08:36 | 35,024 | +671 |
| 12 Nov 2026, 23:19 | 34,353 | +505 |
| 10 Nov 2026, 13:46 | 33,848 | +160 |
| 8 Nov 2026, 23:00 | 33,688 | +202 |
| 7 Nov 2026, 15:17 | 33,486 | +175 |
| 6 Nov 2026, 13:27 | 33,311 | +169 |
| 5 Nov 2026, 12:39 | 33,142 | +261 |
| 4 Nov 2026, 10:49 | 32,881 | +118 |
| 3 Nov 2026, 12:41 | 32,763 | +73 |
| 2 Nov 2026, 14:05 | 32,690 | +322 |
| 1 Nov 2026, 11:00 | 32,368 | +142 |
| 31 Oct 2026, 14:06 | 32,226 | +209 |
| 30 Oct 2026, 11:17 | 32,017 | +124 |
| 29 Oct 2026, 14:41 | 31,893 | +247 |
| 28 Oct 2026, 12:04 | 31,646 | +290 |
| 27 Oct 2026, 09:36 | 31,356 | +142 |
| 26 Oct 2026, 08:36 | 31,214 | +250 |
| 25 Oct 2026, 09:50 | 30,964 | +265 |
| 24 Oct 2026, 13:19 | 30,699 | +125 |
| 23 Oct 2026, 12:55 | 30,574 | first reading |
Engagement
80 posts held, back to 8 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 160 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.95%
- avg views ÷ 35,024 subscribers
- Avg views / post
- 681
- 36 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 36
- of 80 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.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 80 (8 August 2026 – 16 November 2026) |
| Views total | 24,529 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 23:07 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,220
- Videos
- ≈102
- Links
- ≈214
Lifetime counters from Telegram’s own channel header, read 16 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
- 2m 25s
- Average length
- 10s
Measured directly from 14 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 36 posts held from the last 30 days (0%) 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).
#桃花朵儿 #成华区 #嫩妹 #BBW ✨348 车牌: @huaduo592013 👑课时费:4p(50min)7pp(90min)👑 👑#BBW 👑#服务车 👑年龄:21 身高:160 体重:110🐻:C 👑特色:BBW 口活好,态度好👑 👑服务:服务态度好,口活好,菜单上都有👑 👑点评:BBW型嫩妹,服务态度也不错,性价比高,推荐试驾! https://t.me/cdlfls
Telegram 中文圈搜索引擎,积木 JIMU 帮你查询任何您想要的群组、频道(不论公开与私密) 🧩 积木:@jimu · @jimux · @jimuxx 👉 所有入口都能助力提升排名🚀
#成都武侯 #海选会所 🥰云鼎养生SPA店🥰 环境:独立卫浴 ➡️ 情景房 类型:推油spa店 费用:体验价:📱📱📱 贵宾价:📱📱📱 尊享价:📱📱📱 详细项目内容请咨询【琳琳】 🤗每日出勤10➕ 🔣 点击预约客服 🔣 💥特色: ✅性感胸滑 ✅嫦娥之吻 ✅过水漫游 ✅波涛汹涌 ✅蚂蚁上树 ✅三起三落 ✅水漫金山 ✅柔试指滑 ✅猴子偷桃 ✅双宝夹龙 ✅制服诱惑 ✅ ✅正宗莞式18项 只多不少✅ 💥丝袜随便撕 制服随便选💥 📱地址:武侯区来凤二路106号 🚀客服:@CDSPA_92 ❣️双向:@SPA0607bot 🤬群组:@CDSPA92 🥰出勤:@CDSPA93 🌐QQ: 3143419934 😵电话: 13183872608 🀄️微信:smlxhygr (VX同号)
TG必备的搜索引擎,快搜kuai帮你发现有趣群组、频道、视频、音乐、电影、新闻 | Find cool stuff all in one bot! 机器人:@kuai @kuaia @kuaiaa 👉 https://t.me/kuai?start=a_VAC6Q
TG必备的搜索引擎,快搜kuai帮你发现有趣群组、频道、视频、音乐、电影、新闻 | Find cool stuff all in one bot! 机器人:@kuai @kuaia @kuaiaa 👉 https://t.me/kuai?start=a_VAC6Q
Telegram 中文圈搜索引擎,积木 JIMU 帮你查询任何您想要的群组、频道(不论公开与私密) 🧩 积木:@jimu · @jimux · @jimuxx 👉 所有入口都能助力提升排名🚀
#墨涵#青羊区 #少妇 ✨347 车牌: @amh521 👑课时费:5p(50min)8pp(90min)👑 👑#后入 👑年龄:32左右身高:162体重:60🐻C👑 👑特色:后入大屁股体验强,口活好👑 👑服务:陪洗,口活👑 👑点评:老师是个少妇车,健谈喜爱养生。胸大真C随意把玩儿,屁股大适合后入,服务不多,舌功不错,口活好。服务时间不长,不过完事后可以按摩这点很不错。总体来讲性价比偏软。 https://t.me/cdlfls
Telegram 中文圈搜索引擎,积木 JIMU 帮你查询任何您想要的群组、频道(不论公开与私密) 🧩 积木:@jimu · @jimux · @jimuxx 👉 所有入口都能助力提升排名🚀
TG必备的搜索引擎,快搜kuai帮你发现有趣群组、频道、视频、音乐、电影、新闻 | Find cool stuff all in one bot! 机器人:@kuai @kuaia @kuaiaa 👉 https://t.me/kuai?start=a_VAC6Q
#徐冬冬 #武侯区#少妇 ✨346 车牌: @yezi030305 👑课时费:6p(50min)10pp(90min) 👑#服务车 👑年龄:28身高:160体重:105🐻38D👑 👑特色:毒龙无敌,胸又大又软,皮肤滑嫩嫩的👑 👑服务:会所级别,很全面舌头很软👑 👑点评:金品少妇车,服务态度好,服务技术全面,身材属于微胖丰满,人还带点害羞,配合度高,适合懂玩的狼友,喜欢服务车的也可以体验。 https://t.me/cdlfls
#喜儿 #成华区 #御姐 ✨345 车牌: @Yxcdmu55 👑课时费:7p(60min)12pp(90min)👑 👑#御姐车 👑#人工白虎 👑年龄:24身高:162体重:48kg🐻C👑 👑特色:腿长,乳交👑 👑服务:嫩妹三件套 乳交 👑 👑点评:长相有点异域风情,跟照片有个八分相似,说话声音有点夹夹,性子慢半拍,脾气良好,没有什么服务,有很多的纹身,有明显的小肚子,但身材丰臀肥乳,做爱动情,情绪价值给的很足,整体来说还是值得推荐的! https://t.me/cdlfls
Showing the 12 most recent of 80 posts we hold for @cdrbl. 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 26 posts on @cdrbl 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
- 16 August 2026
- Most recent seen missing
- 9 November 2026
- Median time before seen missing
- 27 hours
- Seen missing in the last 30 days
- 5
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.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@cdrbl named 1 handle 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 6 posts, 16 August 2026 – 4 November 2026
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“成都楼凤阁丨车库” (@cdrbl), 35,024 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/cdrbl.
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.