Telegram RegisterThe public register of Telegram
Telegram profile photo for 宇宙自然博物馆

Channel

宇宙自然博物馆

@manhuadao04

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

19,916subscribers

+4,570 since we began measuring on 16 August 2026

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

Register entry

Telegram ID-1002698507973
TypeChannel
Username@manhuadao04
CreatedBetween 1 April 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 August 2026
Last confirmed live5 September 2026
Measurements held18
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/manhuadao04

Growth

15,34619,91617,63116 August 2026 — 15,346 subscribers17 August 2026 — 15,614 subscribers18 August 2026 — 15,873 subscribers19 August 2026 — 16,145 subscribers20 August 2026 — 16,476 subscribers22 August 2026 — 16,857 subscribers24 August 2026 — 17,341 subscribers25 August 2026 — 17,534 subscribers26 August 2026 — 17,770 subscribers27 August 2026 — 17,912 subscribers28 August 2026 — 18,094 subscribers29 August 2026 — 18,277 subscribers30 August 2026 — 18,478 subscribers31 August 2026 — 18,696 subscribers1 September 2026 — 19,028 subscribers2 September 2026 — 19,230 subscribers3 September 2026 — 19,474 subscribers5 September 2026 — 19,916 subscribers16 August 20265 September 2026
18 measurements spanning 20 days, net +4,570. 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 14,661–20,602 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 15:5919,916+442
3 Sept 2026, 16:5519,474+244
2 Sept 2026, 08:4719,230+202
1 Sept 2026, 07:3819,028+332
31 Aug 2026, 06:5518,696+218
30 Aug 2026, 08:5418,478+201
29 Aug 2026, 05:1618,277+183
28 Aug 2026, 07:1318,094+182
27 Aug 2026, 06:3617,912+142
26 Aug 2026, 07:3217,770+236
25 Aug 2026, 04:1317,534+193
24 Aug 2026, 00:2317,341+484
22 Aug 2026, 09:2416,857+381
20 Aug 2026, 22:3616,476+331
19 Aug 2026, 19:0716,145+272
18 Aug 2026, 15:3315,873+259
17 Aug 2026, 13:1715,614+268
16 Aug 2026, 14:3115,346first reading

Engagement

21 posts held, back to 16 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 33 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.41%
avg views ÷ 19,916 subscribers
Avg views / post
480
21 posts measured
Reaction rate
2.53%
reactions ÷ views · ER floor
Posts in window
21
of 21 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 17 of 21 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 1 September 2026
Posts held21 (16 August 20261 September 2026)
Views total10,089
Reactions total212
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 01:32 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.

Reaction mix

212 reactions across 17 posts, in 1 kind.

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

Measured over the 21 most recent posts we hold, published 16 August 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, 05:47 UTC326 views13 reactionsread 3 September 2026
Photo

这是金星,由阿雷西博射电望远镜拍摄的图像

13

1 Sept 2026, 05:46 UTC324 views12 reactionsread 3 September 2026
Photo

大自然的惊人力量。 这张照片是在内布拉斯加州的一场雷暴中拍摄的。

12

1 Sept 2026, 05:46 UTC297 views12 reactionsread 3 September 2026
Photo

北极熊,在极光下。 加拿大,丘吉尔。

12

23 Aug 2026, 17:20 UTC≈1,040 views16 reactionsread 3 September 2026
Photo

中国火箭实现海陆两种回收技术突破 中国可重复使用火箭近期连续取得关键进展。朱雀三号遥二运载火箭完成发射后,一子级通过着陆腿实现陆地可控回收,这是中国首次完成入轨级运载火箭一子级着陆腿方式陆地回收。 此前长征十号乙已完成海上网系回收验证,两种不同技术路线相继取得突破,意味着中国重复使用运载火箭正在从试验验证向更加完整的工程体系推进。火箭回收能力也是未来降低商业航天发射成本、提高发射频率的重要基础。 央视新闻

16

23 Aug 2026, 17:19 UTC826 views12 reactionsread 3 September 2026
Photo

中国嫦娥七号月球南极任务推迟发射 中国原定于 8 月 24 日执行的嫦娥七号任务已推迟。Space报道称,文昌发射场附近天气条件恶化,中国方面确认此次任务目前不满足发射条件,因此不会按照原定窗口实施。 嫦娥七号是中国探月工程四期的重要任务,由轨道器、着陆器、巡视器和飞跃器等组成,重点探索月球南极并寻找水冰。任务原计划使用长征五号遥十四运载火箭发射,新的发射窗口目前尚未公布。 Space.com

12

23 Aug 2026, 17:16 UTC615 views12 reactionsread 3 September 2026
Photo

在华盛顿州圣海伦火山上空的银河系 ✨ 📸 克里斯托弗·C·沃克

12

23 Aug 2026, 17:15 UTC457 views12 reactionsread 3 September 2026
Photo

西班牙一座拥有800年历史的教堂,正值日全食

12

23 Aug 2026, 17:14 UTC292 views12 reactionsread 3 September 2026
Photo

这是一张M15-52脉冲星风云星云的合成图像,看起来像一只幽灵般的手。 这种类型的星云被称为“普勒离子”(plerion)。 它们通常存在于超新星遗迹的壳层内部,由中心脉冲星产生的脉冲星风所驱动。 著名的蟹状星云是这种现象的另一个例子。

12

23 Aug 2026, 17:14 UTC300 views12 reactionsread 3 September 2026
Photo

新西兰塔拉纳基山顶上,雄伟的仙女座星系遥相对比

12

23 Aug 2026, 17:14 UTC300 views12 reactionsread 3 September 2026
Photo

令人难以置信的景色,就在坠毁的道格拉斯DC-3飞机事故现场附近。 冰岛,索尔黑马山地。

12

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

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

“宇宙自然博物馆” (@manhuadao04), 19,916 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/manhuadao04.

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.