Telegram RegisterThe public register of Telegram

Channel

Призраки | ЦСКА Москва

@ghst_cska

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

284subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002258470036
TypeChannel
Username@ghst_cska
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 live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/ghst_cska

Growth

2849 Aug 2026, 14:16 — 284 subscribers9 Aug 2026, 14:21 — 284 subscribers9 Aug 2026, 14:169 Aug 2026, 14:21
2 measurements taken within a single day. 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 283–285 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 14:21284no change
9 Aug 2026, 14:16284first reading

Engagement

16 posts held, back to 31 March 2026the 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.

ERR · 30 days
122.9%
avg views ÷ 284 subscribers
Avg views / post
349
2 posts measured
Reaction rate
13.8%
reactions ÷ views · ER floor
Posts in window
2
of 16 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 2 August 2026
Posts held16 (31 March 20262 August 2026)
Views total698
Reactions total96
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 14:16 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

Video runtime
2m 23s
Average length
1m 12s

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

711 reactions across 16 posts, in 4 distinct kinds. The most used accounts for 40.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 528071827103577103228740.4%
custom 519296119714140507922331.4%
16523.2%
👍365.06%

Custom emoji. 2 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 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 16 of the 16 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 711reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

2 Aug 2026, 05:15 UTC201 views31 reactionsread 9 August 2026
Video

Video, posted without a caption

👍1310custom 52807182710357710328

17 Jul 2026, 17:35 UTC497 views65 reactionsread 9 August 2026
Photo

Рисуй за ЦСКА!

custom 519296119714140507929custom 52807182710357710322213👍1

11 Jul 2026, 10:26 UTC674 views68 reactionsread 9 August 2026
Photo

📍Рязанская область

27custom 519296119714140507921custom 528071827103577103220

10 Jul 2026, 18:23 UTC427 views13 reactionsread 9 August 2026

С датой, братва🔥🔥

custom 519296119714140507913

10 Jul 2026, 18:23 UTC387 views52 reactionsread 9 August 2026
Forwarded from @NEMESTNYE33FanPhoto

💫 💫💫💫💫⭐️ Погнали дальше хулиганы! Всех причастных поздравляем! 🥹💜

custom 51929611971414050792812custom 528071827103577103212

8 Jun 2026, 11:22 UTC818 views38 reactionsread 9 August 2026
Photo

📍Турция, Стамбул

custom 528071827103577103225👍13

18 May 2026, 19:56 UTC968 views69 reactionsread 9 August 2026
Photo

Призраки × Happy Band

custom 52807182710357710322724custom 519296119714140507918

17 May 2026, 11:01 UTC750 views63 reactionsread 9 August 2026
Photo

XX.05.2026. White Whiskey (кс)+ KD ( Коломна) vs Некие (кб), 16х16, 3 минуты, победа кс!

custom 51929611971414050793821custom 52807182710357710324

3 May 2026, 22:13 UTC890 views48 reactionsread 9 August 2026
Photo

Увидимся на дерби! ____ × Horse Company × SouthSide

custom 528071827103577103227custom 519296119714140507921

26 Apr 2026, 14:21 UTC662 views29 reactionsread 9 August 2026
Forwarded from @cskavandalsVideo

🔴СБОР СРЕДСТВ НА ПЕРФОМАНС🔵 Армейцы! Спустя долгие 6 лет нас ожидает столичное дерби с мясом при полных трибунах! Пандемия и введение FAN-ID лишили нас таких матчей на постоянной основе, но волею судьбы нам предстоит встретиться в кубке. Наш сектор в логове заклятых должен выглядеть максимально красочно и выделяться на фоне всего стадиона! Помимо перфомансов у нас есть куча расходников, которые тоже требуют вложе

custom 528071827103577103214custom 519296119714140507987

17 Apr 2026, 20:35 UTC726 views22 reactionsread 9 August 2026
Forwarded from @Active_JHCCSKAPhoto

Завтра вновь дерби! Без права на ошибку! Все на хоккей! «Красная Армия» - «спартак» 18 апреля, 14:00. Автозаводская ул, 23А. 🗣️Бронь билетов на домашний активный сектор 10, как обычно, через @Gorbachev_CSKA. Телеграм время от времени может не работать по понятным причинам, поэтому рекомендуем обращаться по телефону +7 (961) 009 21-08 или в ВКонтакте https://vk.com/id157422801. Цена: 0 руб 00 коп. Писать в рабочее в

10custom 52807182710357710327custom 51929611971414050795

8 Apr 2026, 16:32 UTC745 views24 reactionsread 9 August 2026
Photo

Кэп, с днём рождения!

22custom 52807182710357710322

Showing the 12 most recent of 16 posts we hold for @ghst_cska. 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 — 808,333 of 1,340,412entries 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

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

“Призраки | ЦСКА Москва” (@ghst_cska), 284 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/ghst_cska.

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.