Telegram RegisterThe public register of Telegram
Telegram profile photo for 常州龙城🅥认证榜

Channel

常州龙城🅥认证榜

@yxtczy

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

20,113subscribers

+6,654 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1001494243859
TypeChannel
Username@yxtczy
CreatedBetween 1 June 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live26 October 2026
Measurements held41
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/yxtczy

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

13,45920,11316,78614 August 2026 — 13,459 subscribers16 August 2026 — 13,576 subscribers17 August 2026 — 13,618 subscribers18 August 2026 — 13,670 subscribers19 August 2026 — 13,755 subscribers20 August 2026 — 13,851 subscribers22 August 2026 — 13,907 subscribers23 August 2026 — 13,981 subscribers24 August 2026 — 14,097 subscribers25 August 2026 — 14,034 subscribers27 August 2026 — 14,107 subscribers28 August 2026 — 14,204 subscribers29 August 2026 — 14,269 subscribers30 August 2026 — 14,328 subscribers31 August 2026 — 14,383 subscribers1 September 2026 — 14,459 subscribers2 September 2026 — 14,439 subscribers3 September 2026 — 14,478 subscribers5 September 2026 — 14,614 subscribers8 September 2026 — 14,686 subscribers11 September 2026 — 14,780 subscribers13 September 2026 — 14,807 subscribers15 September 2026 — 14,812 subscribers17 September 2026 — 15,015 subscribers19 September 2026 — 15,300 subscribers26 September 2026 — 15,976 subscribers4 October 2026 — 17,056 subscribers9 October 2026 — 17,590 subscribers13 October 2026 — 18,282 subscribers14 October 2026 — 18,502 subscribers15 October 2026 — 18,507 subscribers16 October 2026 — 18,678 subscribers17 October 2026 — 18,799 subscribers18 October 2026 — 19,089 subscribers19 October 2026 — 19,281 subscribers20 October 2026 — 19,465 subscribers22 October 2026 — 19,654 subscribers23 October 2026 — 19,750 subscribers24 October 2026 — 19,856 subscribers25 October 2026 — 20,008 subscribers26 October 2026 — 20,113 subscribers14 August 202626 October 2026
41 measurements spanning 73 days, net +6,654. 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 12,461–21,111 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 41
Measured (UTC)SubscribersChange
26 Oct 2026, 10:3720,113+105
25 Oct 2026, 12:5620,008+152
24 Oct 2026, 09:5919,856+106
23 Oct 2026, 09:4419,750+96
22 Oct 2026, 07:2119,654+189
20 Oct 2026, 22:4919,465+184
19 Oct 2026, 19:1719,281+192
18 Oct 2026, 18:4819,089+290
17 Oct 2026, 19:3718,799+121
16 Oct 2026, 20:2718,678+171
15 Oct 2026, 16:5818,507+5
14 Oct 2026, 20:0618,502+220
13 Oct 2026, 09:3618,282+692
9 Oct 2026, 06:5717,590+534
4 Oct 2026, 17:2017,056+1,080
26 Sept 2026, 18:1915,976+676
19 Sept 2026, 14:3615,300+285
17 Sept 2026, 03:1915,015+203
15 Sept 2026, 02:0114,812+5
13 Sept 2026, 08:5514,807first reading

Engagement

22 posts held, back to 24 May 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 33 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 22 posts for this entry, the most recent from 1 September 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3m 25s
Average length
12s

Measured directly from 17 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

19 reactions across 11 posts, in 2 distinct kinds. The most used accounts for 94.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1894.7%
😁15.26%

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 15 of the 22 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 19 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 24 May 2026 to 1 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.

Recent posts

1 Sept 2026, 07:44 UTC670 views0 reactionsread 2 September 2026
Photo

👩🏻‍💼艺名: 迪妹 📍地址:常州/武进区 p800 pp1600 📱电报:点击获取📱双向:双向联系 📜车评:开始撰写👀车评:查看车评 ✳️常州龙城交流群总群 📊 0条车评,综合评分 好评 0% |人照 |服务

31 Aug 2026, 04:13 UTC436 views1 reactionsread 2 September 2026
Photo

👩🏻‍💼艺名: 奶牛 📍地址:常州/武进区 p700 pp1400 📱电报:点击获取📱双向:双向联系 📜车评:开始撰写👀车评:查看车评 ✳️常州龙城交流群总群 📊 0条车评,综合评分 好评 0% |人照 |服务

❤1

27 Aug 2026, 06:13 UTC844 views0 reactionsread 2 September 2026
Photo

👩🏻‍💼艺名: 绿萝 📍地址:常州/武进区 p500 pp1000 📱电报:点击获取📱双向:双向联系 📜车评:开始撰写👀车评:查看车评 ✳️常州龙城交流群总群 📊 0条车评,综合评分 好评 0% |人照 |服务

26 Aug 2026, 05:44 UTC822 views1 reactionsread 2 September 2026
Photo

👩🏻‍💼艺名: 潘金莲 📍地址:常州/天宁区 p400 pp800 📱电报:点击获取📱双向:双向联系 📜车评:开始撰写👀车评:查看车评 ✳️常州龙城交流群总群 📊 0条车评,综合评分 好评 0% |人照 |服务

❤1

25 Aug 2026, 08:34 UTC799 viewsread 2 September 2026
Photo

👩🏻‍💼艺名: 甜宝 📍地址:常州/武进区 p600 pp1100 📱电报:点击获取📱双向:双向联系 📜车评:开始撰写👀车评:查看车评 ✳️常州龙城交流群总群 📊 0条车评,综合评分 好评 0% |人照 |服务

25 Aug 2026, 06:08 UTC644 viewsread 31 August 2026
Photo

👩🏻‍💼艺名: 糖宝 📍地址:常州/武进区 p600 pp1100 📱电报:点击获取📱双向:双向联系 📜车评:开始撰写👀车评:查看车评 ✳️常州龙城交流群总群 📊 1条车评,综合评分8.5 好评 0% |人照 8 |服务 8

24 Aug 2026, 09:10 UTC581 views1 reactionsread 30 August 2026
Photo

👩🏻‍💼艺名: 曼语 📍地址:常州/新北区 p700 pp1400 📱电报:点击获取📱双向:双向联系 📜车评:开始撰写👀车评:查看车评 ✳️常州龙城交流群总群 📊 0条车评,综合评分 好评 0% |人照 |服务

❤1

24 Aug 2026, 08:08 UTC332 viewsread 27 August 2026
Photo

👩🏻‍💼艺名: 雪儿 📍地址:常州/新北区 p800 pp1600 📱电报:点击获取📱双向:双向联系 📜车评:开始撰写👀车评:查看车评 ✳️常州龙城交流群总群 📊 0条车评,综合评分 好评 0% |人照 |服务

24 Aug 2026, 06:14 UTC191 viewsread 25 August 2026
Photo

👩🏻‍💼艺名: 妮妮 📍地址:常州/新北区 p600 pp1100 📱电报:点击获取📱双向:双向联系 📜车评:开始撰写👀车评:查看车评 ✳️常州龙城交流群总群 📊 0条车评,综合评分 好评 0% |人照 |服务

23 Aug 2026, 10:26 UTC303 views1 reactionsread 25 August 2026
Photo

👩🏻‍💼艺名: 18岁小小 📍地址:常州/武进区 p600 pp1200 📱电报:点击获取📱双向:双向联系 📜车评:开始撰写👀车评:查看车评 ✳️常州龙城交流群总群 📊 0条车评,综合评分 好评 0% |人照 |服务

❤1

23 Aug 2026, 07:52 UTC194 viewsread 24 August 2026
Photo

👩🏻‍💼艺名: 崽崽 📍地址:常州/武进区 p800 pp1600 📱电报:点击获取📱双向:双向联系 📜车评:开始撰写👀车评:查看车评 ✳️常州龙城交流群总群 📊 0条车评,综合评分 好评 0% |人照 |服务

23 Aug 2026, 06:46 UTC183 viewsread 24 August 2026
Photo

👩🏻‍💼艺名: 白虎 📍地址:常州/武进区 p800 pp1600 📱电报:点击获取📱双向:双向联系 📜车评:开始撰写👀车评:查看车评 ✳️常州龙城交流群总群 📊 0条车评,综合评分 好评 0% |人照 |服务

Showing the 12 most recent of 22 posts we hold for @yxtczy. 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

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.

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

“常州龙城🅥认证榜” (@yxtczy), 20,113 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/yxtczy.

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.