Channel
SecEasy Channel
@SecEasy
On this record: Topic · Growth · Engagement · Cite this entry
1,910subscribers
-48 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001219192496 |
|---|---|
| Type | Channel |
| Username | @SecEasy |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 September 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/SecEasy |
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 22 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) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 01:18 | 1,910 | -1 |
| 4 Oct 2026, 22:18 | 1,911 | -5 |
| 25 Sept 2026, 12:36 | 1,916 | -9 |
| 21 Sept 2026, 23:13 | 1,925 | no change |
| 17 Sept 2026, 01:19 | 1,925 | -1 |
| 13 Sept 2026, 06:40 | 1,926 | -3 |
| 8 Sept 2026, 22:59 | 1,929 | -3 |
| 3 Sept 2026, 14:57 | 1,932 | -3 |
| 31 Aug 2026, 18:35 | 1,935 | -3 |
| 29 Aug 2026, 05:08 | 1,938 | -1 |
| 26 Aug 2026, 14:04 | 1,939 | -1 |
| 23 Aug 2026, 03:18 | 1,940 | -2 |
| 19 Aug 2026, 17:03 | 1,942 | -4 |
| 16 Aug 2026, 17:13 | 1,946 | -5 |
| 13 Aug 2026, 00:52 | 1,951 | -3 |
| 10 Aug 2026, 01:22 | 1,954 | -3 |
| 7 Aug 2026, 07:04 | 1,957 | -1 |
| 6 Aug 2026, 16:58 | 1,958 | 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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“SecEasy Channel” (@SecEasy), 1,910 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/SecEasy.
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.