Channel
Stop (Djvu) Ransomware
@stopransomware
On this record: Topic · Growth · Engagement · Cite this entry
1,105subscribers
-41 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001446594310 |
|---|---|
| Type | Channel |
| Username | @stopransomware |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 October 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 2 times, most recently 31 October 2026 |
| On Telegram | t.me/stopransomware |
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 6 October 2026 and assigned it the closest of 31 fixed categories, at 83% 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 |
|---|---|---|
| 27 Oct 2026, 23:11 | 1,105 | -2 |
| 19 Oct 2026, 02:26 | 1,107 | -3 |
| 16 Oct 2026, 07:16 | 1,110 | -1 |
| 13 Oct 2026, 11:49 | 1,111 | -6 |
| 7 Oct 2026, 06:41 | 1,117 | -3 |
| 6 Oct 2026, 04:51 | 1,120 | no change |
| 30 Sept 2026, 13:16 | 1,120 | -12 |
| 19 Sept 2026, 17:21 | 1,132 | -1 |
| 15 Sept 2026, 04:40 | 1,133 | -1 |
| 11 Sept 2026, 10:18 | 1,134 | -4 |
| 6 Sept 2026, 17:38 | 1,138 | -3 |
| 1 Sept 2026, 22:57 | 1,141 | -1 |
| 27 Aug 2026, 07:35 | 1,142 | -1 |
| 20 Aug 2026, 16:38 | 1,143 | -2 |
| 17 Aug 2026, 14:14 | 1,145 | -1 |
| 14 Aug 2026, 08:25 | 1,146 | -1 |
| 8 Aug 2026, 06:55 | 1,147 | +1 |
| 7 Aug 2026, 15:38 | 1,146 | 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 27 October 2026 — this entry's latest reading, not the date you are reading this.
“Stop (Djvu) Ransomware” (@stopransomware), 1,105 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/stopransomware.
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.