Channel
Cybersecurity Study Group
@cybersecuritycare
On this record: Growth · Engagement · Telegram's recommendations · Cite this entry
13,169subscribers
+248 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001722889059 |
|---|---|
| Type | Channel |
| Username | @cybersecuritycare |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/cybersecuritycare |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 09:21 | 13,169 | +31 |
| 7 Sept 2026, 04:18 | 13,138 | +14 |
| 4 Sept 2026, 15:16 | 13,124 | +15 |
| 3 Sept 2026, 01:15 | 13,109 | +14 |
| 1 Sept 2026, 23:25 | 13,095 | -3 |
| 1 Sept 2026, 01:17 | 13,098 | +16 |
| 31 Aug 2026, 01:04 | 13,082 | +8 |
| 30 Aug 2026, 03:14 | 13,074 | +8 |
| 29 Aug 2026, 06:28 | 13,066 | +12 |
| 28 Aug 2026, 06:28 | 13,054 | +4 |
| 27 Aug 2026, 09:54 | 13,050 | +4 |
| 26 Aug 2026, 11:22 | 13,046 | +9 |
| 24 Aug 2026, 08:07 | 13,037 | +17 |
| 22 Aug 2026, 17:28 | 13,020 | +17 |
| 21 Aug 2026, 10:25 | 13,003 | +11 |
| 20 Aug 2026, 10:17 | 12,992 | +10 |
| 20 Aug 2026, 09:58 | 12,982 | no change |
| 19 Aug 2026, 13:36 | 12,982 | +12 |
| 18 Aug 2026, 10:45 | 12,970 | +12 |
| 17 Aug 2026, 14:07 | 12,958 | first reading |
Engagement
No public post preview. We read this entry on 20 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.
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.
@udemyrip · 67,840
Telegram ranks this channel #22 of 36 here — alongside 35 others — read 21 August 2026
@learningnets · 30,417
Telegram ranks this channel #24 of 56 here — alongside 55 others — read 7 September 2026
@pythonadvisorai · 32,293
Telegram ranks this channel #31 of 71 here — alongside 70 others — read 5 September 2026
@codelivly · 35,330
Telegram ranks this channel #35 of 41 here — alongside 40 others — read 8 September 2026
@ctinow · 37,976
Telegram ranks this channel #35 of 42 here — alongside 41 others — read 31 August 2026
@thehackernews · 162,289
Telegram ranks this channel #45 of 58 here — alongside 57 others — read 13 August 2026
@cibsecurity · 27,941
Telegram ranks this channel #51 of 58 here — alongside 57 others — read 10 September 2026
@Cyber_Security_Channel · 56,541
Telegram ranks this channel #53 of 71 here — alongside 70 others — read 23 August 2026
This channel appears in 8 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“Cybersecurity Study Group” (@cybersecuritycare), 13,169 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/cybersecuritycare.
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.