Channel
CC的小窝💞
@yushen122
On this record: Topic · Growth · Engagement · Citations · Cite this entry
1,436subscribers
+1,102 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003255635877 |
|---|---|
| Type | Channel |
| Username | @yushen122 |
| Description | 频道 : @yushen122 群组: @cc0809clt 精品报告及防： @cc080921pd 双向机器人： @yushen121_bot 爱神丘比特的缘分：https://t.me/+Ts5zBi2-5nFmMjJl |
| First recorded | 29 September 2026 |
| Last confirmed live | 29 September 2026 |
| Measurements held | 11 |
| On Telegram | t.me/yushen122 |
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 29 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 29 Sept 2026, 03:19 | 1,436 | no change |
| 28 Sept 2026, 06:19 | 1,436 | +65 |
| 18 Sept 2026, 19:39 | 1,371 | +101 |
| 14 Sept 2026, 00:39 | 1,270 | +213 |
| 10 Sept 2026, 16:38 | 1,057 | +232 |
| 1 Sept 2026, 11:55 | 825 | +102 |
| 26 Aug 2026, 00:24 | 723 | +225 |
| 19 Aug 2026, 17:08 | 498 | +65 |
| 13 Aug 2026, 11:26 | 433 | +98 |
| 7 Aug 2026, 02:07 | 335 | +1 |
| 6 Aug 2026, 20:03 | 334 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Mentions
Named by 12 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.
@lotteryln · 63,2885 postsLotteryBest抽奖导航
@lotterynav · 174,1785 posts隔壁老王的回忆录
@lwgeo · 8,6832 posts深圳东莞公开榜
@ShenZhen_68 · 22,0782 posts深圳枫林晚优惠福利🧧
@youhuila · 9,7742 posts深圳欢乐谷【公开榜】
@HLGGB · 22,1341 postPaPa玛特达人榜
@papma002 · 14,9541 post派大星抽奖优惠活动频道
@pdxdcjzl · 16,0101 post深圳修车大队LY之声
@szlym · 9,2081 post深圳少女御姐报告集
@SZsnqstl · 15,5621 post深圳【汤臣一品】精选榜
@tcypa5 · 65,2791 post深圳高牌红中约炮榜
@xog888 · 16,0081 post
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 29 September 2026 — this entry's latest reading, not the date you are reading this.
“CC的小窝💞” (@yushen122), 1,436 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/yushen122.
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.