Telegram RegisterThe public register of Telegram
Telegram profile photo for CyberHero Team | PUBG Mobile

Channel

CyberHero Team | PUBG Mobile

@cyberheropubgm

On this record: Topic · Growth · Engagement · Reactions · Advertising · Posts · Citations · Cite this entry

1,401subscribers

+10 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003545385728
TypeChannel
Username@cyberheropubgm
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/cyberheropubgm

Topic

Gaming — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

1,3381,4011,369.56 August 2026 — 1,391 subscribers7 August 2026 — 1,391 subscribers9 August 2026 — 1,387 subscribers13 August 2026 — 1,385 subscribers16 August 2026 — 1,372 subscribers19 August 2026 — 1,368 subscribers23 August 2026 — 1,359 subscribers26 August 2026 — 1,355 subscribers29 August 2026 — 1,345 subscribers1 September 2026 — 1,338 subscribers5 September 2026 — 1,358 subscribers10 September 2026 — 1,368 subscribers13 September 2026 — 1,383 subscribers18 September 2026 — 1,401 subscribers6 August 202618 September 2026
14 measurements spanning 42 days, net +10. 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,329–1,410 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 03:011,401+18
13 Sept 2026, 22:571,383+15
10 Sept 2026, 09:161,368+10
5 Sept 2026, 12:561,358+20
1 Sept 2026, 19:041,338-7
29 Aug 2026, 16:021,345-10
26 Aug 2026, 08:571,355-4
23 Aug 2026, 14:551,359-9
19 Aug 2026, 21:421,368-4
16 Aug 2026, 20:561,372-13
13 Aug 2026, 05:081,385-2
9 Aug 2026, 23:311,387-4
7 Aug 2026, 03:461,391no change
6 Aug 2026, 23:461,391first reading

Engagement

20 posts held, back to 18 July 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

447 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 44.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤19744.1%
⚡10924.4%
🔥10022.4%
👍173.80%
custom 5355333157321212261132.91%
custom 535707439719255399940.895%
🌚40.895%
😈30.671%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 447 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 18 July 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Advertising

Ad load
5.00%
1 of 20 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
535
over 1 measured post
Median views · rest
550
over 19 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
CQH36pWzJqMkuqb6bxVchHuyqZGapYfHxwy4HsGdy3JugA128 July 202628 July 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 20 most recent posts we hold, published 18 July 2026 to 6 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

6 Aug 2026, 13:31 UTC184 views9 reactionsread 6 August 2026
Photo

Знатоки, снова ваш выход 😎

⚡6❤3

5 Aug 2026, 18:31 UTC270 views24 reactionsread 6 August 2026
Photo

Будете смотреть турнир или без нас не интересно? 🤔

❤14⚡4🔥3custom 53570743971925539992👍1

4 Aug 2026, 14:34 UTC305 views13 reactionsread 6 August 2026
Photo

Готовы сегодня оценить кроссовер с Наруто? 🧐

⚡6❤3🔥3👍1

3 Aug 2026, 13:33 UTC338 views14 reactionsread 6 August 2026
Photo

Шарющие за фильм Королевская битва присутствуют?

⚡10❤2custom 53570743971925539992

2 Aug 2026, 14:31 UTC406 views7 reactionsread 6 August 2026
Photo

Уже заценили Друваэна? 🤔

⚡2❤2🔥2👍1

1 Aug 2026, 14:30 UTC424 views7 reactionsread 6 August 2026
Photo

Успели найти полезные баг-фиксы? 😙

❤4🔥2⚡1

31 Jul 2026, 13:33 UTC465 views37 reactionsread 6 August 2026
Photo

Горячие штучки на базе? 👆

❤30🔥3😈3⚡1

30 Jul 2026, 13:35 UTC492 views36 reactionsread 6 August 2026
Photo

Регулярный интерактивчик про режимы на базе. Что у вас по предпочтениям на данный момент? 😋

❤30🔥3👍2⚡1

29 Jul 2026, 16:54 UTC511 views17 reactionsread 6 August 2026
Photo

Знать ник создателя игры — достаточно нишево или нет? 😙

⚡12❤5

28 Jul 2026, 13:48 UTC535 views6 reactionsread 6 August 2026
Advertisementerid CQH36pWzJqMkuqb6bxVchHuyqZGapYfHxwy4HsGdy3JugAPhoto

Тоже хочешь ловить новые скины за 10 UC? В тарифе MiXX PLAY PRO, помимо интернета и пополнения Steam без комиссии каждый месяц вам будут начислять 180 UC на рулеточки: https://u.t2.ru/mixx_play_pro 🤩 Реклама ООО «Т2 Мобайл» ИНН 7743895280 erid: CQH36pWzJqMkuqb6bxVchHuyqZGapYfHxwy4HsGdy3JugA

❤4🔥1custom 53553331573212122611

27 Jul 2026, 14:33 UTC550 views13 reactionsread 6 August 2026
Photo

Падеры на месте? 🤔

❤9⚡3🔥1

26 Jul 2026, 13:31 UTC588 views65 reactionsread 6 August 2026
Photo

Что лучше оставить третьей картой в киберспорте? 😏

🔥52❤13

Showing the 12 most recent of 20 posts we hold for @cyberheropubgm. 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.

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

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“CyberHero Team | PUBG Mobile” (@cyberheropubgm), 1,401 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/cyberheropubgm.

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.