Channel
Infosec and Risk Management docs, memes and shit
@iso27001
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,611subscribers
+11 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 | -1001819583693 |
|---|---|
| Type | Channel |
| Usernames | @InfoSec_and_Risk_Management @iso27001 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 3 times, most recently 18 September 2026 |
| On Telegram | t.me/iso27001 |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 14 Sept 2026, 09:56 | 4,611 | no change |
| 14 Sept 2026, 09:37 | 4,611 | +9 |
| 10 Sept 2026, 20:36 | 4,602 | no change |
| 10 Sept 2026, 12:36 | 4,602 | -5 |
| 5 Sept 2026, 19:18 | 4,607 | no change |
| 5 Sept 2026, 08:57 | 4,607 | -2 |
| 2 Sept 2026, 22:47 | 4,609 | no change |
| 1 Sept 2026, 23:18 | 4,609 | +3 |
| 1 Sept 2026, 14:39 | 4,606 | -1 |
| 31 Aug 2026, 21:30 | 4,607 | +1 |
| 30 Aug 2026, 00:16 | 4,606 | +2 |
| 27 Aug 2026, 06:05 | 4,604 | +3 |
| 24 Aug 2026, 12:08 | 4,601 | +4 |
| 21 Aug 2026, 05:53 | 4,597 | +2 |
| 17 Aug 2026, 20:16 | 4,595 | -1 |
| 14 Aug 2026, 20:15 | 4,596 | -2 |
| 11 Aug 2026, 16:22 | 4,598 | -4 |
| 8 Aug 2026, 05:56 | 4,602 | +2 |
| 7 Aug 2026, 12:08 | 4,600 | 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.
@dailywalkinjobs · 37,466
Telegram ranks this channel #13 of 48 here — alongside 47 others — read 31 August 2026
@BlueTeamOps · 27,712
Telegram ranks this channel #39 of 53 here — alongside 52 others — read 11 September 2026
This channel appears in 2 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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Infosec and Risk Management docs, memes and shit” (@iso27001), 4,611 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/iso27001.
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.