Channel
🌐 Hacking y Seguridad
@hackingyseguridad
On this record: Topic · Growth · Engagement · Cite this entry
132subscribers
+14 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001096888922 |
|---|---|
| Type | Channel |
| Username | @hackingyseguridad |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 October 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/hackingyseguridad |
Topic
Hacking & security — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 18 October 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 6 Nov 2026, 23:18 | 132 | +1 |
| 30 Oct 2026, 21:01 | 131 | +2 |
| 24 Oct 2026, 06:35 | 129 | +2 |
| 18 Oct 2026, 05:44 | 127 | no change |
| 16 Oct 2026, 10:15 | 127 | +1 |
| 8 Oct 2026, 21:38 | 126 | +3 |
| 28 Sept 2026, 05:19 | 123 | +1 |
| 14 Sept 2026, 05:59 | 122 | +1 |
| 6 Sept 2026, 02:22 | 121 | +2 |
| 28 Aug 2026, 00:27 | 119 | -1 |
| 20 Aug 2026, 03:22 | 120 | -1 |
| 12 Aug 2026, 23:35 | 121 | +3 |
| 6 Aug 2026, 00:14 | 118 | 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.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“🌐 Hacking y Seguridad” (@hackingyseguridad), 132 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/hackingyseguridad.
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.