天津24.168.55C奶主播,可口可无,3天7k,全国飞,新人听话,皮肤好

Channel
短期选妃
@ccca55888
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
4,374subscribers
-1,985 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1003663148550 |
|---|---|
| Type | Channel |
| Username | @ccca55888 |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 1 October 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 1 October 2026 |
| On Telegram | t.me/ccca55888 |
Topic
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Oct 2026, 19:55 | 4,374 | -264 |
| 16 Sept 2026, 12:00 | 4,638 | -89 |
| 12 Sept 2026, 10:39 | 4,727 | -71 |
| 8 Sept 2026, 18:16 | 4,798 | -245 |
| 3 Sept 2026, 09:04 | 5,043 | -607 |
| 30 Aug 2026, 17:55 | 5,650 | -360 |
| 27 Aug 2026, 10:26 | 6,010 | -57 |
| 24 Aug 2026, 19:56 | 6,067 | -47 |
| 21 Aug 2026, 07:38 | 6,114 | -36 |
| 18 Aug 2026, 11:02 | 6,150 | -60 |
| 15 Aug 2026, 17:55 | 6,210 | -71 |
| 12 Aug 2026, 07:58 | 6,281 | -62 |
| 8 Aug 2026, 22:00 | 6,343 | -16 |
| 8 Aug 2026, 03:15 | 6,359 | first reading |
Engagement
35 posts held, back to 3 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 6 pages 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 35 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 13s
- Average length
- 7s
Measured directly from 2 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
陕西西安 20 D🐻 雪生 性价比三天5k 🉑口 🉑sm 🉑无🍑 妹妹经济紧张 不事B 紧致水多 性欲旺盛 🐻大配合高 颜🐍、👅阴/肛、控制高、情趣玩具等等…妹妹放假了空着,看上的老板找我拿资料
BBw 巨乳 屁股大 听话 可以轻微调教 年纪小 性价比高 下面又紧又嫩 云南昆明 20 大胸E杯 500一天,性价比拉满
这几天在深圳 甜美可爱大学生 放暑假了 四天五千 性价比今天可见
湖南长沙 18/163/90 B杯 🉑口、sm、无🍑 活泼可爱开朗 清纯少女 不事B 紧紧紧 乳头粉而敏感 会喷水 配合度高 各种穿搭随便驾驭 🉑🛩️
广东珠海 02/160/80 幼师 3天6k 🉑口 可提供情绪价值 听话漂亮 配合度高 皮肤滑 XSH少紧水多 看上的找我拿资料
武汉 21/170/118 C🐻 雪生刚毕业 清纯听话 事少 圈子小/干净 很少接触异性 BB紧 会穿搭
河南23/170/90 C杯 模特顶美 三天2个 🉑口 🉑SM 🉑外省 声音好听 性格温柔 紧致水多 会打配合 看上的老板找我拿资料
四川成都 05/171/92 美牙职业 🉑口 🉑无🍑 大长腿 御姐小顶 成熟玩得开 听话B紧紧 人比照片好看 🉑飞
广东广州 20/157/82 A 性价比3天5k 🉑无🍑 清纯妹紧B 看上的哥哥找我拿资料
陕西西安 20 D🐻 雪生 性价比三天5k 🉑口 🉑sm 🉑无🍑 妹妹经济紧张 不事B 紧致水多 性欲旺盛 🐻大配合高 颜🐍、👅阴/肛、控制高、情趣玩具等等…妹妹放假了空着,看上的老板找我拿资料
河南 23/164/95 B🐻 雪生在读 🉑口、无🍑 🉑外省 会唱歌跳舞 情绪价值拉满 听话温柔坦诚直率 个人圈子干净 事少
Showing the 12 most recent of 35 posts we hold for @ccca55888. 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.
Forward network
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.
Mentions
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.
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 1 October 2026 — this entry's latest reading, not the date you are reading this.
“短期选妃” (@ccca55888), 4,374 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/ccca55888.
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.