《致同路人的勒索信》 Uber救護車作為云云抗爭者中的一個Nobody。 即使未來我們可能無法以後勤頻道的名義服務各位手足,但我們只是改頭換面,本團隊會用另一個角色身份繼續向光復香港的共同願景前進。 但開風氣不為師,不論我們的勒索成功與否,希望一眾尊貴的議員以及從政的同路人會以我們的決定作為警惕,切忌留戀光環,在必要時用盡任何方式繼續為香港民族自由而犧牲的手足抗爭下去。 I am Nobody, We are Nobody, Nobody, I don’t know. 👇🏻👇🏻訂閱Patreon,解鎖光復我城計劃進度 👇🏻👇🏻 https://www.patreon.com/hkua 請另外使用瀏覽器開啟 #記得睇到最後 #請分享比每一個仲堅持緊嘅手足 #SUPPORT_HKUA #最後一戰Patreon5000 ——————————————— Facebook https://www.facebook.com/wat…

Channel
📡 民防事務管理局
@HongKongStateCDMA
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
71subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001186837883 |
|---|---|
| Type | Channel |
| Username | @HongKongStateCDMA |
| Description | Hong Kong State Civil Defense Management Administration |
| Created | 30 April 2020 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/HongKongStateCDMA |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 06:30 | 71 | no change |
| 12 Aug 2026, 06:17 | 71 | first reading |
Engagement
20 posts held, back to 6 September 2020 — the 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.
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 1 October 2020. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 866
- Videos
- 26
- Links
- 137
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 7m 18s
- Average length
- 3m 39s
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.
Recent posts
🚧18:00 #RB 整合🚧 1) T1250 #紅隧 往九龍方向巴士站對出,查私家車/貨車,有拖車; T1800 繼續 2) T1250 #西隧 往九龍方向巴士站,查巴士/私家車,包括905, 914, 970, 973, 紅van; T1750 繼續 3) T1256 #鑽石山 龍翔道往荃灣方向近蒲崗村道,查私家車/小巴; T1741 繼續 4) T1735 #荃灣 荃灣路往九龍方向近荃灣西站,雷射槍即時派彩 5) T1750 #啟德隧道 九龍灣入口前,查巴士
#旺角 1740update 🛎🛎🛎🛎🛎🛎🛎🛎 旺角基本上已形成包圍網,防暴已進入西洋菜南街、洗衣街等內街巡邏、驅趕。登打士街、山東街,豉油街、奶路臣街、亞皆老街等橫街均有佈防。需留意染布房街泉章居有約十架狗車停泊,預計會進入黑布街、登打士街、洗衣街、旺角東火車橋等進行截查 👉 朗豪坊正門及附近街道有防暴把守 👉 亞皆老街通菜街交界 有防最聚會 👉 潮流特區外有至少5鬼車停泊 👉 彌敦道山東街交界70+狗,行人路已封 👉 廣華醫院外至少6鬼私停泊 👉 染布房街泉章居近十架狗車停泊 👉 登打士街好景有狗車停泊
1800 旺角 鼓油街公廁,大量 ss‼️
#旺角 1630 彌敦道往尖沙咀近山東街巴士站4豬2衝2白色小巴2鬼私 #HK5764 #VT8075
#油麻地 1630 彌敦道眾坊街交界 有警員登上一部970巴士查身分證,另至少40防暴同時駐守及進行截查中,check證check袋。
#旺角 1634 洗衣街 亞皆老街交界7仔 約30綠狗聚集
#旺角 1630 彌敦道艾麗大廈天台 三便衣守備 似哨
#旺角 1630 西洋菜南街山東街十字路口藍旗
1630 #油麻地 #眾坊街 #被捕人士 有市民被押上警察旅遊巴。 #蘋果
#旺角 1626 亞皆老街先達門外 2籠1鬼巴1鬼私家衝 #VH3547 #SP5346 停泊 1630 上海街朗豪坊門口 一鬼私 #VB2745 停泊 10暴ss4男子
#旺角 1630 around 20隻防暴沿西洋菜南街往亞皆老街方向行
Showing the 12 most recent of 20 posts we hold for @HongKongStateCDMA. 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 — 1,163,438 of 1,345,403entries 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
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 3 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.
Handles this channel named that no longer answer
- Dead references
- 3
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 3
- vacant every time we have ever looked
@HongKongStateCDMA named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 13 August 2026 – 13 August 2026
named in 1 post, 13 August 2026 – 13 August 2026
named in 1 post, 13 August 2026 – 13 August 2026
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“📡 民防事務管理局” (@HongKongStateCDMA), 71 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/HongKongStateCDMA.
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.