Telegram RegisterThe public register of Telegram
Telegram profile photo for Красно-Синяя Таблетка | ЦСКА

Channel

Красно-Синяя Таблетка | ЦСКА

@cska_tabl

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

92subscribers

+57 since we began measuring on 14 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003702294991
TypeChannel
Username@cska_tabl
CreatedBetween 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live2 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/cska_tabl

Previous handles

@cska_tabl was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@kis_pas
held 14 August 202614 August 2026

Growth

32926214 August 2026 — 35 subscribers15 August 2026 — 34 subscribers17 August 2026 — 33 subscribers17 August 2026 — 33 subscribers18 August 2026 — 32 subscribers2 September 2026 — 92 subscribers14 August 20262 September 2026
6 measurements spanning 18 days, net +57. 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 23–101 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 02:4492+60
18 Aug 2026, 09:2232-1
17 Aug 2026, 18:0033no change
17 Aug 2026, 17:4533-1
15 Aug 2026, 15:5234-1
14 Aug 2026, 15:0135first reading

Engagement

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

ERR · 30 days
860.0%
avg views ÷ 92 subscribers
Avg views / post
791
12 posts measured
Reaction rate
0.341%
reactions ÷ views · ER floor
Posts in window
12
of 31 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. It is computed over the 7 of 12 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 August 2026
Posts held31 (24 July 202616 August 2026)
Views total9,494
Reactions total32
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Aug 2026, 18: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.

Reaction mix

58 reactions across 11 posts, in 11 distinct kinds. The most used accounts for 31.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1831.0%
1017.2%
👍813.8%
🥰813.8%
💋610.3%
💯35.17%
👌11.72%
👏11.72%
🤩11.72%
🤯11.72%
🥴11.72%

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 11 of the 31 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 58 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 31 most recent posts we hold, published 24 July 2026 to 16 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

16 Aug 2026, 21:10 UTC12 viewsread 17 August 2026

А вот и подтверждение https://t.me/karpinside/39765

16 Aug 2026, 20:32 UTC14 views1 reactionsread 17 August 2026

Очередной вброс от мясного быдло. Видимо они даже не в курсе, что он вингер, а не ФРВ, а вингеров мы не ищем. https://t.me/UniversalBakha/10030

👏1

16 Aug 2026, 15:09 UTC17 views2 reactionsread 17 August 2026

А никого не смущает, что чел сидел свободным агентом с начала ТО и только Рубин, потерявший Даку, решил его подписать? https://t.me/transferi_rpl/8815

👌1🥴1

16 Aug 2026, 13:39 UTC17 views3 reactionsread 17 August 2026

Это пздц.. только начал набирать форму и тут такое. Как же нам повезло, что даже с таким «спортблоком» у нас есть ещё хотя бы Рейс.

2💯1

16 Aug 2026, 13:36 UTC7 views1 reactionsread 17 August 2026
Forwarded from @punkinside

Мойзес порвал кресты По моей информации, защитнику ЦСКА диагностирован разрыв крестообразной связки после сегодняшнего МРТ Специально для @championat @punkinside

🤯1

16 Aug 2026, 12:42 UTC21 viewsread 17 August 2026
Photo

Дух ЧМ испарился. Русский балет вернулся..

15 Aug 2026, 15:47 UTC16 viewsread 17 August 2026
Forwarded from @CSKAbyMike

ЦСКА пропустил лишь 2 гола после 4 туров – самый сухой старт с сезона-2018/19 Тогда армейцы также пропустили лишь 2 гола. А меньше после 4 туров в последний раз ЦСКА пропускал в сезоне-2016/17 (1) — Opta Sports @CSKAbyMike

15 Aug 2026, 15:28 UTC24 views2 reactionsread 17 August 2026
Photo

Выиграли благодаря случайному пенальти в ничейном матче. Больше даже комментировать ничего не хочется, как то грустно всё в плане игры. Если искать позитив, то хочется верить, что Игдисамов просто начал строить команду от обороны, что в принципе логично. Ведь в защите мы реально стали надежнее и мало пропускаем, но и с сильными соперниками пока не играли. Возможно на зимних сборах будет уже более плодотворная рабо

💯2

15 Aug 2026, 14:20 UTC26 views2 reactionsread 17 August 2026

Мы хотим установить рекорд по количеству не засчитанных пропущенным мячей? Ладно, если серьезно, то снова тяжело входили в игру, Кисляк опять при обороне садился пятым защитников в стиле Карпинбола, а при атаке часто поднимался выше к Алвесу, оставляя в глубине одного Облякова. По Алвесу пока не понятно, есть хорошие действия, но как то вспышками, не хватает стабильности. Смотрим второй тайм.

👍2

15 Aug 2026, 13:13 UTC27 viewsread 17 August 2026
Photo

Возвращение легендарного треугольника в центре, отлично начавшего сезон Поповича и Мойзеса. Состав внушает оптимизм, посмотрим на игру.

13 Aug 2026, 14:33 UTC≈9,290 views21 reactionsread 17 August 2026
Photo

Решил пересмотреть нарезки голов с Лусиано Гонду и убедился в одном наблюдении. Почти во всех случаях когда Аргентинец регулярно забивал голы, он играл в два нападающих. Прям отчетливо видно, что ему удобнее находить пространство в полуфлангах. Это было и в Аргентине и в Зените, когда он провел лучший сезон в карьере играя в паре с Кассьерой. Исходя из этого, я своим дилетантским взглядом, считаю, что нам надо по

🔥10👍65

Showing the 12 most recent of 31 posts we hold for @cska_tabl. 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 2 September 2026 — this entry's latest reading, not the date you are reading this.

“Красно-Синяя Таблетка | ЦСКА” (@cska_tabl), 92 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/cska_tabl.

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.