Channel
NEURO H4CK
@appexsoft
On this record: Topic · Growth · Engagement · Cite this entry
2,363subscribers
+64 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 | -1002554491230 |
|---|---|
| Type | Channel |
| Username | @appexsoft |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/appexsoft |
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 71% 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, 22:20 | 2,363 | -37 |
| 5 Oct 2026, 11:39 | 2,400 | -25 |
| 27 Sept 2026, 04:19 | 2,425 | +116 |
| 18 Sept 2026, 14:44 | 2,309 | no change |
| 18 Sept 2026, 05:41 | 2,309 | +152 |
| 14 Sept 2026, 04:21 | 2,157 | -16 |
| 10 Sept 2026, 19:21 | 2,173 | -21 |
| 6 Sept 2026, 03:16 | 2,194 | -24 |
| 1 Sept 2026, 13:56 | 2,218 | -10 |
| 29 Aug 2026, 23:57 | 2,228 | -16 |
| 26 Aug 2026, 23:13 | 2,244 | -9 |
| 24 Aug 2026, 07:04 | 2,253 | -8 |
| 20 Aug 2026, 13:03 | 2,261 | -9 |
| 17 Aug 2026, 17:07 | 2,270 | -2 |
| 14 Aug 2026, 20:37 | 2,272 | -11 |
| 11 Aug 2026, 09:12 | 2,283 | -15 |
| 8 Aug 2026, 04:35 | 2,298 | -1 |
| 7 Aug 2026, 17:15 | 2,299 | 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.
“NEURO H4CK” (@appexsoft), 2,363 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/appexsoft.
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.