Telegram RegisterThe public register of Telegram

Channel

🍵✈️Info

@safetystationinfo

On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

22,870subscribers

-25 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001727440013
TypeChannel
Username@safetystationinfo
Description本頻道旨在提供即時車站查票資訊,以供參考之用。 乘搭港鐵,必須使用正確有效車票。 違者會被徵收HKD 1,000(輕鐵則為HKD 370)附加費 查票資料報料渠道 @Teacoffeeliveinfo_bot 報料格式 #車站 時間 最近出口 閘外/外 查票職員數量(有圖更佳) 示例: #沙田 2359 A出口 閘內2黃捉入 (+圖片)
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held9
Confirmed unchanged2 times, most recently 14 August 2026
On Telegramt.me/safetystationinfo

Growth

22,87022,89522,882.56 August 2026 — 22,895 subscribers6 August 2026 — 22,895 subscribers7 August 2026 — 22,890 subscribers8 August 2026 — 22,889 subscribers9 August 2026 — 22,887 subscribers10 August 2026 — 22,883 subscribers11 August 2026 — 22,878 subscribers12 August 2026 — 22,873 subscribers13 August 2026 — 22,870 subscribers6 August 202613 August 2026
9 measurements spanning 7 days, net -25. 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 22,866–22,899 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 12:0522,870-3
12 Aug 2026, 10:5822,873-5
11 Aug 2026, 10:4222,878-5
10 Aug 2026, 11:4822,883-4
9 Aug 2026, 14:1322,887-2
8 Aug 2026, 16:1022,889-1
7 Aug 2026, 18:2322,890-5
6 Aug 2026, 02:0422,895no change
6 Aug 2026, 01:4822,895first reading

Engagement

177 posts held, back to 5 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 22 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
3.72%
avg views ÷ 22,870 subscribers
Avg views / post
850
177 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
177
of 177 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 15 August 2026
Posts held177 (5 August 202615 August 2026)
Views total150,493
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 05:12 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

Photos
10,100
Videos
11
Links
1,450

Lifetime counters from Telegram’s own channel header, read 15 August 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.

Recent posts

15 Aug 2026, 04:45 UTC174 viewsread 15 August 2026
Photo

1244 南昌 🆎 3黃繼續捉出入‼️‼️ CD 3黃繼續捉出入‼️‼️

15 Aug 2026, 02:27 UTC530 viewsread 15 August 2026

#荔景 #LaiKing Ticket Inspection 1025 上層最少1黃捉入⚠️

15 Aug 2026, 01:35 UTC627 viewsread 15 August 2026

#炮台山 #FortressHill Ticket Inspection 0932 客服2黃有cam 捉入⚠️ 連捉兩更‼️

15 Aug 2026, 01:10 UTC673 viewsread 15 August 2026
Photo

#大圍 #TaiWai Ticket Inspection 0910 🆎2黃捉入⚠️ 1035 🆎5黃捉出入‼️‼️‼️ #ChunChoi 🤪Team ‼️‼️ 大圍 沙田 #連站‼️

15 Aug 2026, 01:05 UTC656 viewsread 15 August 2026
Photo

#南昌 #NamCheong Ticket Inspection 0905 0915 1244 🆎3黃捉出入‼️ CD 3黃捉出入‼️ #Ivana 🍠mixed

15 Aug 2026, 00:34 UTC667 viewsread 15 August 2026
Photo

#沙田 #ShaTin Ticket Inspection 0833 1045 🅰/連城 3黃捉出入‼️有cam #MWFUCKER 🖕TEAM ‼️‼️‼️ 大圍 沙田 #連站‼️

15 Aug 2026, 00:19 UTC641 viewsread 15 August 2026
Photo

#鑽石山 #DiamondHill Ticket Inspection 0817 0837 觀塘綫🅰1黃柱後捉入‼️ 觀塘綫BC 1黃捉入⚠️ #VC #刀佬耀🔪‼️‼️‼️ 編按:成半佰有多仲要輪更,仲要諗點樣去伏人,個圓周直徑越黎越長😄

15 Aug 2026, 00:16 UTC641 viewsread 15 August 2026
Photo

#香港 #HongKong Ticket Inspection 0818 1300 AB DEF 閘內4黃⚠️ 有抽查 #LCM 🤡TEAM‼️‼️

15 Aug 2026, 00:16 UTC644 viewsread 15 August 2026
Photo

#天水圍 #TinShuiWai Ticket Inspection 0804 0837 0858 1001 C閘內2黃⚠️DE閘內2黃⚠️ 有人中伏‼️ 有 #查飛廣播📣 #KS 🥸TEAM‼️‼️

14 Aug 2026, 23:32 UTC676 viewsread 15 August 2026

#將軍澳 #TseungKwanO Ticket Inspection 0732 0836 1252 A 閘內2黃⚠️有cam C 閘內2黃 ⚠️有cam

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

@safetystationinfo edited 6 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
8 August 2026
Most recent edit
9 August 2026

Citation-graph rank

Citation-graph rank — 322,602 of 1,350,102entries 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.

Republishes

Channels on the register whose posts this channel has forwarded.

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 2 registered channels — 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“🍵✈️Info” (@safetystationinfo), 22,870 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/safetystationinfo.

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.