
Channel
HupSMS
@HupSMScom
On this record: Topic · Growth · Engagement · Cite this entry
2,404subscribers
+795 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 | -1003348154554 |
|---|---|
| Type | Channel |
| Username | @HupSMScom |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 September 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/HupSMScom |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 |
|---|---|---|
| 6 Oct 2026, 03:38 | 2,404 | +99 |
| 28 Sept 2026, 18:20 | 2,305 | +197 |
| 19 Sept 2026, 22:48 | 2,108 | no change |
| 15 Sept 2026, 13:39 | 2,108 | +39 |
| 12 Sept 2026, 08:40 | 2,069 | +55 |
| 8 Sept 2026, 11:56 | 2,014 | +79 |
| 3 Sept 2026, 08:57 | 1,935 | +50 |
| 31 Aug 2026, 08:04 | 1,885 | +33 |
| 28 Aug 2026, 04:17 | 1,852 | +36 |
| 25 Aug 2026, 01:33 | 1,816 | +62 |
| 21 Aug 2026, 11:49 | 1,754 | +32 |
| 18 Aug 2026, 01:33 | 1,722 | +22 |
| 14 Aug 2026, 20:37 | 1,700 | +54 |
| 11 Aug 2026, 15:36 | 1,646 | +32 |
| 8 Aug 2026, 10:57 | 1,614 | +5 |
| 7 Aug 2026, 21:22 | 1,609 | 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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“HupSMS” (@HupSMScom), 2,404 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/HupSMScom.
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.