Telegram RegisterThe public register of Telegram
Telegram profile photo for SVG

Channel

SVG

@hex80

On this record: Topic · Growth · Engagement · Posts · Cite this entry

94subscribers

+5 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002283454407
TypeChannel
Username@hex80
Created5 January 2025 — measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live10 November 2026
Measurements held11
Confirmed unchanged2 times, most recently 10 November 2026
On Telegramt.me/hex80

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 27 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 the other topics.

Growth

819487.57 August 2026 — 89 subscribers9 August 2026 — 89 subscribers23 August 2026 — 81 subscribers31 August 2026 — 84 subscribers10 September 2026 — 85 subscribers17 September 2026 — 84 subscribers2 October 2026 — 89 subscribers13 October 2026 — 91 subscribers21 October 2026 — 92 subscribers28 October 2026 — 93 subscribers3 November 2026 — 94 subscribers7 August 20263 November 2026
11 measurements spanning 88 days, net +5. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 79–96 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 22:4794+1
28 Oct 2026, 11:2793+1
21 Oct 2026, 07:5692+1
13 Oct 2026, 06:0191+2
2 Oct 2026, 08:4189+5
17 Sept 2026, 15:3984-1
10 Sept 2026, 01:3785+1
31 Aug 2026, 00:3584+3
23 Aug 2026, 11:2581-8
9 Aug 2026, 15:1789no change
7 Aug 2026, 21:2089first reading

Engagement

2 posts held, back to 5 January 2025 — 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 2 posts for this entry, the most recent from 5 January 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

5 Jan 2025, 18:36 UTC≈63,900 viewsread 9 August 2026
Photo

User - x Name - Vlad Age - x Website hacking of any complexity for $600

Showing the 2 most recent of 2 posts we hold for @hex80. 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 3 November 2026 — this entry's latest reading, not the date you are reading this.

“SVG” (@hex80), 94 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/hex80.

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.