Channel
ENGINEERS DNA
@engineersdna
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,584subscribers
-108 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001165648999 |
|---|---|
| Type | Channel |
| Username | @engineersdna |
| Created | 22 July 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/engineersdna |
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 14 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 14:17 | 3,584 | -6 |
| 5 Nov 2026, 15:15 | 3,590 | -4 |
| 3 Nov 2026, 00:56 | 3,594 | -2 |
| 31 Oct 2026, 05:10 | 3,596 | -4 |
| 27 Oct 2026, 19:01 | 3,600 | -3 |
| 24 Oct 2026, 10:45 | 3,603 | -2 |
| 21 Oct 2026, 14:27 | 3,605 | -7 |
| 18 Oct 2026, 12:06 | 3,612 | -4 |
| 15 Oct 2026, 05:08 | 3,616 | -2 |
| 11 Oct 2026, 17:57 | 3,618 | -7 |
| 5 Oct 2026, 09:02 | 3,625 | -7 |
| 26 Sept 2026, 21:21 | 3,632 | -9 |
| 15 Sept 2026, 22:21 | 3,641 | -6 |
| 12 Sept 2026, 02:55 | 3,647 | -10 |
| 7 Sept 2026, 13:01 | 3,657 | no change |
| 7 Sept 2026, 10:39 | 3,657 | -3 |
| 2 Sept 2026, 13:14 | 3,660 | -8 |
| 30 Aug 2026, 18:35 | 3,668 | -6 |
| 27 Aug 2026, 08:25 | 3,674 | -4 |
| 24 Aug 2026, 10:13 | 3,678 | first 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.
Appears in Telegram’s recommendations for other channels
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.
@jaspalsirofficial · 27,135
Telegram ranks this channel #23 of 70 here — alongside 69 others — read 11 September 2026
@ojaankiasacademy · 20,346
Telegram ranks this channel #32 of 62 here — alongside 61 others — read 25 September 2026
@Civil_Engineering_Pdfs_Notes · 31,762
Telegram ranks this channel #48 of 85 here — alongside 84 others — read 5 September 2026
@CSE_Prelims_MCQs_Quiz · 31,471
Telegram ranks this channel #65 of 81 here — alongside 80 others — read 5 September 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“ENGINEERS DNA” (@engineersdna), 3,584 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/engineersdna.
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.