1750 #藍田 鯉魚門道 近藍田公共運輸交匯處 1警私家黑色Honda Stepwgn UB7632 往油塘方向 行駛

Channel
銀河系哨俠頻道🛰
@universalsentinelsinblack
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
11,789subscribers
-164 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001295775972 |
|---|---|
| Type | Channel |
| Username | @universalsentinelsinblack |
| Created | 17 September 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/universalsentinelsinblack |
Topic
National news — 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 94% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 21:15 | 11,789 | -4 |
| 15 Sept 2026, 14:42 | 11,793 | -8 |
| 14 Sept 2026, 01:40 | 11,801 | -7 |
| 12 Sept 2026, 06:41 | 11,808 | -8 |
| 10 Sept 2026, 02:40 | 11,816 | -16 |
| 6 Sept 2026, 23:21 | 11,832 | -7 |
| 4 Sept 2026, 08:40 | 11,839 | -4 |
| 2 Sept 2026, 23:15 | 11,843 | -4 |
| 1 Sept 2026, 21:07 | 11,847 | -8 |
| 31 Aug 2026, 22:16 | 11,855 | -8 |
| 31 Aug 2026, 00:54 | 11,863 | -4 |
| 30 Aug 2026, 02:34 | 11,867 | -5 |
| 29 Aug 2026, 04:48 | 11,872 | -1 |
| 28 Aug 2026, 05:46 | 11,873 | -4 |
| 27 Aug 2026, 02:37 | 11,877 | -2 |
| 26 Aug 2026, 03:11 | 11,879 | -9 |
| 25 Aug 2026, 05:23 | 11,888 | -6 |
| 24 Aug 2026, 05:14 | 11,894 | -8 |
| 22 Aug 2026, 13:14 | 11,902 | -5 |
| 21 Aug 2026, 04:43 | 11,907 | first reading |
Engagement
56 posts held, back to 25 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 47 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.68%
- avg views ÷ 11,789 subscribers
- Avg views / post
- 198
- 20 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 20
- of 56 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.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 56 (25 July 2026 – 2 September 2026) |
| Views total | 3,957 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 23:35 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
2052 #青衣 牙鷹洲街 近青雅苑 1衝 AM8041 KWT 3/2 1白豬 ZE8382 停泊
99.1%宏福苑業主接受收購 何永賢將安排特設銷售計劃售樓 大埔宏福苑業主接受政府收購業權方案今日屆滿,截至下午5時,當局收到99.1%業主交回接受收購建議信件。房屋局局長何永賢在社交專頁表示,當局接下來會推進簽署《買賣協議》,並安排「特設銷售計劃」的售樓工作,包括在下月為參與計劃的業主進行電腦隨機排序,將以信件通知業主結果,預計9月底前開始分批揀樓,每日處理約50至80戶,協助業主前行安頓。 何永賢提到,宏福苑業主向政府出售業權涉及三個步驟,先是交回接受收購建議信件,然後簽署出售宏福苑單位的《買賣協議》,最後完成轉讓契約。完成首個步驟的業主,可按所屬批次參與電腦隨機排序;簽署買賣協議後將獲邀揀樓;完成轉讓契約後,房委會及房協方會與業主簽訂購買新單位的買賣協議或臨時買賣協議。 編輯:李俊傑 2026-08-31 20:05:00
1926 #旺角 警署入1衝 另出1衝 2軍裝1 便衣 出警署 往界限街方向 走去
1916 #太子 界限街 基隆外 再多1衝 EUKW22 往警署方向 行駛
1914 #太子 界限街 基隆外1衝 往警署方向 行駛 另3便衣 基隆外 戒備
1800 #旺角 亞皆老街 塘尾道交界 塘尾道天橋底1衝 閃燈停泊
1732 #大角咀 亞皆老街旺角街市外 1衝 閃燈停泊
1513 #尖沙嘴 港鐵站D出口外 1 衝 隸屬TST 閃燈停泊 另A出口 至少3軍裝 戒備及隨機SS
1006 #九龍塘 港鐵站 AE閘內 往東鐵方向走廊 3藍衫1白衫 戒備
1700 #觀塘 巧明街 近世達中心 1警私家銀色Honda Stepwgn TK7645 停泊
1618 #觀塘 港鐵站內 近客服中心外 2軍裝1便衣 戒備
Showing the 12 most recent of 56 posts we hold for @universalsentinelsinblack. 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.
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.
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.
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.
@youarenotalonehk · 48,344
Telegram ranks this channel #6 of 68 here — alongside 67 others — read 28 August 2026
@HK_Schedule · 23,100
Telegram ranks this channel #15 of 75 here — alongside 74 others — read 19 September 2026
@metwarn · 24,367
Telegram ranks this channel #20 of 71 here — alongside 70 others — read 16 September 2026
@weatherjj · 42,911
Telegram ranks this channel #20 of 74 here — alongside 73 others — read 28 August 2026
@HK_Traffic_News · 44,059
Telegram ranks this channel #20 of 70 here — alongside 69 others — read 28 August 2026
@nowtv_news · 42,741
Telegram ranks this channel #32 of 72 here — alongside 71 others — read 29 August 2026
@inmediahknet · 39,025
Telegram ranks this channel #37 of 82 here — alongside 81 others — read 31 August 2026
@youarenotalonehk_live · 32,152
Telegram ranks this channel #41 of 75 here — alongside 74 others — read 5 September 2026
This channel appears in 8 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“銀河系哨俠頻道🛰” (@universalsentinelsinblack), 11,789 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/universalsentinelsinblack.
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.