Telegram RegisterThe public register of Telegram
Telegram profile photo for PARI Esports CS2

Channel

PARI Esports CS2

@bc_pari_esports_cs

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

44,880subscribers

+11,301 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-1001690713709
TypeChannel
Username@bc_pari_esports_cs
DescriptionШоу, акции, подкасты и многое другое, объединенные нашим любимым CS2. По всем вопросам [email protected] Смотри за Дотой в @bc_pari_esports Выполняй задания в @pari_pass Админ: @pari_esports_cs2_admin
Created18 January 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live7 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/bc_pari_esports_cs

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

32,41045,43138,920.544,8806 August 20267 November 2026
63 measurements spanning 93 days, net +11,301. 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 30,457–47,384 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
7 Nov 2026, 08:2844,880-14
6 Nov 2026, 06:4444,894-50
5 Nov 2026, 08:1044,944-42
4 Nov 2026, 06:2944,986-22
3 Nov 2026, 04:0745,008-31
2 Nov 2026, 06:3645,039-42
1 Nov 2026, 08:2745,081-59
31 Oct 2026, 05:0145,140-133
30 Oct 2026, 02:2945,273-52
29 Oct 2026, 00:1045,325-66
28 Oct 2026, 01:0645,391-36
27 Oct 2026, 00:3545,427-4
26 Oct 2026, 00:0045,431+20
24 Oct 2026, 21:3645,411+247
23 Oct 2026, 19:1645,164+984
22 Oct 2026, 16:3444,180+408
21 Oct 2026, 14:0643,772-51
20 Oct 2026, 13:3943,823-38
19 Oct 2026, 14:3643,861-51
18 Oct 2026, 16:0943,912first reading

Engagement

956 posts held, back to 2 August 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 167 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.84%
avg views ÷ 44,880 subscribers
Avg views / post
1,270
370 posts measured
Reaction rate
4.49%
reactions ÷ views · ER floor
Posts in window
370
of 956 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 7 November 2026
Posts held956 (2 August 2026 – 7 November 2026)
Views total471,233
Reactions total21,157
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 20:00 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
≈1,990
Videos
≈598
Links
≈1,200

Lifetime counters from Telegram’s own channel header, read 7 November 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
54m 21s
Average length
20s

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

52,833 reactions across 946 posts, in 28 distinct kinds. The most used accounts for 14.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤7,86914.9%
custom 53751322521811170364,4868.49%
custom 52940195227584631293,9607.50%
custom 53705713104453771193,2006.06%
custom 51906810204787962063,1746.01%
🔥3,0605.79%
👍2,9285.54%
custom 51953955115903368532,6875.09%
custom 52627940067099411162,6535.02%
custom 53932645604277824832,2034.17%
custom 53121197304195489002,1294.03%
😈2,0883.95%
custom 51881778190494058451,9893.76%
custom 54336419087547369931,8113.43%
custom 54114096204323453091,7743.36%
custom 53255555993022092431,5332.90%
😭1,2052.28%
custom 53145207803467703201,0622.01%
⚡7651.45%
custom 52627110193518689266691.27%
8 further kinds1,5883.01%

Custom emoji. 14 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 955 of the 956 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 53,591 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 956 most recent posts we hold, published 2 August 2026 to 7 November 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

Telegram’s own ‘edited’ marker: 97 of 370 posts held from the last 30 days (26.2%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

7 Nov 2026, 17:34 UTC397 views30 reactionsread 7 November 2026
Video

🌟 Дефолтная ситуация после проигранного Миража 😳 Больше вайбовых и мемных видосов по CS вы сможете найти в нашем TikTok канале 😃 СТАВЬ РЕАКЦИИ — ПОЛУЧАЙ ФРИБЕТЫ

custom 539326456042778248317👍7❤4🤣2

7 Nov 2026, 15:01 UTC680 views54 reactionsread 7 November 2026

💣💣💣💣💣💣💣💣💣 💣💣💣💣💣💣💣💣💣 💣💣💣💣💣💣💣💣💣 💣💣💣💣💣💣💣💣💣 💣💣💣💣💣💣💣💣💣 💣💣💣💣💣💣💣💣💣 💣💣💣💣💣💣💣💣💣 💣💣💣💣💣💣💣💣💣 💣💣💣💣💣💣💣💣💣 👀 ВЕЧЕРНЯЯ БОМБОЧКА 😎 Админу снова ее подкинули, так что вам придется потрудиться и помочь админу отгадать код. Три человека которые угадают код от бомбы получат ФРИБЕТ 500 рублей ➡️ Количество попыток не ограничено 😃 СТАВЬ РЕАКЦИИ — ПОЛУЧАЙ ФРИБЕТЫ

custom 539326456042778248335❤11👍4🔥1🤔1😈1😎1

7 Nov 2026, 12:30 UTC819 views59 reactionsread 7 November 2026
Photo

👏 ПЕРЕД ВАМИ ИТОГИ ПОЛУФИНАЛОВ ПЕКИНА Определились финалисты — ими оказались ⭐️ The MongolZ и ⭐️ MOUZ! Также будет разыграно 3-е место между ⭐️ NAVI и ⭐️ BB Team К какому матчу просыпаемся? ❤️ — финал 🔥️️️️️️ — за 3-е место

custom 539326456042778248330❤17🔥11🤔1

7 Nov 2026, 11:35 UTC782 views39 reactionsread 7 November 2026
Video

⭐️ MOUZ — ВТОРОЙ ФИНАЛИСТ IEM BEIJING 2026! 😳 В невероятной форме находятся Мышки, закрыли эту серию 2-0 по картам! Путь команды Кирилл Михалыча остановился на полуфинале, однако могут еще забрать бронзу. Пытались навязать борьбу, но этого оказалось недостаточно!

custom 539326456042778248330❤4👍3🔥1😈1

7 Nov 2026, 11:24 UTC739 views42 reactionsread 7 November 2026
Video

😆 PR тут же показывает, как стоит принимать выход под Б 🔥️️️️️️ — это жёстко!

custom 539326456042778248325❤8🔥7👍1🤯1

7 Nov 2026, 11:21 UTC688 views35 reactionsread 7 November 2026
Video

👆 S1ren на подхвате! Делает важный трипл-килл, позволяя ⭐️ BB Team выйти на ничейный счёт после первой половины

custom 539326456042778248329❤2👍2🔥1😈1

7 Nov 2026, 11:16 UTC644 views39 reactionsread 7 November 2026
Video

👍 zorte проснулся! Квадро от усатого игрока ⭐️ BB Team!

custom 539326456042778248331❤3🔥3👍1😈1

7 Nov 2026, 10:37 UTC691 views43 reactionsread 7 November 2026
Video

😒 Вот такой клатч отдают BB Team Совсем не идет игра... Ожидаем реабилитацию на второй карте!

custom 539326456042778248330❤8🔥3👍1🤯1

7 Nov 2026, 10:34 UTC653 views38 reactionsread 7 November 2026

Posted without readable text

custom 539326456042778248327❤6🔥3👍1😈1

7 Nov 2026, 08:52 UTC693 views42 reactionsread 7 November 2026

Posted without readable text

custom 539326456042778248332❤5🔥3🤯1custom 54673898075565790051

7 Nov 2026, 08:46 UTC706 views45 reactionsread 7 November 2026
Video

⭐️ NAVI не смогли преодолеть эту стену! ⭐️ The MongolZ проходят в финал, показав характер на второй, вернувшись с счёта 5-7! 🍺 Рожденные Побеждать были в шаге от финала, но, увы.

custom 539326456042778248331🔥6🤣6❤1😈1

7 Nov 2026, 08:15 UTC736 views43 reactionsread 7 November 2026
Video

🔥 WONDERFUL РАСКРУЧИВАЕТСЯ ЗА ТРОЙКОЙ 🙂 По мотивам Stewie2K?

custom 539326456042778248333👍5❤3👎1🔥1

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

Posts edited after publishing

@bc_pari_esports_cs edited 4 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
20 August 2026
Most recent edit
10 October 2026

Forward network

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 9 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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

СТАВОЧНАЯ АУНКЕРА 🤑
@aunkereEZ · 88,895
#1
Dota 2
@Dota2 · 338,119
#2
PARI Esports Dota 2
@bc_pari_esports · 82,735
#3
CS2NEWS | Counter-Strike 2
@newcsgo · 579,489
#4
m0NESY NEWS
@m0NESYGG · 122,689
#5
harumi
@haruminews · 31,355
#6
ТРУСЫ РАЙЗА
@raiznews · 505,813
#7
НАШ КС | CIS NEWS
@cscis · 41,142
#8
РАЙЗ ЛАВ Ю
@raiz · 301,232
#9
SL4M & Counter-Strike
@sl4mtv · 82,301
#10
zoner and CO
@mechanogun · 57,905
#11
Бустер 🍄
@bigpencil · 1,226,285
#12
Team Spirit CS2
@TSpiritCS · 225,646
#13
hooch CS2
@hoochcs2 · 23,008
#14
Логово Внизу
@nebudetgg · 487,980
#15
BETBOOM Esports CS2
@betboom_esports_cs · 122,733
#16
seized 🍉
@seizedofficial · 8,042
#17
Paragon Events CS2
@prgnevents_cs2 · 17,112
#18
SlapNews • Новости CS2
@Slap_News · 8,655
#19
DEGSTER
@degsterof · 47,484
#20
CYBERSLOVO
@cyberslovo · 41,097
#21
deko_O
@dekocsoff · 225,652
#22
Тетрадка с Фишками CS2
@FISHKACS2 · 27,672
#23
AUNKERE
@aunkeretg · 166,446
#24
Cloud9 Counter-Strike 2
@Cloud9_CS_Official · 4,949
#25
HeavyGoD
@heavygodcs · 5,189
#26
зортик :)
@zortelad · 4,793
#27
r3salt x payk
@r3saltg · 7,808
#28
FL4MUS
@fl4mus92 · 12,256
#29
Маликек🦒
@ogmalikek · 5,145
#30
STREAM INSIDE
@streaminside · 267,921
#31
Кальянная у n0rb3r7’а
@n0rb3r7tg · 9,330
#32
Team Spirit
@Team_Spirit_Official · 235,857
#33
donk
@donk1221 · 289,942
#34
alpha
@alphaddv · 7,972
#35
WINLINE Esports
@winlinesports · 122,844
#36
BETBOOM TEAM
@betboomteam · 74,061
#37
ЭРИК СУКА ШОКОВ
@shoke · 94,108
#38
Телега Маелшторма
@maelstormone · 33,789
#39
Ликс
@dmlixxx · 354,723
#40
KENSi & LIFE
@kensilife · 8,185
#41
Мысли F_1N’а
@f_1ncsgo · 7,716
#42
Бустероид 🥋🥊
@busteroid3000 · 454,312
#43
FISSURE Dota 2
@fissure_pro_dota2 · 32,093
#44
BETBOOM Esports Dota 2
@betboom_esports · 165,251
#45
LUNACY TEAM 🌙 CS2
@lunacygg · 60,430
#46
Boombl4
@Boombl4K · 34,143
#47
Counter-Strike 2
@counter_strike2 · 358,179
#48
sh1ro
@sh1rocs2 · 71,611
#49
Улей Пчёлкина 🐝
@alexeeeeey · 31,189
#50
BELCHONOKK 🖤
@BELCHONOKKtg · 5,126
#51
CYBERSHOKE
@cybershoke · 232,221
#52
liTTle & CO.
@littlecsgo · 5,414
#53
Lack1Don
@lack1 · 3,761
#54
flamie friends & family
@flamieTG · 8,648
#55
Sergey "Ax1Le" Rykhtorov
@ax1lecs2 · 6,979
#56
Сын Миража
@sports_cs2 · 10,688
#57
Virtus.pro
@virtuspro · 24,533
#58
d1Ledez контент из петушков
@d1Ledezlife · 5,224
#59
clax
@justaclaxie · 1,134
#60
Zloba
@zloba113 · 4,137
#61
papa pixel
@papapixel · 1,046
#62
AMKAL ESPORTS
@amkalesports · 15,515
#63
ГЛОШИНГ
@glowiingcs · 1,089
#64
bullet CS2
@bullet_cs2 · 1,141
#65
Patsi l Путь пацанчика
@patsiuuu · 1,640
#66
КИБЕР | Counter-Strike 2
@sports_kiber · 60,942
#67
interz squad
@interzsquad · 3,917
#68
Закулисье CS2
@cs2valve2 · 86,996
#69
🥺🤔😏😁
@norwi1 · 1,506
#70
Jay_TB пишшшет -__-
@jay_tbpub · 2,337
#71
Okko Кибер | CS2
@okkocyber · 25,947
#72
Team Space
@teamspace_cs · 1,836
#73
Отец казахского контр-страйка
@adrencs · 9,448
#74
OverDrive | 20 ЛЕТ В АРКАДЕ
@ihuntnoobs · 200,336
#75
Подвал CS | Все о ТИР-2 сцене
@tier2cs · 31,062
#76
Aurora CS2
@AuroraTeam · 199,952
#77
M0NESY LIFE
@m0NESY13 · 252,378
#78
Дневник Симпла
@s1mplegod123 · 242,483
#79
EVELONE 1️⃣9️⃣2️⃣
@evelone192gg · 1,090,103
#80
Ретейк
@retakenews · 249,975
#81
PARIVISION
@parivision · 39,101
#82
Со SNEWSычем | Ньюсыч
@snewscsgo · 60,773
#83
HLTV | Counter-Strike News
@hltvtelegram · 26,877
#84
Dr.Jerry
@Jerry2strong · 38,335
#85
Nafnya
@nafnya · 6,544
#86
9Pandas CS2
@ninepandascs · 12,150
#87
dyrachyo
@dyrachyo · 202,390
#88
SELLTER
@selltertg · 3,197
#89
kyotostxr
@kyotostxr · 1,941
#90
Gabe Follower
@gabefollower · 51,633
#91
FONBET Esports
@fonbetesports · 69,854
#92
CYBERSHOKE Esports | CS2
@team_cybershoke · 17,540
#93
Counter-Strike по полочкам
@innersh1necs · 2,511
#94
Nix
@nixtalk · 256,453
#95
harumijez
@harumijezz · 2,749
#96

Read from Telegram’s recommendation API, most recently 5 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

Безумный Дейв | Раздачи игр
@av_games · 20,147
Telegram ranks this channel #44 of 44 here — alongside 43 others — read 27 September 2026
PARI Esports Dota 2
@bc_pari_esports · 82,735
Telegram ranks this channel #61 of 92 here — alongside 91 others — read 18 August 2026
Okko Кибер | CS2
@okkocyber · 25,947
Telegram ranks this channel #77 of 98 here — alongside 97 others — read 12 September 2026

This channel appears in 3 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 7 November 2026 — this entry's latest reading, not the date you are reading this.

“PARI Esports CS2” (@bc_pari_esports_cs), 44,880 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/bc_pari_esports_cs.

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.