.

Channel
Hack & security
@Hacking_security100
On this record: Topic · Growth · Engagement · Posts · Cite this entry
115subscribers
-5 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001497895921 |
|---|---|
| Type | Channel |
| Username | @Hacking_security100 |
| Created | Between 1 September 2019 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/Hacking_security100 |
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 26 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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 |
|---|---|---|
| 4 Nov 2026, 15:06 | 115 | -1 |
| 27 Sept 2026, 04:22 | 116 | -1 |
| 6 Sept 2026, 10:55 | 117 | -2 |
| 15 Aug 2026, 17:55 | 119 | -1 |
| 9 Aug 2026, 04:02 | 120 | no change |
| 6 Aug 2026, 23:53 | 120 | first reading |
Engagement
20 posts held, back to 19 October 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 1 November 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
.
✅ امروز مسابقه داریم ! ⏰ راس ساعت 10:00🔥 📌 سطح مسابقه : آسان 📚 پیش نیاز : مقدمات برنامه نویسی ⌨ زبان برنامه نویسی : دلخواه ✏️ تمرینات برنامه نویسی (@Coding_Warriors) 🤖 ربات برگزاری مسابقات (@Coding_WarriorBot)
#جلسه_سوم ✅ آموزش کاربرد پایتون در هک و امنیت 🆔 @Hacking_Security100
#جلسه_دوم ✅ آموزش کاربرد پایتون در هک و امنیت 🆔 @Hacking_Security100
#جلسه_اول ✅ آموزش کاربرد پایتون در هک و امنیت 🆔 @Hacking_Security100
#جلسه_بیستوپنجم ✅ آموزش ورود به دنیای هک قانونمند و امنیت 🆔 @Hacking_Security100
#جلسه_بیستوچهارم ✅ آموزش ورود به دنیای هک قانونمند و امنیت 🆔 @Hacking_Security100
#جلسه_بیستوسوم ✅ آموزش ورود به دنیای هک قانونمند و امنیت 🆔 @Hacking_Security100
#جلسه_بیستودوم ✅ آموزش ورود به دنیای هک قانونمند و امنیت 🆔 @Hacking_Security100
#جلسه_بیستویکم ✅ آموزش ورود به دنیای هک قانونمند و امنیت 🆔 @Hacking_Security100
#جلسه_بیستم ✅ آموزش ورود به دنیای هک قانونمند و امنیت 🆔 @Hacking_Security100
Showing the 12 most recent of 20 posts we hold for @Hacking_security100. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Hack & security” (@Hacking_security100), 115 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/Hacking_security100.
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.