Telegram RegisterThe public register of Telegram
Telegram profile photo for Клуб Болельщиков ФК «Ростов»

Channel

Клуб Болельщиков ФК «Ростов»

@FanClub_FC_Rostov

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

9,179subscribers

+81 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001813899119
TypeChannel
Username@FanClub_FC_Rostov
Created13 July 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/FanClub_FC_Rostov

Growth

9,0989,1799,138.56 August 2026 — 9,098 subscribers6 August 2026 — 9,098 subscribers6 August 2026 — 9,099 subscribers9 August 2026 — 9,125 subscribers12 August 2026 — 9,142 subscribers15 August 2026 — 9,179 subscribers6 August 202615 August 2026
6 measurements spanning 9 days, net +81. 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 9,086–9,191 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 14:299,179+37
12 Aug 2026, 11:339,142+17
9 Aug 2026, 14:129,125+26
6 Aug 2026, 14:259,099+1
6 Aug 2026, 10:179,098no change
6 Aug 2026, 10:019,098first reading

Engagement

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

ERR · 30 days
19.5%
avg views ÷ 9,179 subscribers
Avg views / post
1,790
30 posts measured
Reaction rate
1.78%
reactions ÷ views · ER floor
Posts in window
30
of 32 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 15 August 2026
Posts held32 (16 July 202615 August 2026)
Views total53,777
Reactions total955
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 09:54 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 48s
Average length
34s

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

1,126 reactions across 32 posts, in 16 distinct kinds. The most used accounts for 42.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
47342.0%
🔥35431.4%
👍807.10%
🙏645.68%
🤣353.11%
👏282.49%
🕊232.04%
😁211.87%
❤‍🔥201.78%
😱100.888%
50.444%
💯50.444%
💋30.266%
🍌20.178%
🎉20.178%
💘10.089%

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

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

15 Aug 2026, 06:12 UTC285 views16 reactionsread 15 August 2026
Forwarded from @fcrostov_officialPhoto

Дождались! Сегодня сыграем ДОМА против «Рубина» 🔷🔴 Старт матча в 18:30 по мск, трансляцию покажет телеканал «Матч Премьер». Напоминаем про счастливый час 😉 До встречи! @fcrostov_official

🔥14👏2

14 Aug 2026, 16:18 UTC438 views13 reactionsread 15 August 2026
Forwarded from @fcrostov_officialPhoto

Информация для болельщиков Матч 4-го тура Альфа-Банк Российской Премьер-Лиги сезона 2026/27 между «Ростовом» и «Рубином» состоится завтра, 15 августа. Начало игры в 18:30. Вход на территорию «Ростов Арены» будет открыт с 16:30. Вход на стадион возможен только при наличии специального QR-кода, сформированного в личном кабинете портала Госуслуг, на основании карты болельщика и приобретённого билета/абонемента. Вход

10👍1💋1💘1

13 Aug 2026, 15:50 UTC933 views67 reactionsread 15 August 2026
Forwarded from @premierligaVideo

Игор Ногейра прервал выход один на один самым эффектным и неожиданным способом 😅😎

🤣34🔥1910👍4

13 Aug 2026, 15:42 UTC≈1,040 views33 reactionsread 15 August 2026
Photo

Всем, кто справился 👍 #РостовРубин 15 августа в 18:30, до встречи на «Ростов Арене» 🏟️ БИЛЕТЫ 🎫

22👍9🔥2

13 Aug 2026, 15:40 UTC974 views13 reactionsread 15 August 2026
Poll

Лучший бомбардир из нынешнего состава «Ростова» против «Рубина»?

  1. Алексей Миронов13%
  2. Егор Голенков58%
  3. Тимур Сулейманов8%
  4. Роналдо22%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

8🔥3👍2

13 Aug 2026, 15:38 UTC950 views10 reactionsread 15 August 2026
Poll

Кто является лучшим бомбардиром противостояния между «Ростовом» и «Рубином»?

  1. Николай Комличенко39%
  2. Тимофей Калачев23%
  3. Михаил Осинов18%
  4. Егор Голенков20%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

🔥73

13 Aug 2026, 15:37 UTC955 views9 reactionsread 15 August 2026
Poll

Сколько раз за последние 10 личных встреч был счет 0:0?

  1. 016%
  2. 125%
  3. 243%
  4. 316%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

🔥8👍1

13 Aug 2026, 15:36 UTC944 views10 reactionsread 15 August 2026
Poll

Дома мы играли с «Рубином» 23 раза, сколько побед на нашем счету?

  1. 719%
  2. 1033%
  3. 1233%
  4. 1416%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

10

13 Aug 2026, 15:35 UTC928 views14 reactionsread 15 August 2026

Матч против «Рубина» уже в эту субботу, давайте проверим, как хорошо вы к нему готовы? 🤔🫣 Проходи опрос ниже и узнавай что-то новое 🧐

8🔥6

11 Aug 2026, 19:12 UTC770 views38 reactionsread 15 August 2026
Forwarded from @fcrostov_officialPhoto

Болельщики из активного сектора сегодня пришли с подарками на тренировку, чтобы поприветствовать новичков команды и поздравить Комара с круглой цифрой🎁 Как это мило – ради таких моментов мы и играем🫂 @fcrostov_official

🔥259🍌2👍1🤣1

11 Aug 2026, 09:36 UTC≈1,270 views25 reactionsread 15 August 2026
Photo

Новый сезон - новые эмоции! Уже 15 августа состоится первый домашний матч, мы должны показать яркую поддержу и гнать команду к победе 💛 Приходи на активный сектор и стань настоящим 12 игроком 🥁 Для этого пиши в личные сообщения - @adm_FanClub! ✍️

19🔥6

10 Aug 2026, 10:54 UTC≈1,550 views20 reactionsread 15 August 2026
Photo

«Клуб Болельщиков» организовывает выезд на матч 5-го тура РПЛ с «Ахматом» в Грозном. Матч состоится 22.08.2026, в 18:00, место матча - «Ахмат Арена». Выезд из Ростова - 21-го августа от Мегамага в 21-00. Стоимость поездки (зависит от количества людей): Автобус (50 мест) - 5000 взрослый, 4000 дети до 14 лет. Маршрутка (20 мест) - 6000 взрослый, 5500 дети до 14 лет. Для участия в выезде заполните форму ✍️🧾 https://

12🔥8

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

Polls

The 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

13 Aug 2026, 15:40 UTCAnonymous Quiz356 voters

Лучший бомбардир из нынешнего состава «Ростова» против «Рубина»?

  1. Алексей Миронов13%
  2. Егор Голенков58%
  3. Тимур Сулейманов8%
  4. Роналдо22%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

13 Aug 2026, 15:38 UTCAnonymous Quiz362 voters

Кто является лучшим бомбардиром противостояния между «Ростовом» и «Рубином»?

  1. Николай Комличенко39%
  2. Тимофей Калачев23%
  3. Михаил Осинов18%
  4. Егор Голенков20%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

13 Aug 2026, 15:37 UTCAnonymous Quiz337 voters

Сколько раз за последние 10 личных встреч был счет 0:0?

  1. 016%
  2. 125%
  3. 243%
  4. 316%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

13 Aug 2026, 15:36 UTCAnonymous Quiz353 voters

Дома мы играли с «Рубином» 23 раза, сколько побед на нашем счету?

  1. 719%
  2. 1033%
  3. 1233%
  4. 1416%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 32 most recent posts we hold, published 16 July 2026 to 15 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 72,440 of 1,480,975entries 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

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

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.

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.

РОСТОВ ГЛАВНЫЙ - РОСТОВ НОВОСТИ - 161
@rostov_glavniy · 274,620
Telegram ranks this channel #34 of 84 here — alongside 83 others — read 12 August 2026
Это Ростов новости
@etorostov · 381,931
Telegram ranks this channel #46 of 71 here — alongside 70 others — read 12 August 2026
Privet-Rostov.ru - новости Ростов-на-Дону
@privet_rostov_ru · 178,696
Telegram ranks this channel #63 of 85 here — alongside 84 others — read 12 August 2026
Новости Ростова | 161.RU
@news161ru · 214,421
Telegram ranks this channel #84 of 89 here — alongside 88 others — read 12 August 2026

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

“Клуб Болельщиков ФК «Ростов»” (@FanClub_FC_Rostov), 9,179 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/FanClub_FC_Rostov.

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.