Telegram RegisterThe public register of Telegram
Telegram profile photo for 云初频道

Channel

云初频道

@yunchu_0

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

4,635subscribers

+2,959 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1004384074789
TypeChannel
Username@yunchu_0
CreatedBetween 1 June 2026 and 1 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/yunchu_0

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

1,6764,6353,155.57 August 2026 — 1,676 subscribers7 August 2026 — 1,676 subscribers8 August 2026 — 1,940 subscribers11 August 2026 — 2,342 subscribers14 August 2026 — 2,775 subscribers18 August 2026 — 2,990 subscribers21 August 2026 — 3,189 subscribers25 August 2026 — 3,419 subscribers28 August 2026 — 3,631 subscribers30 August 2026 — 3,758 subscribers2 September 2026 — 3,886 subscribers6 September 2026 — 4,083 subscribers11 September 2026 — 4,277 subscribers14 September 2026 — 4,453 subscribers19 September 2026 — 4,635 subscribers7 August 202619 September 2026
15 measurements spanning 42 days, net +2,959. 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 1,232–5,079 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 01:174,635+182
14 Sept 2026, 22:584,453+176
11 Sept 2026, 03:584,277+194
6 Sept 2026, 16:004,083+197
2 Sept 2026, 12:253,886+128
30 Aug 2026, 19:473,758+127
28 Aug 2026, 02:353,631+212
25 Aug 2026, 02:363,419+230
21 Aug 2026, 11:533,189+199
18 Aug 2026, 03:022,990+215
14 Aug 2026, 22:572,775+433
11 Aug 2026, 10:032,342+402
8 Aug 2026, 13:351,940+264
7 Aug 2026, 21:021,676no change
7 Aug 2026, 19:191,676first reading

Engagement

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

Reaction mix

68 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 48.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣3348.5%
2232.4%
🖕811.8%
🤮45.88%
🥱11.47%

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

Measured over the 6 most recent posts we hold, published 1 August 2026 to 7 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

7 Aug 2026, 15:22 UTC282 views1 reactionsread 7 August 2026

📢 系统通知 ━━━━━━━━━━━━ 云初机器人已恢复正常运营状态 ━━━━━━━━━━━━

1

6 Aug 2026, 17:39 UTC752 views4 reactionsread 7 August 2026

@yunchufr_bot 工商法人机器人 自助法人全号机器人 0.5USDT 查询🔍 法人股东 3u 出单联系 @xhwdxb

4

2 Aug 2026, 01:48 UTC≈2,340 views15 reactionsread 7 August 2026

🚀云初 🔐 免费核验机器人。支持身份证二要素核验、有效期核验,运营商三要素,手机二要素核验,法人四要素核验,支付宝二要素核验,银行卡三要素核验,人脸核验带对比度,身份证正反面生成,盖章个户生成,PLC个户生成,开户行查询,婚姻状态查询 更多功能等你体验...... 长期收购支付宝核验接口如: 支付宝二要素核验和支付宝三要素核验 单次核验就够 ✅ 支持签到 推荐🔥🔥 云初新频道 @yunchu_0 云初新群聊 @yunchu520 以前的频道群聊被盗了 云初机器人 @yunchu_bot 永久用户名 @yunchu_0

7🤣7🥱1

1 Aug 2026, 16:00 UTC≈1,850 views33 reactionsread 7 August 2026

马上恢复云初机器人 旧频道群聊荒废处理

🤣207🖕5🤮1

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

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

“云初频道” (@yunchu_0), 4,635 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/yunchu_0.

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.