Sticker, posted without a caption
🤩1

Channel
@weatherjj
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
42,128subscribers
-1,257 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001465749941 |
|---|---|
| Type | Channel |
| Username | @weatherjj |
| Description | 聯絡Admin: 氣象bot打 @weatherjjbot 本頻道主要提供: ✅天氣實況及短中期預報; ✅大型公眾活動現場實況及民防資訊; ✅本地、國際新聞分享及簡評; ✅其他與個人防護相關的資訊(例:法律知識、衛生資訊)。 注意本頻道: ‼️提供非官方天氣資訊,如希望獲取官方資訊,請參閱香港天文台網頁; ‼️僅提供大型公眾活動的民防資訊,不會提倡現場民眾作任何行動; ‼️提供的新聞簡評、法律意見、衛生提示、防護警示及交通消息等僅為個人意見,參考前請自行判斷。 |
| Created | 18 June 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/weatherjj |
Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 69% 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 the other topics.
Recorded in 2019 as “氣象巴打⚠️高登連登氣象台聯合頻道” — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 15:21 | 42,128 | -13 |
| 9 Nov 2026, 19:30 | 42,141 | -16 |
| 8 Nov 2026, 13:59 | 42,157 | -17 |
| 7 Nov 2026, 10:55 | 42,174 | -22 |
| 6 Nov 2026, 08:29 | 42,196 | -8 |
| 5 Nov 2026, 09:18 | 42,204 | -25 |
| 4 Nov 2026, 07:31 | 42,229 | -19 |
| 3 Nov 2026, 09:37 | 42,248 | -2 |
| 2 Nov 2026, 12:44 | 42,250 | -11 |
| 1 Nov 2026, 09:05 | 42,261 | -18 |
| 31 Oct 2026, 07:36 | 42,279 | -16 |
| 30 Oct 2026, 06:34 | 42,295 | -23 |
| 29 Oct 2026, 03:39 | 42,318 | -19 |
| 28 Oct 2026, 01:00 | 42,337 | -12 |
| 26 Oct 2026, 23:08 | 42,349 | -20 |
| 26 Oct 2026, 02:08 | 42,369 | -19 |
| 25 Oct 2026, 02:40 | 42,388 | -3 |
| 24 Oct 2026, 05:36 | 42,391 | -16 |
| 23 Oct 2026, 02:29 | 42,407 | -9 |
| 22 Oct 2026, 05:11 | 42,416 | first reading |
153 posts held, back to 29 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 192 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. It is computed over the 30 of 34 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 153 (29 July 2026 – 13 November 2026) |
| Views total | 87,292 |
| Reactions total | 669 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 21:00 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 13 November 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 2 videos 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.
2,924 reactions across 123 posts, in 32 distinct kinds. The most used accounts for 61.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,807 | 61.8% | |
| 🥱 | 208 | 7.11% | |
| 👍 | 205 | 7.01% | |
| 🔥 | 124 | 4.24% | |
| 🙏 | 89 | 3.04% | |
| 💩 | 78 | 2.67% | |
| 🐳 | 61 | 2.09% | |
| 😱 | 58 | 1.98% | |
| 🤩 | 36 | 1.23% | |
| 🕊 | 31 | 1.06% | |
| 🖕 | 28 | 0.958% | |
| 🤯 | 28 | 0.958% | |
| 🤣 | 26 | 0.889% | |
| 🥰 | 23 | 0.787% | |
| 🙈 | 18 | 0.616% | |
| 💊 | 13 | 0.445% | |
| 🌚 | 12 | 0.41% | |
| ⚡ | 10 | 0.342% | |
| 👌 | 10 | 0.342% | |
| 🦄 | 10 | 0.342% | |
| 12 further kinds | 49 | 1.68% |
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 127 of the 153 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 3,056 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 153 most recent posts we hold, published 29 July 2026 to 13 November 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’s own ‘edited’ marker: 2 of 39 posts held from the last 30 days (5.13%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Sticker, posted without a caption
🤩1
⛈ #狗屎預報 #整備階段 目前部份數值預報模式及AI預報模式均預測本港將會受到西風槽所帶嚟嘅低空急流影響,由今日晚間至聽日上午會出明顯降雨過程,各位如安排咗呢段期間外出活動嘅民眾要加倍留意! 為咗提醒民眾儘早開始準備,以避免受暴雨帶嚟嘅損失,氣象巴打於今日04時30分開始進入🟡 #整備階段。 雖然預計降雨最強時間約於今日午夜時後至聽日清晨時分,但各位民眾仍應該作好預備,預早造好防水浸及陣風措施。 ⚠️留意事項 1. 低空急流橫過香港時可能會出現渦旋中心,中心附近降雨可以好強,並伴隨猛烈陣風/短暫旋風。 2. 視乎渦旋中心的強烈雨區橫過香港時的速度,暴雨可能會嚟得快,去得亦快。 3. 建議以預防8號風球標準處理防止猛烈陣風吹襲(處理大型棚架及懸掛物件);防止水浸/山泥傾瀉則按照預防暴雨標準處理。 4. 如安排星期六前往戶外活動,切勿靠近河道/引水道,預防山洪暴發引起的風險。 5. 渦旋中心將於星期六凌晨至早上橫過香港,機場上…
❤12
Sticker, posted without a caption
Channel name was changed to «🐘氣象巴打🟡»
ℹ️ #氣象小小小知識 上面所講嘅魚麟天其實係卷積雲,氣象諺語中經常有提到「魚鱗天,不雨也風顛」,就係通常於出現呢類雲象後嘅一兩天天氣便會轉壞、風速增強、雲層增厚並帶來降雨。 另一方面,部份數值預報模式及AI預報模式均預測本港由星期五晚間至星期六中午會出明顯降雨過程,各位如安排咗呢段期間外出活動嘅民眾要加倍留意下喇。
👍15
🏞 #實時天氣報料 2100 飛鵝山 魚麟天
❤17
🏞 #實時天氣報料 1615 臺北擎天崗
❤13👍6🥱3
🏵 #尋日天氣報料 尋日1810 深井 讓🔻
👍9❤7🔥3
🏚🗾 #靜岡地震 日本靜岡縣西部於日本時間今日01時04分發生黎克特制5.7級地震,震源深度40公里。 愛知縣西部知多市錄得最大震度為5強,暫時未有傷亡及損毀報告。
🙏30
Sticker, posted without a caption
🤯2
🏞 #實時天氣報料 19:30 (當地時間) 日本千葉縣成田花火大會 氣溫13度 🎆
❤29🎉7🥱5
🏵 #尋日天氣報料 1724 (當地時間 - 尋日) 墨西哥Oaxaca Puerto Escondido La Punta Zicaleta 有雲
❤23🥱4
Showing the 12 most recent of 153 posts we hold for @weatherjj. 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.
@weatherjj 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.
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.
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 28 August 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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“🐘氣象巴打🟢” (@weatherjj), 42,128 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/weatherjj.
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.