Telegram RegisterThe public register of Telegram
Telegram profile photo for 老葉的科普天地

Channel

老葉的科普天地

@yehPopSci

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

396subscribers

-10 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001323192462
TypeChannel
Username@yehPopSci
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live3 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/yehPopSci

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

3964064018 August 2026 — 406 subscribers8 August 2026 — 406 subscribers10 September 2026 — 401 subscribers18 September 2026 — 398 subscribers3 October 2026 — 396 subscribers8 August 20263 October 2026
5 measurements spanning 57 days, net -10. 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 395–408 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 20:41396-2
18 Sept 2026, 09:20398-3
10 Sept 2026, 06:00401-5
8 Aug 2026, 05:46406no change
8 Aug 2026, 00:20406first reading

Engagement

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

Recent posts

6 Aug 2026, 01:35 UTC26 viewsread 8 August 2026

只要談到清朝中後期的歷史,經常可以看到一種說法: 「如果永琪沒有早死,由他繼承皇位,大清或許不會衰敗。」 這類假設乍看很合理:某位皇子比較聰明、比較有才華,那麼由他來當皇帝,似乎就會更好。 問題是,這種說法經常建立在一個虛無的假設上! 怎麼說呢? 看文章:https://vocus.cc/article/6a73c81ffd897800018fcc85

3 Aug 2026, 01:23 UTC42 viewsread 8 August 2026

在讀嘉慶的《御製詩》時,我覺得其中有一首最可愛。 這首詩是在嘉慶七年,他出發去熱河,接著去木蘭圍場進行秋獮的時候作的。 他寫了什麼呢? 看文章:https://vocus.cc/article/6a6fe073fd89780001c9fefc

29 Jul 2026, 00:23 UTC66 viewsread 8 August 2026

談到乾隆為何選了嘉慶,很多人的印象都是: 因為永琪早逝,永珹、永瑢已經出繼,剩下幾位皇子,又各有缺點。 因此,永琰只是那位「相對最沒有問題」的人。 但是,真的是這樣嗎? (7/30轉入付費) 看文章:https://vocus.cc/article/6a6894cffd897800017ef213

24 Jul 2026, 03:18 UTC77 viewsread 8 August 2026

看到「嘉慶與《快雪時晴帖》」這個標題,應該有人會說:說錯了吧?應該是乾隆吧? 沒說錯喔!我的確是要說嘉慶!來看一下吧! 看文章:https://vocus.cc/article/6a62d25ffd897800011a020d

23 Jul 2026, 00:18 UTC63 viewsread 8 August 2026

近年來,《甄嬛傳》《延禧攻略》《如懿傳》等戲劇,把清朝後宮描繪成一座充滿陰謀的競技場。 下毒、栽贓、收買宮女、扶植皇子、拉攏朝臣……每個人都在鬥 但是,如果真正回頭看制度,會發現清朝的皇帝們,其實花了很多力氣,來抑制宮鬥喔! 看文章:https://vocus.cc/article/6a6062e9fd897800019d0458

22 Jul 2026, 00:09 UTC53 viewsread 8 August 2026

小說之外:為什麼博爾濟吉特能走,輝發那拉不能? 在《白鸚鵡》小說中提到: 順治帝的廢后靜妃,回到了科爾沁草原。 為什麼她能回去、繼后卻只能在宮中了此殘生呢? 看文章:https://vocus.cc/article/6a5f48f7fd897800015b8a69

21 Jul 2026, 00:12 UTC47 viewsread 8 August 2026

白鸚鵡(三十):只能這樣了 隨駕南巡,每日早晚進膳,皇帝照例賞菜、太監菜名報得極順溜,但是她卻覺出另一層意思來——原來連自己,也不過是這樣被照例分進去的一個人。 不是問她要不要,也不是記得她愛不愛。只是輪到她,便有她那一份。 看文章:https://vocus.cc/article/6a5d8167fd897800013d9456

20 Jul 2026, 00:36 UTC50 viewsread 8 August 2026

上次提到劉統勳一輩子就做了這麼一次的冊封使副使,讓我想到阿桂。 他是乾隆晚期的軍機處首席,而且以不買和珅的帳出名。 但是...他被叫去當冊封典禮正使...這可是要念詔書的啊... 看文章:https://vocus.cc/article/6a5c688afd897800011b952b

19 Jul 2026, 00:15 UTC47 viewsread 8 August 2026

之前提到乾隆的雙標。 輪到自己時,二十七個月續絃都嫌太快;輪到嘉慶時,卻急著宣布「中宮不可久曠」,要兒子現在、立刻、馬上冊封皇貴妃。 原本我以為,故事大概就到這裡。 沒想到,還有後續... 看文章:https://vocus.cc/article/6a5b2168fd89780001d29af6

18 Jul 2026, 00:30 UTC50 viewsread 8 August 2026

白鸚鵡(二十九):只因應節弗宜多 皇帝看了她一眼,沒有再說什麼,轉身便走。 她只覺得耳邊一陣極輕的嗡鳴,像有人在很遠很遠的地方敲了一下鐘,聲音傳到這裡時,已經只剩迴響了。可她臉上的笑竟還能撐住... 看文章:https://vocus.cc/article/6a598997fd89780001de79fe

16 Jul 2026, 01:02 UTC52 viewsread 8 August 2026

小說之外:永琪不是天生主角,而是被火場照亮的人 在許多連續劇裡,五阿哥永琪聰明、俊秀、得寵,好像天生就是那種會在後宮與皇子群中脫穎而出的主角。然而,若回頭細看史料,這種印象其實缺乏早期證據支持。 怎麼說呢?來看看吧! 看文章:https://vocus.cc/article/6a57778cfd897800012dca79

15 Jul 2026, 00:09 UTC57 viewsread 8 August 2026

小說之外的彩蛋:一場可能存在過的君臣拉鋸 當我看到,令妃封貴妃時,副使居然是被乾隆稱讚「乃不愧真宰相」的劉統勳,而且他只當了那麼一次,我就忍不住幻想... 看文章:https://vocus.cc/article/6a562ba9fd897800010a2df7

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

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

“老葉的科普天地” (@yehPopSci), 396 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/yehPopSci.

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.