10 May 2026, 06:31 UTC282 viewsread 11 August 2026
https://substack.com/@roylin1003/note/c-256604812?utm_source=notes-share-action&r=7u1j05
Signed 肺拉不堪的阿飽 古書男子🇯🇵
Channel
📚古書慢報🎙Royal Talk Show
@roylin1003talk
On this record: Growth · Engagement · Posts · Citations · Cite this entry
245subscribers
-7 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001258722553 |
|---|---|
| Type | Channel |
| Username | @roylin1003talk |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/roylin1003talk |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 20:59 | 245 | -2 |
| 1 Sept 2026, 05:48 | 247 | -3 |
| 17 Aug 2026, 22:27 | 250 | -2 |
| 11 Aug 2026, 13:04 | 252 | no change |
| 11 Aug 2026, 04:15 | 252 | first reading |
Engagement
20 posts held, back to 5 January 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 10 May 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
10 May 2026, 05:20 UTC276 viewsread 11 August 2026
https://substack.com/@roylin1003/note/c-256590877?utm_source=notes-share-action&r=7u1j05
Signed 肺拉不堪的阿飽 古書男子🇯🇵
15 Apr 2026, 12:58 UTC348 viewsread 11 August 2026
https://vocus.cc/article/69df8878fd89780001af7ea0
Signed 肺拉不堪的阿飽 古書男子🇯🇵
12 Apr 2026, 09:23 UTC243 viewsread 11 August 2026
https://www.kadokado.com.tw/chapter/759533
Signed 肺拉不堪的阿飽 古書男子🇯🇵
11 Apr 2026, 16:45 UTC218 viewsread 11 August 2026
https://www.kadokado.com.tw/chapter/758900
Signed 肺拉不堪的阿飽 古書男子🇯🇵
11 Apr 2026, 13:32 UTC177 viewsread 11 August 2026
https://www.kadokado.com.tw/chapter/758898
Signed 肺拉不堪的阿飽 古書男子🇯🇵
11 Apr 2026, 05:27 UTC155 viewsread 11 August 2026
https://vocus.cc/article/69d9d663fd89780001e4260e
Signed 肺拉不堪的阿飽 古書男子🇯🇵
8 Apr 2026, 10:55 UTC148 viewsread 11 August 2026
https://vocus.cc/article/69d62b3bfd89780001068669
Signed 肺拉不堪的阿飽 古書男子🇯🇵
2 Apr 2026, 05:50 UTC149 viewsread 11 August 2026
https://www.youtube.com/live/8c-GAkIzpGE?si=hoK50ayyON7WTxmV&t=18540 從文明帝國 Sid Meier's Civilization 玩家的觀點，一個偉大的文明應該： 1. 致力於解決國內的問題。 2. 打擊敵國的戰略發展，確保本國優勢。 3. 為人類探索新世界。 目前地球上有 1 個國家符合標準。
Signed 肺拉不堪的阿飽 古書男子🇯🇵
30 Mar 2026, 18:17 UTC117 viewsread 11 August 2026
https://vocus.cc/article/69cab63ffd897800010d39d9
Signed 肺拉不堪的阿飽 古書男子🇯🇵
28 Mar 2026, 14:44 UTC109 viewsread 11 August 2026
https://vocus.cc/article/69c78b68fd89780001419f11
Signed 肺拉不堪的阿飽 古書男子🇯🇵
13 Mar 2026, 18:25 UTC137 viewsread 11 August 2026
# 從古巴到台灣：一場閒聊推導出的國際秩序真相 —- 台灣人享有的自由，不是台灣人爭取來的，也不是國際社會賦予的，而是一個地緣政治的偶然——我們剛好在世界最強國家的戰略利益範圍內。 —- ## 起點：古巴怎麼了？ 2026年初，美國對古巴發動石油封鎖。起因是美國軍事介入委內瑞拉、推翻馬杜羅政權後，開始攔截運往古巴的委內瑞拉石油，並對任何向古巴供油的國家威脅加徵關稅。墨西哥在壓力下暫停了對古巴的石油運輸。 後果是災難性的。停電從幾小時延長到好幾天，路上幾乎沒有車，垃圾堆滿街頭，有人在路邊翻垃圾找食物，包括小孩。聯合國警告可能發生人道主義崩潰。 媒體說，上一次古巴這麼受國際矚目，要追溯到飛彈危機。 好，那我想問一個很天真的問題：聯合國會怎麼做？ ## 六個天真的問題 聯合國會制裁美國嗎？ 不會。美國是安理會常任理事國，擁有否決權。任何針對美國的制裁決議，美國自己就能一票否決。 那派維和部隊去救古巴？ 維和部隊的…
Signed 肺拉不堪的阿飽 古書男子🇯🇵
Showing the 12 most recent of 20 posts we hold for @roylin1003talk. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“📚古書慢報🎙Royal Talk Show” (@roylin1003talk), 245 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/roylin1003talk.
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.