Channel
@hackadayBlog
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
1,016subscribers
+20 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001040806200 |
|---|---|
| Type | Channel |
| Username | @hackadayBlog |
| Created | Between 1 January 2016 and 31 October 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/hackadayBlog |
Technology — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 03:16 | 1,016 | +3 |
| 17 Sept 2026, 17:21 | 1,013 | +1 |
| 10 Sept 2026, 17:19 | 1,012 | -1 |
| 1 Sept 2026, 20:16 | 1,013 | +1 |
| 29 Aug 2026, 18:57 | 1,012 | +2 |
| 26 Aug 2026, 22:28 | 1,010 | +6 |
| 23 Aug 2026, 11:45 | 1,004 | +5 |
| 15 Aug 2026, 01:07 | 999 | +3 |
| 6 Aug 2026, 13:18 | 996 | no change |
| 5 Aug 2026, 23:34 | 996 | first reading |
20 posts held, back to 5 August 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.
For decades now, companies like Michelin have been teasing us with futuristic-looking automobile tires that don’t use air. Instead, they use a polymer mesh of sorts which maintains the same …read more (https://hackaday.com/2026/08/05/3d-printing-a-usable-airless-tire/)
3D Printing A Usable Airless Tire https://hackaday.com/2026/08/05/3d-printing-a-usable-airless-tire/
Photo, posted without a caption
Full Teardown of a 2026 Amazon Fire Stick HD https://hackaday.com/2026/08/05/full-teardown-of-a-2026-amazon-fire-stick-hd/
Photo, posted without a caption
After the release of Google’s Chromecast so-called ‘streaming sticks’ have remained a popular form factor, even though such technology is these days part of ‘smart’ TVs. Being curious as to …read more (https://hackaday.com/2026/08/05/full-teardown-of-a-2026-amazon-fire-stick-hd/)
Addressable LEDs Make Giant 16×2 Character Display https://hackaday.com/2026/08/05/addressable-leds-make-giant-16x2-character-display/
Photo, posted without a caption
We’ve always taken a certain childlike joy in seeing tiny things made big, and big things tiny. Evidently [Uncle Stem] is the same way, if this 7x sized 16×2 “LCD” …read more (https://hackaday.com/2026/08/05/addressable-leds-make-giant-16x2-character-display/)
FLOSS Weekly Episode 878: A Tool With Opinions https://hackaday.com/2026/08/05/floss-weekly-episode-878-a-tool-with-opinions/
Photo, posted without a caption
This week Jonathan chats with Jonathan Pallant about embedded Rust! Learn about the growing Rust driver library, the different ways to build a Rust stack on an embedded device, and …read more (https://hackaday.com/2026/08/05/floss-weekly-episode-878-a-tool-with-opinions/)
Showing the 12 most recent of 20 posts we hold for @hackadayBlog. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“Hackaday” (@hackadayBlog), 1,016 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/hackadayBlog.
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.