Channel
SECCURITY_TESTING
@seccurity_testing
On this record: Topic · Growth · Engagement · Cite this entry
488subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001286580090 |
|---|---|
| Type | Channel |
| Username | @seccurity_testing |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 October 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 3 times, most recently 5 November 2026 |
| On Telegram | t.me/seccurity_testing |
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 13 October 2026 and assigned it the closest of 31 fixed categories, at 75% 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 |
|---|---|---|
| 22 Oct 2026, 11:36 | 488 | -2 |
| 14 Oct 2026, 05:41 | 490 | +2 |
| 12 Oct 2026, 05:13 | 488 | no change |
| 5 Oct 2026, 16:59 | 488 | +1 |
| 25 Sept 2026, 03:55 | 487 | -1 |
| 5 Sept 2026, 02:41 | 488 | -2 |
| 28 Aug 2026, 06:55 | 490 | +2 |
| 21 Aug 2026, 10:46 | 488 | -2 |
| 15 Aug 2026, 06:52 | 490 | -5 |
| 8 Aug 2026, 02:05 | 495 | -1 |
| 7 Aug 2026, 06:39 | 496 | 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 22 October 2026 — this entry's latest reading, not the date you are reading this.
“SECCURITY_TESTING” (@seccurity_testing), 488 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/seccurity_testing.
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.