Telegram RegisterThe public register of Telegram
Telegram profile photo for Cybersecurity Study Group

Channel

Cybersecurity Study Group

@cybersecuritycare

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

13,429subscribers

+508 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
TypeChannel
Username@cybersecuritycare
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 August 2026
Last confirmed live26 October 2026
Measurements held43
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/cybersecuritycare

Topic

Education — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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

12,92113,42913,17513 August 2026 — 12,921 subscribers14 August 2026 — 12,929 subscribers16 August 2026 — 12,945 subscribers17 August 2026 — 12,958 subscribers18 August 2026 — 12,970 subscribers19 August 2026 — 12,982 subscribers20 August 2026 — 12,982 subscribers20 August 2026 — 12,992 subscribers21 August 2026 — 13,003 subscribers22 August 2026 — 13,020 subscribers24 August 2026 — 13,037 subscribers26 August 2026 — 13,046 subscribers27 August 2026 — 13,050 subscribers28 August 2026 — 13,054 subscribers29 August 2026 — 13,066 subscribers30 August 2026 — 13,074 subscribers31 August 2026 — 13,082 subscribers1 September 2026 — 13,098 subscribers1 September 2026 — 13,095 subscribers3 September 2026 — 13,109 subscribers4 September 2026 — 13,124 subscribers7 September 2026 — 13,138 subscribers10 September 2026 — 13,169 subscribers12 September 2026 — 13,174 subscribers14 September 2026 — 13,196 subscribers15 September 2026 — 13,222 subscribers18 September 2026 — 13,250 subscribers30 September 2026 — 13,319 subscribers6 October 2026 — 13,353 subscribers10 October 2026 — 13,373 subscribers13 October 2026 — 13,372 subscribers14 October 2026 — 13,376 subscribers15 October 2026 — 13,378 subscribers17 October 2026 — 13,385 subscribers18 October 2026 — 13,388 subscribers19 October 2026 — 13,391 subscribers20 October 2026 — 13,407 subscribers21 October 2026 — 13,410 subscribers22 October 2026 — 13,412 subscribers23 October 2026 — 13,417 subscribers24 October 2026 — 13,420 subscribers25 October 2026 — 13,426 subscribers26 October 2026 — 13,429 subscribers13 August 202626 October 2026
43 measurements spanning 75 days, net +508. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 12,845–13,505 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 43
Measured (UTC)SubscribersChange
26 Oct 2026, 22:5613,429+3
25 Oct 2026, 20:1813,426+6
24 Oct 2026, 17:5013,420+3
23 Oct 2026, 15:0113,417+5
22 Oct 2026, 14:5913,412+2
21 Oct 2026, 05:2713,410+3
20 Oct 2026, 02:0513,407+16
19 Oct 2026, 00:3013,391+3
18 Oct 2026, 01:5113,388+3
17 Oct 2026, 00:2013,385+7
15 Oct 2026, 23:4613,378+2
14 Oct 2026, 22:0913,376+4
13 Oct 2026, 18:3713,372-1
10 Oct 2026, 05:5913,373+20
6 Oct 2026, 04:4013,353+34
30 Sept 2026, 21:3613,319+69
18 Sept 2026, 04:1813,250+28
15 Sept 2026, 23:1713,222+26
14 Sept 2026, 06:2113,196+22
12 Sept 2026, 14:1813,174first 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.

Cyber Security Jobs
@CyberSecurityJobs · 18,780
Telegram ranks this channel #10 of 47 here — alongside 46 others — read 5 October 2026
Networking | Cisco I Huawei | CISSP | JNICA
@CCNA_CCNP_HUAWEI · 19,276
Telegram ranks this channel #12 of 62 here — alongside 61 others — read 2 October 2026
CyberDost
@cyberdosti4c · 21,714
Telegram ranks this channel #16 of 60 here — alongside 59 others — read 23 September 2026
Learn Cybersecurity
@teammatrixs · 23,728
Telegram ranks this channel #16 of 26 here — alongside 25 others — read 17 September 2026
Udemy
@udemyrip · 68,629
Telegram ranks this channel #22 of 36 here — alongside 35 others — read 21 August 2026
Network Learning
@learningnets · 30,919
Telegram ranks this channel #24 of 56 here — alongside 55 others — read 7 September 2026
All Security Engineering Courses
@AllSecurityEngineeringCourses · 19,275
Telegram ranks this channel #31 of 37 here — alongside 36 others — read 3 October 2026
Codehub
@pythonadvisorai · 31,552
Telegram ranks this channel #31 of 71 here — alongside 70 others — read 5 September 2026
Codelivly - Your Journey To Cybersecurity
@codelivly · 35,172
Telegram ranks this channel #35 of 41 here — alongside 40 others — read 8 September 2026
Cyber Threat Intelligence
@ctinow · 39,717
Telegram ranks this channel #35 of 42 here — alongside 41 others — read 31 August 2026
Pentesting News
@PentestingNews · 27,698
Telegram ranks this channel #36 of 46 here — alongside 45 others — read 12 September 2026
Cyber Guardians
@IRCyberGuardians · 20,664
Telegram ranks this channel #39 of 53 here — alongside 52 others — read 30 September 2026
OSCP+ Exam Resources👩‍💻
@noobtooscp · 23,402
Telegram ranks this channel #39 of 41 here — alongside 40 others — read 19 September 2026
Blue Team | SOC | DFIR | Cloud Security
@BlueTeamOps · 28,222
Telegram ranks this channel #45 of 53 here — alongside 52 others — read 11 September 2026
The Hacker News
@thehackernews · 163,920
Telegram ranks this channel #45 of 58 here — alongside 57 others — read 13 August 2026
Cloud and Cybersecurity
@cloudandcybersecurity · 21,762
Telegram ranks this channel #48 of 62 here — alongside 61 others — read 22 September 2026
🛡 Cybersecurity & Privacy 🛡 - News
@cibsecurity · 28,877
Telegram ranks this channel #51 of 58 here — alongside 57 others — read 10 September 2026
Cyber Security News
@Cyber_Security_Channel · 57,038
Telegram ranks this channel #53 of 71 here — alongside 70 others — read 23 August 2026

This channel appears in 18 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 26 October 2026 — this entry's latest reading, not the date you are reading this.

“Cybersecurity Study Group” (@cybersecuritycare), 13,429 subscribers as measured 26 October 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.