Channel
Security alert
@Alert_Security
On this record: Topic · Growth · Engagement · Cite this entry
984subscribers
-30 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 | -1001292968956 |
|---|---|
| Type | Channel |
| Username | @Alert_Security |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 October 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 30 October 2026 |
| On Telegram | t.me/Alert_Security |
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 9 October 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 |
|---|---|---|
| 30 Oct 2026, 08:37 | 984 | -4 |
| 23 Oct 2026, 04:37 | 988 | -1 |
| 16 Oct 2026, 07:56 | 989 | +1 |
| 10 Oct 2026, 08:57 | 988 | -3 |
| 9 Oct 2026, 05:04 | 991 | no change |
| 30 Sept 2026, 09:57 | 991 | -3 |
| 8 Sept 2026, 13:16 | 994 | -5 |
| 29 Aug 2026, 15:34 | 999 | -1 |
| 26 Aug 2026, 07:07 | 1,000 | -1 |
| 19 Aug 2026, 20:04 | 1,001 | -2 |
| 16 Aug 2026, 20:34 | 1,003 | -5 |
| 13 Aug 2026, 05:34 | 1,008 | -2 |
| 10 Aug 2026, 10:35 | 1,010 | -4 |
| 6 Aug 2026, 20:00 | 1,014 | 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 30 October 2026 — this entry's latest reading, not the date you are reading this.
“Security alert” (@Alert_Security), 984 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/Alert_Security.
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.