Supergroup
RUSCADASEC community: Кибербезопасность АСУ ТП
@RUSCADASEC
On this record: Topic · Growth · Engagement · Cite this entry
3,421members
-8 since we began measuring on 6 August 2026
1,140 online right now
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001035519085 |
|---|---|
| Type | Supergroup |
| Username | @RUSCADASEC |
| Created | Between 1 January 2016 and 31 October 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 2 times, most recently 13 September 2026 |
| On Telegram | t.me/RUSCADASEC |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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) | Members | Change |
|---|---|---|
| 9 Sept 2026, 10:21 | 3,421 | +1 |
| 8 Sept 2026, 21:22 | 3,420 | no change |
| 3 Sept 2026, 19:16 | 3,420 | +9 |
| 31 Aug 2026, 17:13 | 3,411 | -7 |
| 29 Aug 2026, 03:42 | 3,418 | +3 |
| 25 Aug 2026, 19:53 | 3,415 | -8 |
| 23 Aug 2026, 01:07 | 3,423 | +3 |
| 19 Aug 2026, 18:52 | 3,420 | -7 |
| 16 Aug 2026, 20:07 | 3,427 | +1 |
| 13 Aug 2026, 02:34 | 3,426 | +3 |
| 10 Aug 2026, 03:20 | 3,423 | -6 |
| 6 Aug 2026, 20:28 | 3,429 | 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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“RUSCADASEC community: Кибербезопасность АСУ ТП” (@RUSCADASEC), 3,421 members as measured 9 September 2026. Telegram Register, tgregister.com/channel/RUSCADASEC.
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.