Telegram RegisterThe public register of Telegram
Telegram profile photo for Pubg Esp

Channel

Pubg Esp

@pubgesps

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

716subscribers

-44 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-1001407822174
TypeChannel
Username@pubgesps
Created18 May 2021 — measured — dated from the channel’s first post
First recorded6 September 2026
Last confirmed live29 October 2026
Measurements held10
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/pubgesps

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 36% 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

7167607387 August 2026 — 760 subscribers15 August 2026 — 751 subscribers23 August 2026 — 745 subscribers29 August 2026 — 743 subscribers6 September 2026 — 743 subscribers8 September 2026 — 737 subscribers28 September 2026 — 729 subscribers9 October 2026 — 723 subscribers22 October 2026 — 718 subscribers29 October 2026 — 716 subscribers7 August 202629 October 2026
10 measurements spanning 83 days, net -44. 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 709–767 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Oct 2026, 12:35716-2
22 Oct 2026, 16:16718-5
9 Oct 2026, 05:19723-6
28 Sept 2026, 08:54729-8
8 Sept 2026, 04:39737-6
6 Sept 2026, 01:22743no change
29 Aug 2026, 05:47743-2
23 Aug 2026, 00:07745-6
15 Aug 2026, 17:36751-9
7 Aug 2026, 01:06760first reading

Engagement

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

What this channel posts

Video runtime
7m 32s
Average length
7m 32s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

13 Aug 2026, 03:04 UTC144 viewsread 6 September 2026
Forwarded from @manifesto_appVideo

The manifesto will be released upon the reaching of at least 1,000 users on telegram. Therefore, please share and encourage others to reach this 1,000-user threshold to secure a free release for all. Otherwise, the manifesto will remain private indefinitely. Its features include: - APK editing - Dex editor - .so file editor - Flutter decompiler and editor - Frida analysis with support for both rooted and non-rooted …

Signed nhCoder

Showing the 2 most recent of 2 posts we hold for @pubgesps. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

binManager
@binManager · 5351 postHackerz Network
@heaven_officially · 9881 post

Republishes

Channels on the register whose posts this channel has forwarded.

Manifesto
@manifesto_app · 331 post

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

Manifesto
@manifesto_app · 331 post

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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 29 October 2026 — this entry's latest reading, not the date you are reading this.

“Pubg Esp” (@pubgesps), 716 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/pubgesps.

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.