Telegram RegisterThe public register of Telegram
Telegram profile photo for https://t.me/pubghack_pro

Channel

https://t.me/pubghack_pro

@pubghack_pro

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

2subscribers

+1 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-1003688001046
TypeChannel
Username@pubghack_pro
Created4 August 2026 — measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live18 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/pubghack_pro

Topic

Hacking & security — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 18 November 2026 and assigned it the closest of 31 fixed categories, at 64% 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

121.57 August 2026 — 1 subscribers14 August 2026 — 1 subscribers18 November 2026 — 2 subscribers7 August 202618 November 2026
3 measurements spanning 103 days, net +1. 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 1–2 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Nov 2026, 08:592+1
14 Aug 2026, 18:341no change
7 Aug 2026, 15:551first reading

Engagement

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

Recent posts

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

“https://t.me/pubghack_pro” (@pubghack_pro), 2 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/pubghack_pro.

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.