https://x.com/i/status/2085239725061972327

Channel
Horsehead Group
@horseheadgroup
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,377subscribers
-52 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002216364549 |
|---|---|
| Type | Channel |
| Username | @horseheadgroup |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 2 times, most recently 12 October 2026 |
| On Telegram | t.me/horseheadgroup |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 07:56 | 1,377 | -3 |
| 27 Sept 2026, 04:19 | 1,380 | -10 |
| 17 Sept 2026, 12:17 | 1,390 | -4 |
| 13 Sept 2026, 06:01 | 1,394 | -7 |
| 9 Sept 2026, 12:35 | 1,401 | -4 |
| 4 Sept 2026, 07:40 | 1,405 | -3 |
| 31 Aug 2026, 20:04 | 1,408 | -2 |
| 29 Aug 2026, 01:43 | 1,410 | -5 |
| 26 Aug 2026, 10:56 | 1,415 | -1 |
| 23 Aug 2026, 09:13 | 1,416 | -3 |
| 20 Aug 2026, 01:47 | 1,419 | -2 |
| 16 Aug 2026, 20:45 | 1,421 | -4 |
| 13 Aug 2026, 13:34 | 1,425 | -5 |
| 10 Aug 2026, 20:11 | 1,430 | +1 |
| 7 Aug 2026, 22:03 | 1,429 | no change |
| 7 Aug 2026, 18:22 | 1,429 | first reading |
Engagement
20 posts held, back to 29 July 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 page of 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
https://x.com/i/status/2085098603425493472
https://x.com/i/status/2083579156261220783
https://www.munichre.com/en/solutions/for-industry-clients/insure-ai.html
https://x.com/i/status/2085068631059386501
https://x.com/i/status/2085043839589617918
https://x.com/Alfred_Lin/status/2084636778791858256?s=20
https://www.weco.ai/blog/4-levels-of-recursive-self-improvement
https://x.com/waterloo_intern/status/2084426439034540297?s=20
https://x.com/i/status/2084421546395705756
https://x.com/i/status/2084389116012339220
https://x.com/i/status/2084399057095594414
Showing the 12 most recent of 20 posts we hold for @horseheadgroup. 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.
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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“Horsehead Group” (@horseheadgroup), 1,377 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/horseheadgroup.
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.