Telegram RegisterThe public register of Telegram
Telegram profile photo for 常州永动机老师公开榜

Channel

常州永动机老师公开榜

@Czgrls

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

4,313subscribers

+1,005 since we began measuring on 27 August 2026

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

Register entry

Telegram ID-1002292572824
TypeChannel
Username@Czgrls
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 August 2026
Last confirmed live18 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/Czgrls

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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

3,3084,3133,810.527 August 2026 — 3,308 subscribers27 August 2026 — 3,308 subscribers27 August 2026 — 3,321 subscribers30 August 2026 — 3,444 subscribers2 September 2026 — 3,546 subscribers6 September 2026 — 3,740 subscribers11 September 2026 — 3,925 subscribers14 September 2026 — 4,119 subscribers18 September 2026 — 4,313 subscribers27 August 202618 September 2026
9 measurements spanning 23 days, net +1,005. 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 3,157–4,464 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 22:014,313+194
14 Sept 2026, 23:184,119+194
11 Sept 2026, 05:173,925+185
6 Sept 2026, 05:583,740+194
2 Sept 2026, 08:083,546+102
30 Aug 2026, 14:583,444+123
27 Aug 2026, 22:343,321+13
27 Aug 2026, 07:003,308no change
27 Aug 2026, 06:453,308first reading

Engagement

5 posts held, back to 25 October 2025 — 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 21 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
16s
Average length
8s

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.

Reaction mix

11 reactions across 2 posts, in 1 kind.

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

Measured over the 5 most recent posts we hold, published 25 October 2025 to 21 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

21 Aug 2026, 04:20 UTC305 viewsread 27 August 2026
Photo

#常州 #新北区 #常州小丽 艺名 # 小丽(36E) 位置 #常州市新北区 课费 #600/p 1200/pp 服务 : https://t.me/xiaoxiao1122331 联系方式 :@xiaoxiao1122346 投稿管理: @Yongdongji88_bot 常州永动机总群:https://t.me/Cztthecha

4 Mar 2026, 13:49 UTC≈2,850 viewsread 27 August 2026
Photo

#常州 #湖塘 #萱萱 艺名 #萱萱 位置 #常州市武进区 课费 #700/P #1400/PP 服务 :https://t.me/Xuanxuan_66 联系方式 :@Xuanxuan_77 投稿管理: @Yongdongji88_bot 常州永动机总群:https://t.me/Cztthecha

31 Jan 2026, 12:57 UTC≈3,610 views4 reactionsread 27 August 2026
Photo

#常州 #湖塘 #沐颜 艺名 #沐颜 位置 #常州市武进区 课费 #600/P #1100/PP 服务 :https://t.me/muyan_1314 联系方式 :@mu520yan 投稿管理: @Yongdongji88_bot 常州永动机总群:https://t.me/Cztthecha

❤4

27 Jan 2026, 16:01 UTC≈3,360 viewsread 27 August 2026
Photo

#常州 #天宁区 #菲菲 艺名 #菲菲 位置 #常州市天宁区 课费 #600/P #1200/PP 服务 :https://t.me/Czfeifei 联系方式 :@feifei33445 投稿管理: @Yongdongji88_bot 常州永动机总群:https://t.me/Cztthecha

25 Oct 2025, 08:06 UTC≈5,520 views7 reactionsread 27 August 2026
Photo

#常州 #天宁 #小鑫 艺名 #小鑫 位置 #天宁区 课费 #400/P #600/PP 服务 :https://t.me/xiaoooxinnn 联系方式 :@xiaoooxinn 投稿管理: @Yongdongji88_bot 常州永动机总群:https://t.me/Cztthecha

❤7

Showing the 5 most recent of 5 posts we hold for @Czgrls. 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.

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.

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

“常州永动机老师公开榜” (@Czgrls), 4,313 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Czgrls.

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.