Channel
@thebeardedengineer
On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry
25,241subscribers
-440 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002132013339 |
|---|---|
| Type | Channel |
| Username | @thebeardedengineer |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/thebeardedengineer |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 |
|---|---|---|
| 15 Sept 2026, 20:22 | 25,241 | -22 |
| 14 Sept 2026, 05:18 | 25,263 | -33 |
| 12 Sept 2026, 10:18 | 25,296 | -26 |
| 10 Sept 2026, 07:18 | 25,322 | -41 |
| 6 Sept 2026, 22:01 | 25,363 | -41 |
| 4 Sept 2026, 09:39 | 25,404 | -15 |
| 2 Sept 2026, 20:42 | 25,419 | -14 |
| 1 Sept 2026, 16:36 | 25,433 | -16 |
| 31 Aug 2026, 15:24 | 25,449 | -14 |
| 30 Aug 2026, 15:12 | 25,463 | -11 |
| 29 Aug 2026, 16:54 | 25,474 | -14 |
| 28 Aug 2026, 13:53 | 25,488 | -11 |
| 27 Aug 2026, 14:25 | 25,499 | -15 |
| 26 Aug 2026, 10:55 | 25,514 | -13 |
| 25 Aug 2026, 13:13 | 25,527 | -19 |
| 24 Aug 2026, 13:16 | 25,546 | -33 |
| 22 Aug 2026, 19:27 | 25,579 | -15 |
| 21 Aug 2026, 12:47 | 25,594 | -7 |
| 20 Aug 2026, 15:34 | 25,601 | -20 |
| 19 Aug 2026, 15:15 | 25,621 | first reading |
7 posts held, back to 10 April 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 39 pages 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 7 posts for this entry, the most recent from 17 April 2026. An engagement rate over an empty window would be a number about nothing.
30 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 93.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 28 | 93.3% | |
| 👍 | 1 | 3.33% | |
| 🔥 | 1 | 3.33% |
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 5 of the 7 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 30 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 10 April 2026 to 17 April 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.
websites that help you visualize Code and Data Structures 🖇️ • visualgo.net • visuallearner.org • learngitbranching.js.org • https://www.cs.usfca.edu/~galles/visualization/Algorithms.html
❤10
Photo, posted without a caption
❤3
Here are 5 projects you can do in under 24 hours → 1. AI Projects (includes 5 projects, 1 hour each): https://youtu.be/uRQH2CFvedY?si=3p4ovcUPDE46M6QG 2. Credit Card Fraud Detection (2 hours): https://www.geeksforgeeks.org/machine-learning/ml-credit-card-fraud-detection/ 3. Python Automation Project (3 hours): https://youtu.be/PXMJ6FS7llk?si=Gv23QhlBUn8MRJFz 4. Movie Recommendation Engine (1.5 hours): https:/…
❤8👍1
Photo, posted without a caption
Computer Science Skills that College didn't teach, But you need to Know in 2026! 🔥 🖇️ Link: https://docs.google.com/document/d/1ltgZZd460ugnbVan367dtPCjmQpPcJjDTeyamsGepDw/edit?usp=drivesdk
❤6🔥1
Photo, posted without a caption
❤1
15 LeetCode Questions You Should Practice Before Any Interview 👨💼 🖇️Link: https://docs.google.com/document/d/1E0XR8XIqxNWAQnPEmUMkJMzYcIFUIjjHdYSEoHErv2A/edit?usp=drivesdk
Showing the 7 most recent of 7 posts we hold for @thebeardedengineer. 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 14 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 6 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“THE BEARDED ENGINEER” (@thebeardedengineer), 25,241 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/thebeardedengineer.
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.