Telegram RegisterThe public register of Telegram
Telegram profile photo for OpenHD Users

Supergroup

OpenHD Users

@OpenHD_User

On this record: Topic · Growth · Engagement · Cross-platform identity · Cite this entry

1,556members

-13 since we began measuring on 7 August 2026

31 online right now

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

Register entry

Telegram ID-1001545703930
TypeSupergroup
Username@OpenHD_User
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live12 October 2026
Measurements held14
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/OpenHD_User

Topic

Other / unclassifiable — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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

1,5541,5691,561.57 August 2026 — 1,569 members14 August 2026 — 1,568 members17 August 2026 — 1,567 members20 August 2026 — 1,569 members24 August 2026 — 1,568 members29 August 2026 — 1,565 members1 September 2026 — 1,562 members10 September 2026 — 1,564 members14 September 2026 — 1,563 members18 September 2026 — 1,560 members27 September 2026 — 1,560 members27 September 2026 — 1,554 members5 October 2026 — 1,557 members12 October 2026 — 1,556 members1,5567 August 202612 October 2026
14 measurements spanning 66 days, net -13. 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,552–1,571 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
12 Oct 2026, 02:391,556-1
5 Oct 2026, 13:591,557+3
27 Sept 2026, 16:381,554-6
27 Sept 2026, 02:001,560no change
18 Sept 2026, 02:191,560-3
14 Sept 2026, 03:381,563-1
10 Sept 2026, 14:201,564+2
1 Sept 2026, 22:341,562-3
29 Aug 2026, 20:231,565-3
24 Aug 2026, 07:171,568-1
20 Aug 2026, 20:471,569+2
17 Aug 2026, 16:041,567-1
14 Aug 2026, 08:081,568-1
7 Aug 2026, 05:111,569first 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.

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q108846630 on Wikidata, read 11 October 2026
LabelOpenHD
DescriptionOpen system for long range video transmission
Official sitehttps://www.openhdfpv.org

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

“OpenHD Users” (@OpenHD_User), 1,556 members as measured 12 October 2026. Telegram Register, tgregister.com/channel/OpenHD_User.

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.