Telegram RegisterThe public register of Telegram
Telegram profile photo for 停班停課最新通知 🇹🇼 Taiwan Alerts

Channel

停班停課最新通知 🇹🇼 Taiwan Alerts

@TaiwanAlerts

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

8,967subscribers

-14 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001429383034
TypeChannel
Username@TaiwanAlerts
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live2 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/TaiwanAlerts

Growth

8,8748,9818,927.56 August 2026 — 8,981 subscribers6 August 2026 — 8,981 subscribers7 August 2026 — 8,956 subscribers10 August 2026 — 8,884 subscribers13 August 2026 — 8,889 subscribers16 August 2026 — 8,874 subscribers20 August 2026 — 8,881 subscribers23 August 2026 — 8,929 subscribers27 August 2026 — 8,953 subscribers29 August 2026 — 8,950 subscribers2 September 2026 — 8,967 subscribers8,9676 August 20262 September 2026
11 measurements spanning 26 days, net -14. 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 8,858–8,997 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 06:448,967+17
29 Aug 2026, 20:148,950-3
27 Aug 2026, 03:358,953+24
23 Aug 2026, 22:258,929+48
20 Aug 2026, 04:228,881+7
16 Aug 2026, 18:078,874-15
13 Aug 2026, 11:598,889+5
10 Aug 2026, 20:448,884-72
7 Aug 2026, 20:238,956-25
6 Aug 2026, 20:458,981no change
6 Aug 2026, 20:398,981first reading

Engagement

138 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 30 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
18.1%
avg views ÷ 8,967 subscribers
Avg views / post
1,620
114 posts measured
Reaction rate
0.809%
reactions ÷ views · ER floor
Posts in window
114
of 138 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 108 of 114 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 28 August 2026
Posts held138 (1 August 202628 August 2026)
Views total185,098
Reactions total1,437
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 15:49 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.

What this channel posts

Video runtime
35s
Average length
35s

Measured directly from 1 video 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

1,866 reactions across 131 posts, in 30 distinct kinds. The most used accounts for 28.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍53328.6%
34718.6%
👌25013.4%
🤣1779.49%
😱1689.00%
🙏1196.38%
😁482.57%
👀331.77%
🤔331.77%
💩261.39%
🔥191.02%
👏180.965%
😢180.965%
🫡120.643%
🤷‍♂90.482%
😍80.429%
😨60.322%
😭60.322%
🙉60.322%
🌭50.268%
10 further kinds251.34%

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

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

Telegram Stars

Stars received
9
across the posts below
Posts paid on
2
of 138 we hold a reading for · 1%
Most on one post
8
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @TaiwanAlerts. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 138 most recent posts we hold for this entry, published 1 August 2026 to 28 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

28 Aug 2026, 12:44 UTC774 views6 reactionsread 28 August 2026
Photo

🌦️【#天氣小叮嚀|大低壓帶仍活躍 留意熱帶擾動發展】 大家準備迎接週末的同時,也可以稍微留意一下接下來的天氣變化! 目前從南海一路到臺灣東方海面,仍是範圍相當廣大的低壓帶,也已經可以觀察到一些熱帶系統發展的訊號。 不過,現在還只是非常 #初期 的階段,後續會如何發展仍有待觀察,暫時不用過度擔心,持續留意最新天氣資訊就好。 祝福大家週末愉快!(愉快關機放假去~) 〔發布❯❯2026-08-28∙20:44〕

2👌2👍2

28 Aug 2026, 06:19 UTC≈1,030 views13 reactionsread 28 August 2026
Photo

✅【颱風 #沙德爾 海上颱風警報解除】 中央氣象署今(28)日14時30分解除輕度颱風「沙德爾」海上颱風警報。 雖然颱風警報已解除,中南部地區仍受到風場影響,局部地區可能出現較大雨勢,提醒大家外出仍應留意天氣變化及自身安全。 隨著颱風警報解除,這也是我們對「沙德爾」颱風的最後一篇報導。 〔發布❯❯2026-08-28∙14:20〕

9👍3👌1

28 Aug 2026, 05:14 UTC≈1,100 views16 reactionsread 28 August 2026
Photo

🌀【颱風 #班朗 生成】 根據日本氣象廳最新觀測,今年第22號(還記得台灣跟日本差一號嗎XD)颱風「班朗」(BANG-LANG)生成,對台灣沒有影響。 而且是「班朗」不是「檳...榔...」更不是「BANG BANG BANG」。 〔發布❯❯2026-08-28∙10:32〕

😁15💯1

28 Aug 2026, 04:11 UTC≈1,130 views20 reactionsread 28 August 2026

💬【#小編的話|十幾年前只是課本名詞,如今卻成了我們正在經歷的現實】 猶記十多年前,還在念國、高中時,看到課本裡寫著「極端氣候」、「全球暖化」、「氣候變遷」,其實真的沒有太多感覺。 知道這些名詞,卻很難想像它們到底跟我們的生活有什麼關係。但十幾年後再回頭看,很多事情已經不再只是課本上的文字。 我們也開始真正理解什麼叫做「#複合式災害」:災害不一定是一場結束,就全部歸零、Game over、下課。 有時候,前一場災害留下的影響,反而會替下一場災害創造條件。 連續大雨讓土壤更加脆弱,原本已經受損的環境再遇到新的天氣系統,風險就可能一層一層疊加。 所以我們需要正視的,不只是「現在這場災害有多嚴重」,更是前一場災害留下了什麼,以及下一個風險可能從哪裡接著出現。 曾經只是課本裡的名詞,如今已經成為我們必須學會理解、面對,也必須提前準備的現實。 〔發布❯❯2026-08-28∙12:11〕

🙏14👍5👌1

28 Aug 2026, 02:32 UTC≈1,150 views15 reactionsread 28 August 2026

🌀【颱風 #沙德爾 快訊|國際天氣|沙德爾登陸浙江玉環】 根據中國地區氣象部門資訊,今年第18號颱風「沙德爾」中心已於上午8時5分在中國浙江省玉環市登陸。 〔發布❯❯2026-08-28∙10:32〕

👌9👍6

27 Aug 2026, 22:25 UTC≈1,270 views20 reactionsread 28 August 2026
Photo

🌀【颱風 #沙德爾 快訊|國際天氣|沙德爾即將登陸中國地區】 根據中國地區氣象部門資訊,今年第18號颱風「沙德爾」中心目前位於中國浙江省 #台州市、#溫州市 近海一帶,即將登陸。 其中,大家近期相當關心的「#玉環市」即位於台州市轄區內。 此外,我國中央氣象署目前仍持續發布輕度颱風「沙德爾」#海上颱風警報。提醒大家,近期仍請不要前往海岸觀浪、戲水,以免發生危險。 〔發布❯❯2026-08-28∙06:10〕

👍162👌1🙊1

27 Aug 2026, 09:09 UTC≈1,320 views46 reactionsread 28 August 2026
Photo

💬【#小編的話|我們來回答也許你想問的一件事:「你們到底在寫啥」】 隨著「0822豪雨」逐漸落幕,「沙德爾」颱風路徑北偏、對台影響程度降低,我們也想趁這個空檔,和大家談談一件平常比較少被看見的事:我們每天發布這些資訊,背後的「底層邏輯」究竟是什麼? 是看到有趣的事情就發?心情好才發?生氣就不發?還是小編想發什麼就發什麼? ❌ 其實都不是。 📝 我們內部有一套「#風險危機報導階段」原則,作為不同天氣與災害情境下,判斷資訊如何進入、整理、發布及持續更新的基本架構。 更重要的是,這套邏輯可以從 #微觀 一路運用到 #宏觀 視角。 ▍#從微觀到宏觀:一則貼文與他的位置 從微觀來看,它可以用來理解「一則貼文」是如何產生的:從原始資料進入編輯端、來源篩檢、資訊分類、消化理解、編輯轉譯,最後成為大家實際看到的內容。 從宏觀來看,同樣的邏輯也可以放到「整個事件生命週期」中理解:現在事件發展到哪一個階段?目前最重要的風險是什麼?這個

👍31👌87

27 Aug 2026, 08:22 UTC≈1,350 views34 reactionsread 28 August 2026
Photo

快逃...啊不對!是艾陶!

🤣32👌2

27 Aug 2026, 07:58 UTC≈1,430 views4 reactionsread 28 August 2026
Photo

🌀【颱風 #艾陶 生成|遠在中太平洋 對台沒有影響】 靠近遙遠中太平洋的熱帶低氣壓 TD26,已率先增強為今年第21號颱風「#艾陶」(ETAU),旁邊還有熱帶低氣壓 TD25 相伴,兩個系統一起在遠洋上,不會孤單。 放心!它們都距離台灣非常遙遠,對台灣沒有影響,因此這也是我們對「艾陶」颱風的最後一次報告。(完) 〔發布❯❯2026-08-27∙15:58〕

👌4

27 Aug 2026, 03:20 UTC≈1,460 views5 reactionsread 28 August 2026
Photo

🌀【颱風 #沙德爾 海上颱風警報|北部海面、馬祖戒備 台灣零星降雨】 中央氣象署今(27)日上午 8 時 30 分正式發布「沙德爾」海上颱風警報。 目前預測「沙德爾」將持續朝 #中國 方向移動(預計真的還是玉環...),主要威脅 #台灣北部海面 及 #馬祖。⛴️海上作業船隻請嚴加戒備,這段期間也不要靠近海邊戲水、觀浪。 雖然颱風本體沒有直接靠近台灣,但還是帶來一些 #西南風 水氣,因此各地仍可能出現局部短暫陣雨或雷雨,外出記得留意天氣變化。 〔發布❯❯2026-08-27∙11:17〕

4👌1

26 Aug 2026, 21:47 UTC≈1,650 views1 reactionsread 28 August 2026
Photo

⚠️ 【中央氣象署有感 #地震 報告】(速報後更新) —— 📅 發震時間 ❯ 2026年08月27日 05時47分20秒 Ⓜ️ 芮氏規模 ❯ 5.2 📍 震央位置 ❯ 臺灣東南部海域(臺東縣政府東北東方 21.3 公里) ❎ 震央座標 ❯ 北緯 22.82 度.東經 121.35 度 🌏 震源深度 ❯ 35 公里 📲 告警範圍 ❯ 臺東縣 —— (資料來源:中央氣象署地震測報中心)

👌1

26 Aug 2026, 13:45 UTC≈1,610 views21 reactionsread 28 August 2026
Photo

🌀【熱帶低氣壓 #TD25 生成】 位於中太平洋的熱帶擾動今(26)日晚間發展為熱帶性低氣壓 TD25。 他獨自美麗,距離台灣非常遙遠、沒有影響,大家知道一下就好。(完) 〔發布❯❯2026-08-26∙21:45〕

😁164👌1

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

Posts edited after publishing

@TaiwanAlerts edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
10 August 2026
Most recent edit
25 August 2026

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

記者爆料網
@reporter_Taiwan · 59,409
Telegram ranks this channel #1 of 38 here — alongside 37 others — read 30 August 2026
郭哲榮分析師-台灣最多人的財經頻道
@a178178 · 61,044
Telegram ranks this channel #11 of 40 here — alongside 39 others — read 30 August 2026
林睿閎證券分析師-John
@johnstock888 · 49,340
Telegram ranks this channel #13 of 70 here — alongside 69 others — read 30 August 2026
實時現場新聞直播(及 獨家實時消息)
@realtimenewsbroadcasts · 60,293
Telegram ranks this channel #14 of 60 here — alongside 59 others — read 28 August 2026
動區動趨 BlockTempo⚡️區塊鏈 加密貨幣新聞
@blocktemponews · 39,523
Telegram ranks this channel #29 of 87 here — alongside 86 others — read 30 August 2026
Gooaye 股癌
@Gooaye · 105,927
Telegram ranks this channel #44 of 80 here — alongside 79 others — read 30 August 2026

This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“停班停課最新通知 🇹🇼 Taiwan Alerts” (@TaiwanAlerts), 8,967 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/TaiwanAlerts.

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.