Telegram RegisterThe public register of Telegram
Telegram profile photo for Hazzy DC List

Channel

Hazzy DC List

@hazzydclist

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

7subscribers

+4 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-1003854107205
TypeChannel
Username@hazzydclist
Created5 June 2026 — measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live12 November 2026
Measurements held5
Confirmed unchanged7 times, most recently 12 November 2026
On Telegramt.me/hazzydclist

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 2 October 2026 and assigned it the closest of 31 fixed categories, at 82% 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

3757 August 2026 — 3 subscribers13 August 2026 — 3 subscribers16 August 2026 — 4 subscribers10 September 2026 — 5 subscribers19 September 2026 — 7 subscribers7 August 202619 September 2026
5 measurements spanning 43 days, net +4. 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 2–8 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 12:167+2
10 Sept 2026, 14:015+1
16 Aug 2026, 20:054+1
13 Aug 2026, 15:313no change
7 Aug 2026, 19:343first reading

Engagement

2 posts held, back to 5 June 2026 — 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 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

5 Jun 2026, 17:50 UTC≈2,090 views0 reactionsread 13 August 2026

🇺🇾 Discord Username Store 🇺🇾 Every username in this shop comes with their OGE in Hotmail/Outlook ! @gii BIN: $175 @Ivk BIN: $ 155 @vos BIN: $200 @cxt BIN: $135 @99z BIN: $100 @k2s BIN: $85 @6am BIN: $115 @tuw BIN: $185 @sx_ BIN: $75 @q.r BIN: $70 @pxl BIN: $130 @_99 BIN: $100 @ssk BIN: $185 @d1y BIN: $80 @MDR BIN: $160 @_yv BIN: $100 @etv BIN: $210 @vs. BIN: $95 @77v BIN: $85 @rt_ BIN: $75…

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

“Hazzy DC List” (@hazzydclist), 7 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/hazzydclist.

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.