Channel
@HeyHey_Hayden
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
415subscribers
+139 since we began measuring on 1 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004297155882 |
|---|---|
| Type | Channel |
| Username | @HeyHey_Hayden |
| Created | Between 1 June 2026 and 5 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/HeyHey_Hayden |
Automotive — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 06:20 | 415 | +2 |
| 26 Oct 2026, 05:09 | 413 | +1 |
| 18 Oct 2026, 12:11 | 412 | +1 |
| 10 Oct 2026, 16:40 | 411 | +39 |
| 30 Sept 2026, 09:55 | 372 | -3 |
| 11 Sept 2026, 06:39 | 375 | +98 |
| 2 Sept 2026, 03:09 | 277 | +1 |
| 1 Sept 2026, 11:30 | 276 | no change |
| 1 Sept 2026, 11:15 | 276 | first reading |
9 posts held, back to 5 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 9 posts for this entry, the most recent from 1 September 2026. An engagement rate over an empty window would be a number about nothing.
53 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 94.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 50 | 94.3% | |
| ❤ | 1 | 1.89% | |
| 🤡 | 1 | 1.89% | |
| 🤣 | 1 | 1.89% |
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 6 of the 9 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 53 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 5 July 2026 to 1 September 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.
August vehicle loss statistics will go up around 5 September. As always I am allowing time for the databases to add in losses from the final days of the month and will go back and update July's figures in case there are any late additions (typically only a couple of vehicles in one or two categories).
👍16
Signed HeyHeyHayden
Just the July column
👍18🤡1
Signed HeyHeyHayden
Telegram loves to butcher the quality when I post them as photos but here is the table in slightly higher quality.
Signed HeyHeyHayden
No major surprises for July, just more of the same trends that have been observed throughout the year: 1. Russian tank losses were a bit higher this month entirely due to that one odd mechanised wave towards Shakhove. 2. IFV usage has continued to decline and is at near record low levels for both sides, hence the incredibly low losses. Yes Ukraine has lost a significant amount over the war and hasn't been getting r…
👍6🤣1
Signed HeyHeyHayden
Personally I saw about 15 videos of Ukrainian SPGs being hit that weren't added to Lostarmour in July as there wasn't clear aftermath (explosion but no closeup or drone watching was too far away to see vehicle), so the actual number hit is likely quite a bit higher than shown here.
👍5
Signed HeyHeyHayden
July 2026 Military vehicle loss statistics are in. As always, Russian losses are from UkraineWarSpotting and Ukrainian losses are from LostArmour. I am only including destroyed and captured vehicles, so no damaged ones, unclear footage or lack of aftermath. I also regularly go back and check previous month tallies as late vehicles or delayed footage is occasionally added, so June has had a few categories with minor…
👍5
Signed HeyHeyHayden
APC losses didn't load in the previous post so they are here
❤1
Signed HeyHeyHayden
Combined graphs and charts for 2025 and 2026 military vehicle losses for comparison.
Signed HeyHeyHayden
Photo, posted without a caption
Signed HeyHeyHayden
Showing the 9 most recent of 9 posts we hold for @HeyHey_Hayden. 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.
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.
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.
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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“HeyHeyHayden” (@HeyHey_Hayden), 415 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/HeyHey_Hayden.
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.