Telegram RegisterThe public register of Telegram
Telegram profile photo for 常州轻奢嫩妹

Channel

常州轻奢嫩妹

@changzhounvyou

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

11,598subscribers

+610 since we began measuring on 19 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002196149511
TypeChannel
Username@changzhounvyou
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 August 2026
Last confirmed live3 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/changzhounvyou

Growth

10,98811,59811,29319 August 2026 — 10,988 subscribers20 August 2026 — 11,041 subscribers21 August 2026 — 11,070 subscribers23 August 2026 — 11,140 subscribers24 August 2026 — 11,209 subscribers26 August 2026 — 11,241 subscribers27 August 2026 — 11,284 subscribers28 August 2026 — 11,356 subscribers29 August 2026 — 11,404 subscribers30 August 2026 — 11,441 subscribers31 August 2026 — 11,459 subscribers1 September 2026 — 11,500 subscribers2 September 2026 — 11,538 subscribers3 September 2026 — 11,598 subscribers19 August 20263 September 2026
14 measurements spanning 15 days, net +610. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 10,897–11,690 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 09:1811,598+60
2 Sept 2026, 04:2511,538+38
1 Sept 2026, 04:2411,500+41
31 Aug 2026, 05:4211,459+18
30 Aug 2026, 06:2311,441+37
29 Aug 2026, 03:4311,404+48
28 Aug 2026, 03:1811,356+72
27 Aug 2026, 00:4411,284+43
26 Aug 2026, 00:2411,241+32
24 Aug 2026, 23:1611,209+69
23 Aug 2026, 07:1311,140+70
21 Aug 2026, 17:2711,070+29
20 Aug 2026, 17:2311,041+53
19 Aug 2026, 18:4510,988first reading

Engagement

36 posts held, back to 12 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 22 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.13%
avg views ÷ 11,598 subscribers
Avg views / post
711
36 posts measured
Reaction rate
0.074%
reactions ÷ views · ER floor
Posts in window
36
of 36 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. It is computed over the 14 of 36 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 August 2026
Posts held36 (12 August 202628 August 2026)
Views total25,582
Reactions total10
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 23:51 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

Video runtime
3m 46s
Average length
6s

Measured directly from 35 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.

Reaction mix

10 reactions across 8 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10100.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 14 of the 36 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 10 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 36 most recent posts we hold, published 12 August 2026 to 28 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.

Recent posts

28 Aug 2026, 06:13 UTC≈1,390 views1 reactionsread 2 September 2026
Photo

视频真实 1500p (一小时) 2800pp (两小时) 3500✌️(22:30开始8个小时) 无套+300 见面满意付,不满意可换,可以上门也有自己的房间,约课领取位置时间直接转发此条消息给⬇️ 免费客服:@huanyingchanglai 双向限制:@qiuqiuxiaosaohuo_bot

1

28 Aug 2026, 06:13 UTC≈1,230 viewsread 2 September 2026
Photo

视频真实 1500p (一小时) 2800pp (两小时) 3500✌️(22:30开始8个小时) 无套+300 见面满意付,不满意可换,可以上门也有自己的房间,约课领取位置时间直接转发此条消息给⬇️ 免费客服:@huanyingchanglai 双向限制:@qiuqiuxiaosaohuo_bot

28 Aug 2026, 06:12 UTC933 views0 reactionsread 2 September 2026
Photo

视频真实 1500p (一小时) 2800pp (两小时) 3500✌️(22:30开始8个小时) 无套+300 见面满意付,不满意可换,可以上门也有自己的房间,约课领取位置时间直接转发此条消息给⬇️ 免费客服:@huanyingchanglai 双向限制:@qiuqiuxiaosaohuo_bot

28 Aug 2026, 06:12 UTC754 viewsread 2 September 2026
Photo

视频真实 1500p (一小时) 2800pp (两小时) 3500✌️(22:30开始8个小时) 无套+300 见面满意付,不满意可换,可以上门也有自己的房间,约课领取位置时间直接转发此条消息给⬇️ 免费客服:@huanyingchanglai 双向限制:@qiuqiuxiaosaohuo_bot

28 Aug 2026, 06:12 UTC649 viewsread 2 September 2026
Photo

视频真实 1500p (一小时) 2800pp (两小时) 3500✌️(22:30开始8个小时) 无套+300 见面满意付,不满意可换,可以上门也有自己的房间,约课领取位置时间直接转发此条消息给⬇️ 免费客服:@huanyingchanglai 双向限制:@qiuqiuxiaosaohuo_bot

28 Aug 2026, 06:12 UTC570 viewsread 2 September 2026
Photo

视频真实 1500p (一小时) 2800pp (两小时) 3500✌️(22:30开始8个小时) 无套+300 见面满意付,不满意可换,可以上门也有自己的房间,约课领取位置时间直接转发此条消息给⬇️ 免费客服:@huanyingchanglai 双向限制:@qiuqiuxiaosaohuo_bot

28 Aug 2026, 06:12 UTC522 views1 reactionsread 2 September 2026
Photo

视频真实 1500p (一小时) 2800pp (两小时) 3500✌️(22:30开始8个小时) 无套+300 见面满意付,不满意可换,可以上门也有自己的房间,约课领取位置时间直接转发此条消息给⬇️ 免费客服:@huanyingchanglai 双向限制:@qiuqiuxiaosaohuo_bot

1

28 Aug 2026, 06:11 UTC504 viewsread 2 September 2026
Photo

视频真实 1500p (一小时) 2800pp (两小时) 3500✌️(22:30开始8个小时) 无套+300 见面满意付,不满意可换,可以上门也有自己的房间,约课领取位置时间直接转发此条消息给⬇️ 免费客服:@huanyingchanglai 双向限制:@qiuqiuxiaosaohuo_bot

28 Aug 2026, 06:11 UTC489 viewsread 2 September 2026
Photo

视频真实 1500p (一小时) 2800pp (两小时) 3500✌️(22:30开始8个小时) 无套+300 见面满意付,不满意可换,可以上门也有自己的房间,约课领取位置时间直接转发此条消息给⬇️ 免费客服:@huanyingchanglai 双向限制:@qiuqiuxiaosaohuo_bot

28 Aug 2026, 06:11 UTC525 viewsread 2 September 2026
Photo

视频真实 1500p (一小时) 2800pp (两小时) 3500✌️(22:30开始8个小时) 无套+300 见面满意付,不满意可换,可以上门也有自己的房间,约课领取位置时间直接转发此条消息给⬇️ 免费客服:@huanyingchanglai 双向限制:@qiuqiuxiaosaohuo_bot

26 Aug 2026, 11:34 UTC610 views0 reactionsread 27 August 2026
Photo

🎟 抽奖标题: 自选半价券 1..本次抽奖为乐透模式【多抽多中】 2..需要 10KFC 积分参与抽奖 3.有效期至2026年9月3号 4.最终解释权归 常州娱乐城 所有 5.中奖后联系 @emooost 完成兑换 6.抽奖口令:一起爽玩 7.签到:大吉大利 8.参与主群: @changzhouylc 9.半价券:车友会在榜老师【即时半价奖池】 👉👉👉.参与主群: @changzhouylc 👉👉👉#发言1%概率随机掉落 10. 50. 100积分,双倍积分卡,专属小尾巴 👉👉👉每日积分398上限 👉👉👉开启图片功能 👉👉👉开启,老虎机,炸金花,牛牛,快3,21点等游戏 👉👉👉连续签到10天奖励100分,连续签到20天奖励200分。 👉👉👉增加日发言量达300,增加50积分 👉👉👉以上规则为试行版本,后续将根据实际情况调整 消耗积分: 10 积分 定时开奖 2026-08-31 21:00:00 参与关键词: 一起爽

22 Aug 2026, 09:41 UTC≈1,320 views2 reactionsread 27 August 2026
Photo

视频真实 1500p (一小时) 2800pp (两小时) 3500✌️(22:30开始8个小时) 无套+300 见面满意付,不满意可换,可以上门也有自己的房间,约课领取位置时间直接转发此条消息给⬇️ 免费客服:@huanyingchanglai 双向限制:@qiuqiuxiaosaohuo_bot

2

Showing the 12 most recent of 36 posts we hold for @changzhounvyou. 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 edited after publishing

@changzhounvyou edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
27 August 2026
Most recent edit
27 August 2026

Mentions

Named by 4 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.

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 3 September 2026 — this entry's latest reading, not the date you are reading this.

“常州轻奢嫩妹” (@changzhounvyou), 11,598 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/changzhounvyou.

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.