Telegram RegisterThe public register of Telegram
Telegram profile photo for PUNKSHOW Off

Channel

PUNKSHOW Off

@PUNKSHOW18

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

5,427subscribers

+5 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002270202555
TypeChannel
Username@PUNKSHOW18
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live29 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/PUNKSHOW18

Growth

5,4145,4295,421.59 August 2026 — 5,422 subscribers10 August 2026 — 5,417 subscribers13 August 2026 — 5,414 subscribers16 August 2026 — 5,429 subscribers19 August 2026 — 5,424 subscribers22 August 2026 — 5,429 subscribers25 August 2026 — 5,426 subscribers29 August 2026 — 5,427 subscribers5,4279 August 202629 August 2026
8 measurements spanning 19 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 5,412–5,431 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 01:545,427+1
25 Aug 2026, 17:365,426-3
22 Aug 2026, 19:375,429+5
19 Aug 2026, 14:035,424-5
16 Aug 2026, 19:445,429+15
13 Aug 2026, 12:355,414-3
10 Aug 2026, 08:115,417-5
9 Aug 2026, 19:475,422first reading

Engagement

17 posts held, back to 8 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
30.3%
avg views ÷ 5,427 subscribers
Avg views / post
1,650
5 posts measured
Reaction rate
4.22%
reactions ÷ views · ER floor
Posts in window
5
of 17 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held17 (8 July 20269 August 2026)
Views total8,230
Reactions total347
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 04:18 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

1,030 reactions across 17 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52626439362576623271,030100.0%

Custom emoji. One row above is a 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 count beside it isTelegram’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 17 of the 17 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 1,030reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 8 July 2026 to 9 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.

Recent posts

9 Aug 2026, 17:19 UTC≈1,050 views41 reactionsread 12 August 2026

Бля тока на стриме рассказывал, что рядом со мной эта хуила пизданула и ослепила, когда я в магаз шел. Я хз...она не она или другая, но про этих зверей даж в новостях пишут( Опять чуть не сдох слуайно седня(

custom 526264393625766232741

9 Aug 2026, 15:58 UTC≈1,180 views50 reactionsread 12 August 2026
Photo

На пофапать. А стрим начался коммон: https://youtube.com/live/9LV_cNodySM?feature=share

custom 526264393625766232750

9 Aug 2026, 13:10 UTC≈1,220 views58 reactionsread 12 August 2026
Photo

Сиводня стриииим братишки, 19:00 по мск, всех жду

custom 526264393625766232758

3 Aug 2026, 03:30 UTC≈2,350 views114 reactionsread 12 August 2026

Блин пацаны, спасибо что вы не тупые. А то я жёстко от тупости людей охуиваю по практически всем вопросам мироздания

custom 5262643936257662327114

2 Aug 2026, 12:35 UTC≈2,430 views84 reactionsread 12 August 2026
Photo

Здарова всем, седня стрим в 19:00 по мск. Кстати во нашел на детскую фотку, про которую на прошлом говорил

custom 526264393625766232784

26 Jul 2026, 10:36 UTC≈3,340 views67 reactionsread 12 August 2026
Photo

привет мои коровята(ну я и уебок седня) а раз я уебок, возможно седня стрим в 19:00 по мск будет смешным, на прошлом пиздато поговорили про маньяков туда сюда и это в четверг было, но бля традиционное воскресенье тоже важно, как у католиков

custom 526264393625766232767

24 Jul 2026, 21:15 UTC≈3,240 views69 reactionsread 12 August 2026
Photo

не работаю на дядю я уже давно сам дядя, эта хуйня рил выглядит как бдсм чешское порно с игрушечной коровой и там еще есть теленок, чтобы посадить его на кресло, чтобы он смотрел, там еще за лям двести есть доильный тренажер и отрезать этой сиську четверную и приделать сиську интерактивную. Короче мне кинуло эту хуйню в таргете на сайте с шахматами, вот куда приводят шутки про пизду коровы. А вы знали про существован

custom 526264393625766232769

19 Jul 2026, 10:28 UTC≈3,500 views44 reactionsread 12 August 2026
Voice message

Voice message, posted without a caption

custom 526264393625766232744

11 Jul 2026, 23:56 UTC≈4,010 views51 reactionsread 12 August 2026

Сука Хааленд все запорол, а я в него верил сука

custom 526264393625766232751

10 Jul 2026, 14:52 UTC≈4,060 views60 reactionsread 12 August 2026

Пацаны рил не спамьте, один бы кто написал и все, просто послы на хуй один такой хороший добрый на хуй. Пс. если чо каждый может брать мои работы и постить к себе на страничку куда хочет и писать под ними чо хочет, хоть ГРАНЖЕР ХУИСОС. Можете хоть перерисовывать их, хоть че ваще. Мне похер ебал авторское право пиратство могает. Ну вы это и так знаете

custom 526264393625766232760

10 Jul 2026, 14:49 UTC≈3,880 views43 reactionsread 12 August 2026
Photo

антиваксеры я антиваксер я никогда не кололся спутником ковид мой друг антиваксер засуди меня🍒🎂

custom 526264393625766232743

10 Jul 2026, 14:42 UTC≈3,500 views42 reactionsread 12 August 2026

Кому в бан не жалко отлететь там, напишите плиз в комментах :ой иди ты нахуй от гранжера

custom 526264393625766232742

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

Citation-graph rank

Citation-graph rank — 1,106,265 of 1,627,445entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

Names

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

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

“PUNKSHOW Off” (@PUNKSHOW18), 5,427 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/PUNKSHOW18.

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.