Telegram RegisterThe public register of Telegram
Telegram profile photo for WIEN 广东预警速报

Channel

WIEN 广东预警速报

@weatherAlert

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

454subscribers

-2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001118577348
TypeChannel
Username@weatherAlert
CreatedBetween 1 February 2017 and 30 June 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live21 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/weatherAlert

Growth

4544564556 August 2026 — 456 subscribers7 August 2026 — 456 subscribers21 August 2026 — 454 subscribers6 August 202621 August 2026
3 measurements spanning 15 days, net -2. 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 454–456 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 15:46454-2
7 Aug 2026, 19:28456no change
6 Aug 2026, 22:31456first reading

Engagement

20 posts held, back to 6 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
1.04%
avg views ÷ 454 subscribers
Avg views / post
4.7
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (6 August 20266 August 2026)
Views total94
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 22:31 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.

Recent posts

6 Aug 2026, 12:48 UTC7 viewsread 6 August 2026

湛江雷州解除雷雨大风黄色预警 目前雷雨云团已减弱消失,从8月6日20时40分起,雷州市雷雨大风预警信号解除。雷州市气象台发布 (2026/08/06 20:41) #湛江雷州 #雷雨大风 #黄色 #解除

6 Aug 2026, 12:19 UTC8 viewsread 6 August 2026

湛江徐闻解除暴雨黄色预警 目前降雨云团影响减弱,从8月6日20时13分起,徐闻县暴雨预警信号解除。徐闻县气象台发布 (2026/08/06 20:14) #湛江徐闻 #暴雨 #黄色 #解除

6 Aug 2026, 12:19 UTC8 viewsread 6 August 2026

湛江徐闻解除雷雨大风黄色预警 目前雷雨云团影响减弱,从8月6日20时15分起,徐闻县雷雨大风预警信号解除。徐闻县气象台发布 (2026/08/06 20:15) #湛江徐闻 #雷雨大风 #黄色 #解除

6 Aug 2026, 12:12 UTC8 viewsread 6 August 2026

韶关始兴解除雷雨大风黄色预警 目前,影响我县的强对流云团已经远离减弱,始兴县气象台于2026年8月6日19时56分解除澄江镇、顿岗镇、罗坝镇、司前镇雷雨大风黄色预警信号。 (2026/08/06 19:58) #韶关始兴 #雷雨大风 #黄色 #解除

6 Aug 2026, 11:46 UTC7 viewsread 6 August 2026

河源连平解除雷雨大风黄色预警 目前,影响本地的强对流云团已经减弱远离,连平县气象台于2026年8月6日19时31分解除连平县雷雨大风预警信号。 (2026/08/06 19:32) #河源连平 #雷雨大风 #黄色 #解除

6 Aug 2026, 11:20 UTC7 viewsread 6 August 2026

湛江雷州解除暴雨红色预警 目前降雨云团影响减弱,从8月6日19时09分起,企水镇、北和镇、乌石镇暴雨预警信号解除。雷州市气象台发布 (2026/08/06 19:11) #湛江雷州 #暴雨 #红色 #解除

6 Aug 2026, 10:57 UTC5 viewsread 6 August 2026

🟡 韶关始兴发布雷雨大风黄色预警 [Ⅲ级/较重] 受强雷雨云团影响,预计未来1-3小时我县澄江镇、顿岗镇、罗坝镇、司前镇将有6-8级阵风和强雷电,并伴有短时强降水。始兴县气象台于2026年8月6日18时50分发布澄江镇、顿岗镇、罗坝镇、司前镇雷雨大风黄色预警信号,请注意防御短时大风和强雷电。 (2026/08/06 18:52) #韶关始兴 #雷雨大风 #黄色 #发布

6 Aug 2026, 10:43 UTC5 viewsread 6 August 2026

清远连州解除暴雨黄色预警 受午后热对流云团影响,我市出现分散性强降水天气,最大雨量站点为瑶安激水尾55.7毫米,目前影响我市的强降水云团已减弱,连州市气象台于2026年8月6日18时36分解除连州市暴雨黄色预警信号。 (2026/08/06 18:39) #清远连州 #暴雨 #黄色 #解除

6 Aug 2026, 10:38 UTC4 viewsread 6 August 2026

清远英德解除暴雨黄色预警 17时起,横石水出现短时强降水,目前强雷雨云团已移出,英德市气象台8月6日18时32分解除横石水镇暴雨黄色预警信号。 (2026/08/06 18:34) #清远英德 #暴雨 #黄色 #解除

6 Aug 2026, 10:24 UTC4 viewsread 6 August 2026

韶关翁源解除雷雨大风黄色预警 目前,影响我县的强对流云团已减弱远离,翁源县气象台于2026年8月6日18时11分解除全县雷雨大风黄色预警信号。 (2026/08/06 18:11) #韶关翁源 #雷雨大风 #黄色 #解除

6 Aug 2026, 10:12 UTC4 viewsread 6 August 2026

🔴 湛江雷州更新暴雨红色预警 [Ⅰ级/特别严重] 8月6日18时01分北和镇暴雨红色预警信号已生效 (2026/08/06 18:08) #湛江雷州 #暴雨 #红色 #发布

6 Aug 2026, 10:10 UTC4 viewsread 6 August 2026

🔴 湛江雷州升级发布暴雨红色预警 [Ⅰ级/特别严重] 受强降雨云团影响,过去3小时北和镇降雨量已达100毫米以上,预计未来2小时内,降雨仍将持续,从8月6日18时01分起,北和镇暴雨橙色预警信号升级为红色,企水镇、乌石镇暴雨黄色预警信号继续生效,请注意加强防御。雷州市气象台发布 (2026/08/06 18:04) #湛江雷州 #暴雨 #红色 #发布

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

Citation-graph rank

Citation-graph rank — 980,264 of 1,602,868entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“WIEN 广东预警速报” (@weatherAlert), 454 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/weatherAlert.

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.