Channel
@chenchenyouxuan1
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
3,422subscribers
+30 since we began measuring on 2 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002161160876 |
|---|---|
| Type | Channel |
| Username | @chenchenyouxuan1 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/chenchenyouxuan1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 17:58 | 3,422 | +14 |
| 12 Sept 2026, 02:37 | 3,408 | +18 |
| 2 Sept 2026, 18:04 | 3,390 | -2 |
| 2 Sept 2026, 15:15 | 3,392 | first reading |
18 posts held, back to 27 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.
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 1 of 18 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 18 (27 August 2026 – 2 September 2026) |
| Views total | 2,916 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 15:15 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.
Measured directly from 1 video 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 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 1 of the 18 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 27 August 2026 to 2 September 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.
😃😀🤓🈷️😔日出击排位😀😃... （营业时间14:00-23:00） 客服统一工作时间:11:00-23:30 好评推送区：https://t.me/LL20250907 欢迎大家进入📱QQ群：1063818716 （备注电报即可通过验证）怕vpn掉线 ‼️ Safex:@CQlanlan （苹果应用商店可下载） 安卓下载地址： safex.im 类似电报不需要梯子 🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 🙂江渝北（😀😃湖畔）💸💸💸💸 头牌学妹【针不戳】8/16🈳 萝御双修【揪咪】6/11🈳 销魂情人【秦无双】7/13🈳 尚品拾陆 人如其名【水多多】5/9🈳 预约联系👉👍客服: 澜澜 1️⃣双向私信：@CQhupanlanlan3_bot 🙂🙂🙂🙂🙂🙂 🙂🙂🙂🙂🙂 两江新区直通车（力帆时代 北岸铂寓 珠江一号） 🙂北岸铂寓（人多 更多请咨询澜澜） 嫩妹⬇️⬇️ …
（😀😃-湖畔） 🤓🈷️😔渝北😘 头牌学妹【针不戳】8/16🈳 萝御双修【揪咪】6/11🈳 销魂情人【秦无双】7/13🈳 预约联系👉👍客服: 澜澜 1️⃣双向私信：@CQhupanlanlan3_bot 1️⃣聊天群：https://t.me/cclm288 🈺业时间14:00-23:00💭 欢迎大家进入📱QQ群：1063818716 （备注电报即可通过验证）怕vpn掉线 ‼️ Safex:@CQlanlan （苹果应用商店可下载） 安卓下载地址： safex.im 类似电报不需要梯子
兜兜转转还是她 胸大屁股大 敏感 水多泛滥。温柔 又配合 像朋友，像情人像初恋 冉家坝雪儿 预约联系👉👍客服: 澜澜 双向私信：@CQhupanlanlan3_bot 1️⃣聊天群：https://t.me/cclm288 欢迎大家进入📱QQ群：1063818716 （备注电报即可通过验证）怕vpn掉线 ‼️ Safex:@CQlanlan （苹果应用商店可下载） 安卓下载地址： safex.im 类似电报不需要梯子
微电园今日在线 琴琴7。 泡泡7 夏语乐8。 夏语安8
（😀😃-湖畔） 🤓🈷️😔渝北😘 萝御双修【揪咪】6/11🈳 销魂情人【秦无双】7/13🈳 预约联系👉👍客服: 澜澜 1️⃣双向私信：@CQhupanlanlan3_bot
🌈珠江一号🤓🈷️😔日在线 鱼幼薇10。金瓶儿10。 少司缘10 貂蝉9。 海棠青8
冉家坝🤓🈷️😔今日在线 （金易E世界） 奕欢8。 安夏8。 滴滴8。 小依8 如意9。 安若8。 菲儿8。 金蝉8。 白雪8。 阿蛮8。 文文8。 梦溪8。 雪儿8。 星空8 丽莎8。 道奇7 素素8。
🗺🤓🈷️😔日力帆时代在线 谢嘉怡8。 倾心8 欢喜8。 苹果8 幼宁8。 蒙恬9。 嘟嘟9。 诗雅9。 兮颜9。 王妃9 胡青青10。 阮梦雅10
🤓🈷️😔北岸铂寓今日在线 （人员太多，更新不过来 直接私信澜澜） 嫩妹⬇️⬇️ 纯爱9。 樱桃8 西西9。 思语9 荔枝8 周一8 蛋挞9。 呦呦9 思雨8。 梦洛9。 苏珊9 小猫9 小柔8。 诺诺8。 七月8。 悦悦8 茉莉9 梦梦9。 陌陌8 心宝9。 乔竹9。 百合9。 灵儿9 小猫咪9 苏妲己8 苏小喵8 小奶酪8 🙂🙂⬇️⬇️ 糖糖9。 草莓9。 夕月8。 星语9 米苏9。 图图10。 韩妃9。 青玉9 饱饱9 白灵9。 淘淘9 夏千禾9。苏妲己9。 上官曦9。 沈熙妍9。 上官雪9。 安可可9 谢思颖9 苏雨晴9。 宋乐柠9 预约联系👉👍客服: 澜澜 双向私信：@CQhupanlanlan3_bot 1️…
妞妞好评，纹身大胸妹，人照一致，态度也好 预约联系👉👍客服: 澜澜 双向私信：@CQhupanlanlan3_bot 1️⃣聊天群：https://t.me/cclm288 欢迎大家进入📱QQ群：1063818716 （备注电报即可通过验证）怕vpn掉线 ‼️ Safex:@CQlanlan （苹果应用商店可下载） 安卓下载地址： safex.im 类似电报不需要梯子
😃😀😔🈷️😔🤓日出击排位😀😃... （营业时间14:00-23:00） 客服统一工作时间:11:00-23:30 好评推送区：https://t.me/LL20250907 欢迎大家进入📱QQ群：1063818716 （备注电报即可通过验证）怕vpn掉线 ‼️ Safex:@CQlanlan （苹果应用商店可下载） 安卓下载地址： safex.im 类似电报不需要梯子 🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 🙂江渝北（😀😃湖畔）💸💸💸💸 萝御双修【啾咪】6/11🈳 头牌学妹【针不戳】8/16🈳 预约联系👉👍客服: 澜澜 1️⃣双向私信：@CQhupanlanlan3_bot 🙂🙂🙂🙂🙂🙂 🙂🙂🙂🙂🙂 两江新区直通车（力帆时代 北岸铂寓 珠江一号） 💝力帆时代在线 芊妤9。 谢嘉怡8。 倾心8 欢喜8 蒙恬9。 🙂北岸铂寓（人多 更多请咨询澜澜） 嫩妹…
微电园今日在线 琴琴7。 吉丽7 筱雪7 冰冰7 柚子7。 夏语乐8。 夏语安8 熙街今日在线 舒艺7。 舒婷7 宠儿8。 小歪7。 如烟7。
Showing the 12 most recent of 18 posts we hold for @chenchenyouxuan1. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
@chenchenyouxuan1 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.
References a handle that is not a live channel — we have no record it ever was one.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“重庆老师优选推荐” (@chenchenyouxuan1), 3,422 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/chenchenyouxuan1.
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.