3 measurements spanning 7 days, net +1. 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 269–270 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Aug 2026, 23:37
270
+1
7 Aug 2026, 00:18
269
no change
6 Aug 2026, 18:03
269
first reading
Engagement
10 posts held, back to 20 April 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 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
146.3%
avg views ÷ 270 subscribers
Avg views / post
395
1 post measured
Reaction rate
0.506%
reactions ÷ views · ER floor
Posts in window
1
of 10 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
Window
Rolling 30 days · latest post in window 22 July 2026
Posts held
10 (20 April 2026 – 22 July 2026)
Views total
395
Reactions total
2
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 00:18 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.
Reaction mix
31 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 51.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
16
51.6%
🔥
6
19.4%
❤
5
16.1%
👏
4
12.9%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 10 of the 10 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 31reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 20 April 2026 to 22 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
On the same day from 7 years ago, 1 million protested against the extradition bill. That’s beginning of the anti-extractions bill in Hong Kong. The world also witness the true nature of #China.
七年前嘅今日,一百萬人喺香港開始對抗暴政。設置一個世界亦都開始見到中共嘅真面目。
#HKProtest #2019反送中 #NeverforgiveNeverforget
宏福苑大火聽證會重點(Day 5–15)
Day 5
居民葉家駒指見有人將大量授權票倒入票箱,並有陌生人出現在業主大會,質疑投票公信力
7名居民作證,指相關負責人刻意迴避責任
消防承辦商確認火災前一週已發現消防總掣被關閉
居民曾查詢「發泡膠封窗」問題,消防建議轉問屋宇署,顯示監管界線模糊
Day 6
宏泰消防董事被問及發現消防總掣全關後為何未跟進,回應「我已經多事咗」
年檢表顯示水缸有問題,該董事稱「可能填錯」,淡化問題嚴重性
Day 7
物管文員指授權票情況難核實,「打個交叉都當簽咗名」
文員亦指工程顧問鴻毅預早知道ICU巡查
物管電工承認關閉8座消防總掣,明知需持牌人士處理仍因已出單而照做
工程主任稱不知兩電工曾協助消防缸放水,被陸啟康質疑失職
Day 8
置邦經理黎永利未有出庭作證,下屬稱不清楚原因
前保安部主管入職14日即辭職,指屋苑環境惡劣,多次反映無果
物業主任稱火災當日才知火警鐘被關
置邦職員否認宏泰消防曾…
🔥2👍1
Signed HKDM2
Showing the 10 most recent of 10 posts we hold for @HKDMovement. 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 — 936,461 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
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 13 August 2026 — this
entry's latest reading, not the date you are reading this.
“Hong Kong Democracy Movement” (@HKDMovement), 270 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/HKDMovement.
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.