Telegram RegisterThe public register of Telegram

Channel

ЭРИК СУКА ШОКОВ

@shoke

Verified by Telegram2 usernames

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

97,201subscribers

-262 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001256644350
TypeChannel
Usernames@shoke @shoketg
DescriptionМикрочел. Серваки: @cybershoke CS2 состав: @team_cybershoke Стендофф состав: @cybershoke_so2 СМИ про CS2: @retakenews Киберклубы в Грузии: instagram.com/cybershoke.kandelaki Связаться лично: @axper
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held15
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/shoke

Growth

97,20197,46497,332.56 August 2026 — 97,463 subscribers6 August 2026 — 97,463 subscribers6 August 2026 — 97,464 subscribers7 August 2026 — 97,439 subscribers7 August 2026 — 97,428 subscribers8 August 2026 — 97,393 subscribers8 August 2026 — 97,394 subscribers9 August 2026 — 97,337 subscribers9 August 2026 — 97,329 subscribers10 August 2026 — 97,294 subscribers10 August 2026 — 97,306 subscribers11 August 2026 — 97,255 subscribers11 August 2026 — 97,255 subscribers12 August 2026 — 97,203 subscribers12 August 2026 — 97,201 subscribers6 August 202612 August 2026
15 measurements spanning 6 days, net -262. 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 97,162–97,503 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 09:1197,201-2
12 Aug 2026, 08:1197,203-52
11 Aug 2026, 09:0397,255no change
11 Aug 2026, 07:0597,255-51
10 Aug 2026, 11:2797,306+12
10 Aug 2026, 07:1097,294-35
9 Aug 2026, 14:1697,329-8
9 Aug 2026, 07:5297,337-57
8 Aug 2026, 12:3597,394+1
8 Aug 2026, 05:0597,393-35
7 Aug 2026, 14:1797,428-11
7 Aug 2026, 07:1897,439-25
6 Aug 2026, 22:1597,464+1
6 Aug 2026, 21:1597,463no change
6 Aug 2026, 21:0497,463first reading

Engagement

30 posts held, back to 20 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 18 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
17.8%
avg views ÷ 97,201 subscribers
Avg views / post
17,300
30 posts measured
Reaction rate
1.17%
reactions ÷ views · ER floor
Posts in window
30
of 30 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 11 August 2026
Posts held30 (20 July 202611 August 2026)
Views total518,570
Reactions total6,042
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 18:36 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.

What this channel posts

Photos
2,980
Videos
416
Links
993

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. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1m 02s
Average length
31s

Measured directly from 2 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

6,042 reactions across 30 posts, in 2 distinct kinds. The most used accounts for 68.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54497351426229068054,10868.0%
custom 54475964121182619531,93432.0%

Custom emoji. Every 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 counts beside them areTelegram’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 30 of the 30 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 6,042reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 30 most recent posts we hold, published 20 July 2026 to 11 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

11 Aug 2026, 15:39 UTC≈4,690 views67 reactionsread 12 August 2026

СОБИРАЕМ ВОПРОСЫ ДЛЯ НОВОГО РОЛИКА! 🎥 Пишите в комментариях всё, что давно хотели у меня спросить - про CYBERSHOKE, бизнес, киберспорт, личное, деньги, планы или вообще что угодно.

custom 544973514262290680567

10 Aug 2026, 13:22 UTC≈6,680 views59 reactionsread 12 August 2026
Video message

Video message, posted without a caption

custom 544973514262290680559

9 Aug 2026, 15:45 UTC≈7,170 views63 reactionsread 12 August 2026
Forwarded from @cybershokePhoto

ГОДНОТА ДЛЯ СТРИМЕРОВ! 😎 Добавили фильтрацию игроков — можно собирать более комфортные лобби для игры на трансляции. • Сортировка по ELO на FACEIT и пингу; • Подписки и статусы: только LITE, PREMIUM, PRO и TALENT; • Функция «только с PRIME в CS2»; • Отбор игроков по часам и стрику дней.

custom 544973514262290680563

9 Aug 2026, 15:15 UTC≈8,730 views107 reactionsread 12 August 2026

Симпл все еще хорош, nt

custom 5449735142622906805107

9 Aug 2026, 13:46 UTC≈22,600 views106 reactionsread 12 August 2026

Сегодня на CYBERSHOKE выйдет интересный апдейт для игры зрителей со стримером

custom 5449735142622906805106

8 Aug 2026, 20:03 UTC≈11,500 views235 reactionsread 12 August 2026
Photo

Основа сегодня в прайме 💪 +10.000$ и вторая победа на CCT

custom 5449735142622906805235

8 Aug 2026, 17:54 UTC≈12,200 views142 reactionsread 12 August 2026
Photo

HEROIC BIG IC BC

custom 5449735142622906805142

8 Aug 2026, 16:14 UTC≈12,200 views109 reactionsread 12 August 2026

Вылетели с медиалиги без единой победы в плей-офф 😭 Я выступаю против медиалиг, где больше двух про-игроков, иначе это превращается в полупрофессиональную лигу. Сейчас регламент давал возможность такое сделать. Турнир создан для креаторов и стримеров в первую очередь. Но безусловно рад, тому что такие турниры в целом проводятся различными БК. Зимой будет лан от Бетбума 🥳

custom 5449735142622906805109

8 Aug 2026, 10:59 UTC≈12,300 views56 reactionsread 12 August 2026
Photo

НОЧЬ В ЭТОМ КЛУБЕ СТОИТ 100.000Р! Ролик, где я проверил самые дорогие и премиальные клубы Москвы уже на канале! https://youtu.be/89Xow5s-MVs

custom 544973514262290680556

7 Aug 2026, 15:14 UTC≈13,500 views108 reactionsread 12 August 2026
Video

САМЫЕ ПРЕМИАЛЬНЫЕ КЛУБЫ В МОСКВЕ! Завтра в 14:00 ✔️

custom 5449735142622906805108

6 Aug 2026, 18:41 UTC≈14,100 views105 reactionsread 12 August 2026
Photo

Мы прошли в верхнюю сетку плей-оффа! 9 августа уже финал Завтра играем против автора названия тг канала 🌟

custom 5449735142622906805105

4 Aug 2026, 13:29 UTC≈17,400 views194 reactionsread 12 August 2026

Если была бы инфа, с каким ножом у меня лучше KD, я уверен, бабочка выигрывает с запасом. У вас нет такого?)

custom 5449735142622906805194

Showing the 12 most recent of 30 posts we hold for @shoke. 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 — 220,447 of 1,151,006entries 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.

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

Named by 7 registered channels — 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Aurora CS2
@AuroraTeam · 212,764
Telegram ranks this channel #2 of 89 here — alongside 88 others — read 11 August 2026
CYBERSHOKE
@cybershoke · 222,065
Telegram ranks this channel #2 of 88 here — alongside 87 others — read 11 August 2026
Дневник Симпла
@s1mplegod123 · 249,900
Telegram ranks this channel #3 of 78 here — alongside 77 others — read 10 August 2026
Ретейк
@retakenews · 262,983
Telegram ranks this channel #3 of 87 here — alongside 86 others — read 10 August 2026
РАЙЗ ЛАВ Ю
@raiz · 314,656
Telegram ranks this channel #12 of 87 here — alongside 86 others — read 10 August 2026
ТРУСЫ РАЙЗА
@raiznews · 521,758
Telegram ranks this channel #12 of 89 here — alongside 88 others — read 9 August 2026
CS2NEWS | Counter-Strike 2
@newcsgo · 579,131
Telegram ranks this channel #12 of 88 here — alongside 87 others — read 8 August 2026
ct0m
@ct0m · 179,371
Telegram ranks this channel #14 of 69 here — alongside 68 others — read 12 August 2026
Counter-Strike 2
@counter_strike2 · 319,539
Telegram ranks this channel #16 of 87 here — alongside 86 others — read 10 August 2026
Team Spirit CS2
@TSpiritCS · 218,575
Telegram ranks this channel #22 of 89 here — alongside 88 others — read 11 August 2026
OverDrive | 20 ЛЕТ В АРКАДЕ
@ihuntnoobs · 207,717
Telegram ranks this channel #33 of 89 here — alongside 88 others — read 11 August 2026
M0NESY LIFE
@m0NESY13 · 255,208
Telegram ranks this channel #34 of 84 here — alongside 83 others — read 10 August 2026
donk
@donk1221 · 282,766
Telegram ranks this channel #39 of 85 here — alongside 84 others — read 10 August 2026
deko_O
@dekocsoff · 199,785
Telegram ranks this channel #42 of 84 here — alongside 83 others — read 11 August 2026
Бустероид 🥋🥊
@busteroid3000 · 451,407
Telegram ranks this channel #59 of 71 here — alongside 70 others — read 10 August 2026
секретный тг шадоукека
@shadowkekw · 612,359
Telegram ranks this channel #64 of 66 here — alongside 65 others — read 8 August 2026

This channel appears in 16 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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.

“ЭРИК СУКА ШОКОВ” (@shoke), 97,201 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/shoke.

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.