Channel
SecureCoders | تست نفوذ
@securecoders
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,266subscribers
+23 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 | -1001977949157 |
|---|---|
| Type | Channel |
| Username | @securecoders |
| Description | آی دی ادمین: @p3ym4n_mhp |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| On Telegram | t.me/securecoders |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 00:49 | 2,266 | no change |
| 16 Sept 2026, 03:36 | 2,266 | +2 |
| 12 Sept 2026, 19:55 | 2,264 | +4 |
| 9 Sept 2026, 01:59 | 2,260 | +9 |
| 3 Sept 2026, 07:45 | 2,251 | +1 |
| 30 Aug 2026, 15:54 | 2,250 | +1 |
| 27 Aug 2026, 15:04 | 2,249 | +1 |
| 24 Aug 2026, 16:28 | 2,248 | +7 |
| 20 Aug 2026, 22:04 | 2,241 | +1 |
| 14 Aug 2026, 12:28 | 2,240 | -5 |
| 10 Aug 2026, 19:11 | 2,245 | +2 |
| 7 Aug 2026, 13:07 | 2,243 | 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.
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.
@kali_linuxxx · 75,988
Telegram ranks this channel #21 of 60 here — alongside 59 others — read 19 August 2026
@cyberbannews_ir · 109,325
Telegram ranks this channel #27 of 62 here — alongside 61 others — read 24 August 2026
@Black_Security · 63,929
Telegram ranks this channel #36 of 64 here — alongside 63 others — read 21 August 2026
@hamidrezasotoudeh98 · 72,689
Telegram ranks this channel #36 of 89 here — alongside 88 others — read 20 August 2026
@AOrgan · 47,423
Telegram ranks this channel #47 of 63 here — alongside 62 others — read 24 August 2026
@Netwo0rk · 52,767
Telegram ranks this channel #55 of 63 here — alongside 62 others — read 24 August 2026
@Pythoni_Developers · 75,374
Telegram ranks this channel #62 of 82 here — alongside 81 others — read 19 August 2026
This channel appears in 7 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“SecureCoders | تست نفوذ” (@securecoders), 2,266 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/securecoders.
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.