Channel
Network Security Channel
@Engineer_Computer
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,988subscribers
+45 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001090197077 |
|---|---|
| Type | Channel |
| Username | @Engineer_Computer |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/Engineer_Computer |
Topic
Hacking & security — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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 |
|---|---|---|
| 15 Sept 2026, 23:17 | 2,988 | +6 |
| 12 Sept 2026, 16:57 | 2,982 | +3 |
| 11 Sept 2026, 21:24 | 2,979 | no change |
| 8 Sept 2026, 06:39 | 2,979 | +6 |
| 2 Sept 2026, 21:12 | 2,973 | +10 |
| 30 Aug 2026, 10:03 | 2,963 | +5 |
| 27 Aug 2026, 17:59 | 2,958 | -2 |
| 25 Aug 2026, 03:38 | 2,960 | +6 |
| 21 Aug 2026, 13:24 | 2,954 | +8 |
| 18 Aug 2026, 04:03 | 2,946 | -3 |
| 15 Aug 2026, 00:03 | 2,949 | -3 |
| 12 Aug 2026, 02:03 | 2,952 | +4 |
| 9 Aug 2026, 06:42 | 2,948 | +5 |
| 6 Aug 2026, 00:23 | 2,943 | 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.
@AOrgan · 47,423
Telegram ranks this channel #49 of 63 here — alongside 62 others — read 24 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Network Security Channel” (@Engineer_Computer), 2,988 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/Engineer_Computer.
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.