1540 #坑口 黨鐵站出口有豬籠車,有狗落地截查後生 勿搭黨鐵

Channel
將軍澳緊急救援 (TKO 999)
@tko999
On this record: Topic · Growth · Engagement · Posts · Cite this entry
4,028subscribers
-161 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001221199626 |
|---|---|
| Type | Channel |
| Username | @tko999 |
| Created | 27 August 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 November 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 18 November 2026 |
| On Telegram | t.me/tko999 |
Topic
Local community — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Nov 2026, 03:51 | 4,028 | -3 |
| 12 Nov 2026, 19:58 | 4,031 | -4 |
| 9 Nov 2026, 00:49 | 4,035 | -7 |
| 6 Nov 2026, 02:39 | 4,042 | -3 |
| 2 Nov 2026, 21:59 | 4,045 | -3 |
| 31 Oct 2026, 05:26 | 4,048 | -10 |
| 28 Oct 2026, 12:49 | 4,058 | -9 |
| 25 Oct 2026, 13:56 | 4,067 | -4 |
| 22 Oct 2026, 15:41 | 4,071 | -8 |
| 16 Oct 2026, 20:34 | 4,079 | -6 |
| 13 Oct 2026, 12:36 | 4,085 | -4 |
| 7 Oct 2026, 11:58 | 4,089 | -16 |
| 30 Sept 2026, 10:16 | 4,105 | -25 |
| 16 Sept 2026, 13:55 | 4,130 | -3 |
| 13 Sept 2026, 03:01 | 4,133 | -4 |
| 8 Sept 2026, 21:38 | 4,137 | -8 |
| 3 Sept 2026, 06:36 | 4,145 | -4 |
| 30 Aug 2026, 23:37 | 4,149 | -3 |
| 27 Aug 2026, 17:03 | 4,152 | -3 |
| 24 Aug 2026, 14:24 | 4,155 | first reading |
Engagement
20 posts held, back to 9 November 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 5 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 29 June 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
1545 #將軍澳工業村 將軍澳工業村巴士站外有環保斗起火,現場有消防救火,同一架EU監視
1516 #坑口 富寧花園外有 警察演習,幾十人扮「遊行」,並有大量軍裝在場
1514 #坑口 富寧花園外有幾十名不明人士舉「支持」標語“遊行”??? 現場有幾隻狗護航
1710 #景林 一架EU由停車場入口駛入景林商場
0023 #景林 6名軍裝係景松樓下截查一名推住單車的男子
0013 #坑口 一架響燈EU衝去尚德方向
1321 #狗屋 狗屋出左3架豬籠車往坑口/尚德方向
1347 #寶琳 #景林村 一衝一私停泊 至少20軍裝落地
1302 #寶琳 景林邨正門 一便衣一藍帽子隨機截查路人
1027 #寶琳 貿業路一衝停泊 am6427
1550 馮晴票站外 1EU 3狗 落地 周圍ss
Showing the 12 most recent of 20 posts we hold for @tko999. 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.
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 18 November 2026 — this entry's latest reading, not the date you are reading this.
“將軍澳緊急救援 (TKO 999)” (@tko999), 4,028 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/tko999.
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.