Telegram RegisterThe public register of Telegram

Channel

公海總谷資訊台

@hkrallyinfo

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

1,025subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001308715183
TypeChannel
Username@hkrallyinfo
CreatedBetween 1 March 2018 and 1 July 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held2
Confirmed unchanged3 times, most recently 13 August 2026
On Telegramt.me/hkrallyinfo

Growth

1,0256 Aug 2026, 14:32 — 1,025 subscribers7 Aug 2026, 05:20 — 1,025 subscribers6 Aug 2026, 14:327 Aug 2026, 05:20
2 measurements taken within a single day. 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 1,024–1,026 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 05:201,025no change
6 Aug 2026, 14:321,025first reading

Engagement

20 posts held, back to 1 July 2019the 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 24 October 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

24 Oct 2021, 20:02 UTCviews —

The account of the user that owns this channel has been inactive for the last 1 month. If it remains inactive in the next 7 days, that account will self-destruct and this channel may no longer have an owner.

4 Aug 2019, 18:47 UTC≈16,300 viewsread 6 August 2026

訓唔著落街行既朋友記得時刻注意安全,盡量企係有瓦遮頭既地方

29 Jul 2019, 02:38 UTC≈17,500 viewsread 6 August 2026

認清事實真相! 不好再講示威者放火!!!推po https://lih.kg/1379922 - 分享自 LIHKG 討論區

27 Jul 2019, 19:02 UTC644 viewsread 6 August 2026
Photo

此為7.28原定遊行路線 注意除咗遮打花園嘅集會有「不反對通知書」之外,其餘地方警方都發出左「反對通知書」,目前正在等候上訴結果 目前已改為下午三點至晚上十一點,於遮打花園集會 7.28中上環集會資訊頻道: https://t.me/sw728update

26 Jul 2019, 17:37 UTC≈11,000 viewsread 6 August 2026

突發!鑽石山驚見彩虹 https://lih.kg/1369521 - 分享自 LIHKG 討論區

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

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.

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

“公海總谷資訊台” (@hkrallyinfo), 1,025 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/hkrallyinfo.

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.