Supergroup
英國戰線 公海 2.0 🇬🇧 By Britons in Hong Kong/UK
@BHK1841
On this record: Topic · Growth · Engagement · Citations · Cite this entry
2,032members
-30 since we began measuring on 6 August 2026
54 online right now
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001826359164 |
|---|---|
| Type | Supergroup |
| Username | @BHK1841 |
| Description | 英國新聞時事生活公海，可集中宣傳英國抗爭及地區活動。 ❗️ 此群組管理員及作用為管理公海秩序，不代表BHK立場,Speaker發言亦僅代表其個人立場。 此公海暫時手動批准入群，如果多次嘗試入群不果請聯絡 @windanz。未能入群原因可以和帳號名稱有關係，及已經被標注為spam帳戶。 🌐 BHK Channel t.me/britonshk 🌐BHK 英戰線 公海 t.me/bhk1841 BHK監察組： @bhkuk ⚠️ 公告BHK群組版規 舉報違規行為 對違規處分上訴等 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 September 2026 |
| Last confirmed live | 20 September 2026 |
| Measurements held | 14 |
| On Telegram | t.me/BHK1841 |
Topic
Politics & activism — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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) | Members | Change |
|---|---|---|
| 20 Sept 2026, 15:45 | 2,032 | no change |
| 18 Sept 2026, 01:38 | 2,032 | -1 |
| 13 Sept 2026, 16:17 | 2,033 | -4 |
| 9 Sept 2026, 16:55 | 2,037 | -5 |
| 4 Sept 2026, 08:40 | 2,042 | +1 |
| 29 Aug 2026, 01:04 | 2,041 | -1 |
| 26 Aug 2026, 06:32 | 2,042 | -1 |
| 23 Aug 2026, 03:43 | 2,043 | -2 |
| 19 Aug 2026, 09:34 | 2,045 | -5 |
| 16 Aug 2026, 08:38 | 2,050 | -7 |
| 12 Aug 2026, 21:56 | 2,057 | -1 |
| 10 Aug 2026, 00:42 | 2,058 | -5 |
| 7 Aug 2026, 05:05 | 2,063 | +1 |
| 6 Aug 2026, 18:46 | 2,062 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Mentions
Named by 4 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.
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 20 September 2026 — this entry's latest reading, not the date you are reading this.
“英國戰線 公海 2.0 🇬🇧 By Britons in Hong Kong/UK” (@BHK1841), 2,032 members as measured 20 September 2026. Telegram Register, tgregister.com/channel/BHK1841.
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.