Channel
@metwarn
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
24,277subscribers
-122 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001394006413 |
|---|---|
| Type | Channel |
| Username | @metwarn |
| Description | 捉得緊現在，先可以預報未來。 MET WARN 天氣預警頻道提供最新天氣消息，請善用Forward功能轉發信息。 免責聲明: 1. 此頻道的天氣資訊均為非官方資訊，如欲獲得官方資訊，請到香港天文台網頁。 2. MET WARN 天氣預警 不會對使用本頻道資料而導致的任何損失而負責。 網頁： www.metwarn.hk |
| Created | 31 May 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 October 2026 |
| Measurements held | 39 |
| Confirmed unchanged | 1 time, most recently 19 October 2026 |
| On Telegram | t.me/metwarn |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Oct 2026, 14:34 | 24,277 | -5 |
| 18 Oct 2026, 11:37 | 24,282 | -1 |
| 17 Oct 2026, 14:47 | 24,283 | -3 |
| 16 Oct 2026, 15:26 | 24,286 | -1 |
| 15 Oct 2026, 16:40 | 24,287 | -2 |
| 14 Oct 2026, 19:01 | 24,289 | -8 |
| 13 Oct 2026, 09:07 | 24,297 | -6 |
| 9 Oct 2026, 07:18 | 24,303 | -12 |
| 4 Oct 2026, 22:41 | 24,315 | -11 |
| 27 Sept 2026, 18:18 | 24,326 | -41 |
| 17 Sept 2026, 15:36 | 24,367 | -2 |
| 15 Sept 2026, 14:21 | 24,369 | -1 |
| 13 Sept 2026, 23:39 | 24,370 | -3 |
| 12 Sept 2026, 05:18 | 24,373 | -7 |
| 6 Sept 2026, 14:55 | 24,380 | -7 |
| 4 Sept 2026, 03:37 | 24,387 | +1 |
| 2 Sept 2026, 15:35 | 24,386 | -5 |
| 1 Sept 2026, 15:23 | 24,391 | +4 |
| 31 Aug 2026, 11:46 | 24,387 | +3 |
| 30 Aug 2026, 13:54 | 24,384 | first reading |
134 posts held, back to 31 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 100 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 19 October 2026 |
|---|---|
| Posts held | 134 (31 July 2026 – 19 October 2026) |
| Views total | 153,120 |
| Reactions total | 1,066 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 19 Oct 2026, 21:34 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.
Lifetime counters from Telegram’s own channel header, read 19 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
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.
8,237 reactions across 133 posts, in 53 distinct kinds. The most used accounts for 17.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🐳 | 1,469 | 17.8% | |
| 🔥 | 986 | 12.0% | |
| 🤡 | 819 | 9.94% | |
| 👍 | 749 | 9.09% | |
| ❤ | 670 | 8.13% | |
| 🫡 | 554 | 6.73% | |
| 🥱 | 388 | 4.71% | |
| 💩 | 349 | 4.24% | |
| 👏 | 217 | 2.63% | |
| 🤣 | 201 | 2.44% | |
| 🕊 | 190 | 2.31% | |
| 🙏 | 160 | 1.94% | |
| 👎 | 142 | 1.72% | |
| 😴 | 140 | 1.70% | |
| 😢 | 127 | 1.54% | |
| 😱 | 118 | 1.43% | |
| 🖕 | 84 | 1.02% | |
| 🤯 | 75 | 0.911% | |
| 😁 | 74 | 0.898% | |
| 😨 | 72 | 0.874% | |
| 33 further kinds | 653 | 7.93% |
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 134 of the 134 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 8,278 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 134 most recent posts we hold, published 31 July 2026 to 19 October 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.
西北太平洋的熱帶氣旋薔琵再度增強為最高級別的五級颱風。按照現時預測，薔琵將趨向台灣至沖繩一帶海域，對本港直接影響不大。 衛星雲圖顯示，薔琵完成眼壁置換後風眼有所擴大，同時環流開始變得廣闊。此外，美國聯合颱風警報中心先前重新分析薔琵針眼巔峰的強度，評估當時風暴為最高級別的五級颱風。 電腦模式目前對薔琵本週中後期的路徑仍有分歧。傳統電腦模式預測風暴登陸台灣，人工智能模式則預測風暴在台灣以東海域轉向。預測分歧主因是西風槽通過東亞的時間和隨後北收速度，導致電腦模式對薔琵路徑的北份量預測有異。 由於副熱帶高壓脊將處於東退週期，加上薔琵的強度和環流大小或進一步擠壓副高，因此預料風暴進入南海的機會不大。但讀者要留意，薔琵的外圍下沉氣流有機會於本週中後期影響本港，屆時日夜溫差會較大。至於計劃前往台灣或沖繩一帶的讀者，亦應留意風暴動向。
👌20🆒4❤1🥰1
位於西北太平洋的熱帶氣旋薔琵爆發性增強，逼近最高級別的五級颱風強度。 衛星雲圖可見薔琵發展出清晰的針眼，並伴隨緊密的核心。基於衛星雲圖強度估算和雷達測風數據，各大氣象機構或低估了薔琵的強度。 薔琵夜間掠過關島以南，該區與風力最強的眼壁擦身而過，可謂避過一劫。薔琵短期內可能開始進行眼壁置換，隨後強度須視乎核心結構的演變。 同時，電腦模式持續將薔琵的預測路徑往南修正，目前較多模式預料風暴直趨台灣。然而，風暴的實際路徑仍須視乎下週中西風槽的南探幅度，以及通過東亞的時間，存在一定變數。MET WARN 會繼續觀察薔琵的動向。
🤔15🫡9🕊3🤡3❤2👏2
印尼年中起發生大範圍野火，是自2015年以來最嚴重。霧霾天氣亦影響鄰國，對公眾健康構成嚴重威脅。究竟這場浩劫背後是天災還是人禍？ 根據 NASA 衛星數據，截至今日（10月17日），印尼全國累計火點數已超過 1,000,000 個。另據獨立監測平台 Nusantara Atlas 分析，截至 9 月全印尼累計遭焚燒土地面積逾 1,400,000 公頃（約等於 13 個香港的面積），是自2019年以來同期最高。 野火產生的大量濃煙隨著季風向西擴散，影響新加坡、馬來西亞等鄰國。新加坡 10 月9日空氣質素指數（AQI）一度達216，一度成為全球空氣污染最嚴重的城市。 霧霾天氣對公共健康構成嚴重威脅，印尼七個州份因霧霾誘發呼吸道疾病的人數升至超過 28.3 萬宗 。霧霾天氣亦降低能見度，影響航空交通。在過去兩個月，印尼有超過2000班航班取消。 這場野火，是天災還是人禍？棕櫚油業者為降低開墾土地成本，非法採用「刀耕火種」（Sla…
🕊23😢16❤5🔥4🤡2🫡2🙈1
日本氣象廳已為西北太平洋的熱帶風暴命名「薔琵」，令本年獲命名熱帶氣旋總數達到 30 個，是2013年以來第一次。 預測薔琵未來數天將大致向西北偏西移動，移向呂宋以東海域並逐步增強。薔琵隨後動向存在變數，需視乎西風槽及副熱帶高壓脊的形態變化。薔琵隨後較可能轉向偏北路徑橫過台灣以東海域，但現階段仍未能排除風暴登陸台灣或進入南海東北部的可能。 今年風季異常活躍，是否與當前的「超級厄爾尼諾」有關？MET WARN 統計2000年至今的數據，發現ENSO 狀態與西北太平洋獲命名風暴的年總數之間並無顯著的相關性。然而，ENSO狀態會影響西北太平洋的海溫配置，從而對風暴生成位置有影響。例如在弱拉尼娜背景下，2013 年風暴生成位置相對偏西，較多風暴影響中國及菲律賓；而今年風季的風暴生成位置偏東，因此較多「遠洋颱」的出現，甚至有風暴從東太平洋「越洋」遠道而來。 雖然已踏入秋季，但西北太平洋風季仍未完結，獲命名風暴數量有機會超越2013年3…
❤29🕊4🫡3🥱2
五年前的2021年10月13日，熱帶氣旋圓規為本港帶來2021年第二個八號信號，是繼獅子山襲港，相隔僅僅兩日半後天文台再次需要發出八號烈風或暴風信號，成為有紀錄以來不同風暴相隔最短時間的八號信號。 圓規的環流較廣闊、移速較快，加上在東北季候風的共同影響下，即使圓規最接近本港距離達360公里，本港仍有部分地區吹烈風，離岸間中達暴風，大老山更一度吹颶風。 而圓規亦為本港帶來較顯著的風暴潮。受圓規及東北季候風的共同影響下，維多利亞港及吐露港的海水高度3.38及3.53米，風暴增水超過1米。維港水位為有紀錄以來十月最高，亦是歷來第六高，僅次溫黛、山竹、天鴿、黑格比及樺加沙等歷史風暴。風暴潮及越堤浪夾擊之下不少沿岸及低窪地區出現水浸。 由於圓規襲港期間主要吹東至東北風，受東北季候風影響下未有轉吹東南風，八號東北烈風或暴風信號生效時間長達23小時20分鐘，是1973年以來單一方向信號生效時數的最長紀錄。 圓規影片特輯： https:…
❤15🫡6🥱3👌1👍1🕊1
五年前的2021年10月8日至9日，熱帶氣旋獅子山襲港，雖然強度只達熱帶風暴級別，但其暖濕的偏南氣流與東北季候風匯聚，為本港帶來異常持續的大風雨天氣，打破當時有紀錄以來10月最高日雨量，以及帶來1961年以來距離香港最遠的八號風球。 10月8日，三號風球及黃雨生效期間，跑馬地一幅巨型棚架在狂風暴雨中倒塌，事件不幸造成一死兩傷。隨後雨勢進一步增強，天文台先後發出紅色及黑色暴雨警告。當日天文台總部共錄得329.7毫米雨量，刷新當時10月最高單日雨量紀錄（此紀錄已被2023年小犬襲港時打破）。 10月9日午夜，獅子山登陸海南島，但港澳兩地風力不跌反升，本港離岸持續吹烈風，西南部高地更達暴風；而澳門亦曾三橋同時錄得九級烈風，隨後更率先預告將會改發八號風球。本港天文台則在未有任何預告下於上午4時40分發出預警八號特別報告，並在兩小時後改發八號東南烈風或暴風信號。此做法屬近年罕有。 八號信號生效期間，由於與獅子山相關的雨帶不時來襲，本…
😁15👏6👍5🕊4❤3🥱3🫡1
位於墨西哥灣的熱帶氣旋Isaias增強為北大西洋今年首個颶風，是自1905 年以來最遲「首颶」。 今年北大西洋熱帶氣旋活動顯著偏低，主因是現時在東太平洋發展的「超級厄爾尼諾」現象。在厄爾尼諾背景下，大西洋熱帶洋區的垂直風切變會較常年強，同時下沉氣流會較盛行，抑制熱帶低壓系統的對流活動及垂直結構發展，導致風季長時間處於低迷狀態。 目前 Isaias 正向東北偏北方向移動，受到墨西哥灣高海溫與大氣條件支持，預料強度仍有進一步提升的空間。Isaias 將以颶風強度移向路易斯安那州至佛羅里達州西部一帶，為當地帶來強風、暴雨及風暴潮威脅。
👏9🌚6👌6🫡3😭1
西北太平洋再次迎來外洋來客。熱帶氣旋諾洛於東太平洋形成，香港時間今日清晨正式進入西北太平洋，成為2023年多拉以來首個東太來客。 諾洛於墨西哥西南海域發展為熱帶低氣壓，初期發展所阻，但最終在中太平洋增強為熱帶風暴並獲名。諾洛一度於夏威夷西南海域急劇增強，與最高級別的五級颶風僅一步之遙。隨後諾洛強度大上大落，但進入西北太平洋前重新增強，現時強度為三級颶風。 西北太平洋迎接外洋來客時有發生，但從東太平洋遠道而來的颶風則相當罕見，有紀錄以來發生少於十次。這是因為高壓脊須維持相當強度，才可令風暴一直在較低緯度西行；而夏威夷附近海域一般亦不利風暴發展，亦成為潛在東太來客的另一屏障。 值得留意的是，風暴越洋進入西北太平洋的情況，較多發生於厄爾尼諾年。這是因為赤道太平洋中部及東部的海溫較正常偏高，令對流活動以及風暴生成的位置隨之東移。
👍16🕊12😱6🫡3🤡2❤1👏1
[暴雨速報] 天文台在下午10時30分取消黃色暴雨警告信號。 雖然暴雨警告已經取消，但市民仍須警覺有關河道氾濫可能帶來的危險。
🫡15❤4👏2
[暴雨速報] 天文台在下午8時20分發出黃色暴雨警告信號。 表示香港廣泛地區可能或已錄得每小時30毫米的大雨，而且雨勢可能持續。
😱28🐳8🆒2🌚1🫡1
與一道冷鋒相關的雷雨帶正逐漸向南移近，預料未來一兩小時香港多處地區將受大驟雨及雷暴影響，新界北部將首當其衝。 正在身處室外的讀者應留意天氣變化。
🫡27🤡13🐳7❤4💩3😢2
[暴雨速報] 天文台在上午9時10分取消黃色暴雨警告信號。 雖然暴雨警告已經取消，但市民仍須警覺有關河道氾濫可能帶來的危險。
👍16👏3🫡2🤡1
Showing the 12 most recent of 134 posts we hold for @metwarn. 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.
@metwarn edited 1 post 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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 16 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 12 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“MET WARN 天氣預警” (@metwarn), 24,277 subscribers as measured 19 October 2026. Telegram Register, tgregister.com/channel/metwarn.
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.