Telegram RegisterThe public register of Telegram

Channel

Шокер Шоу •

@shocker_show

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

13subscribers

+0 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-1002054484904
TypeChannel
Username@shocker_show
DescriptionСамый разный контент. Такое вряд ли увидишь на других каналах. Подпишись на Шокер Шоу!
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/shocker_show

Growth

137 August 2026 — 13 subscribers12 August 2026 — 13 subscribers7 August 202612 August 2026
2 measurements spanning 5 days. 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 12–14 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 03:4513no change
7 Aug 2026, 11:4213first reading

Engagement

20 posts held, back to 14 January 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 27 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
52
Videos
741
Links
2

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
7m 37s
Average length
25s

Measured directly from 18 videos 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.

Reaction mix

43 reactions across 16 posts, in 5 distinct kinds. The most used accounts for 41.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1841.9%
1023.3%
👍920.9%
🤣49.30%
😱24.65%

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 16 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 43reactions 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 14 January 2025 to 27 February 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

27 Feb 2026, 18:11 UTC12 viewsread 12 August 2026

Гигантские крысы спасают людей! Это - африканские сумчатые или гамбийские крысы, которых кмбоджийские власти используют для разминирования своей территории после кровавого правления красных кхмеров. Почему именно эти животные? Ответ прост - у них невероятно сильное обоняние, они легко находят мины и не подрываются на них из-за своей легкого веса (около 2 кг), также они поддаются дрессировке и эффективно выполняют п

6 Jan 2026, 09:36 UTC24 views4 reactionsread 12 August 2026
Video

В Китае построили целый ледяной город в Харбине. Скульпторы возвели замки, длинные горки и другие арт-объекты из льда со снегом. В Харбин ходят прямые рейсы из России

2🔥2

24 Nov 2025, 21:32 UTC31 views5 reactionsread 12 August 2026
Video

Рад был помочь @y316_bot

🔥3👍1🤣1

18 Oct 2025, 04:46 UTC34 views2 reactionsread 12 August 2026
Photo

Психологи заявили, что мужчины, нарушающие ПДД, чаще оказываются ЛУЧШИМИ мужьями. Если мужчина не боится пересечь двойную сплошную или превысить скорость — то и жизненные трудности его не пугают. Психологи заявляют, что такой человек умеет принимать решения и творчески решает проблемы.

👍1🤣1

9 Oct 2025, 20:18 UTC27 views4 reactionsread 12 August 2026
Video

Китай стоит в ГИГАНТСКИХ пробках — водители проводят в пути больше суток. Всё из-за Праздника середины осени, когда вся страна одновременно уходит на каникулы. Дороги забились так, что трасса Пекин-Гонконг-Макао вместо привычных 10 часов растянулась до 20-25 часов. Хуже этого могут быть только вечерние пробки в Москве.

2👍2

6 Oct 2025, 03:12 UTC20 views2 reactionsread 12 August 2026
Video

❗️В Китае прошёл настоящий ОГНЕННЫЙ дождь — дроны на шоу зажглись прямо в небе, когда к программе добавили фейерверки. Но пылающие квадрокоптеры неожиданно посыпались вниз — десятки штук упали прямо на людей. С такими перформансами нам и инопланетного вторжения не надо 💀

😱2

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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“Шокер Шоу •” (@shocker_show), 13 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/shocker_show.

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.