Telegram RegisterThe public register of Telegram
Telegram profile photo for ФК «Ростов» || Столица Юга

Channel

ФК «Ростов» || Столица Юга

@stolitsa_yuga

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry

1,214subscribers

-1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001520262253
TypeChannel
Username@stolitsa_yuga
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/stolitsa_yuga

Topic

Sports — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 why it has no browse page of its own yet.

Growth

1,2091,2151,2126 August 2026 — 1,215 subscribers7 August 2026 — 1,215 subscribers12 August 2026 — 1,214 subscribers19 August 2026 — 1,213 subscribers23 August 2026 — 1,209 subscribers26 August 2026 — 1,211 subscribers5 September 2026 — 1,214 subscribers14 September 2026 — 1,212 subscribers18 September 2026 — 1,214 subscribers1,2146 August 202618 September 2026
9 measurements spanning 43 days, net -1. 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 1,208–1,216 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 07:191,214+2
14 Sept 2026, 04:151,212-2
5 Sept 2026, 06:381,214+3
26 Aug 2026, 14:031,211+2
23 Aug 2026, 12:051,209-4
19 Aug 2026, 14:251,213-1
12 Aug 2026, 16:341,214-1
7 Aug 2026, 09:431,215no change
6 Aug 2026, 17:181,215first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

254 reactions across 19 posts, in 13 distinct kinds. The most used accounts for 45.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
11545.3%
😢4618.1%
👍228.66%
💊176.69%
😱155.91%
💯83.15%
🤡72.76%
🤬62.36%
👏51.97%
💩51.97%
🤣41.57%
🥴31.18%
😭10.394%

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

Measured over the 20 most recent posts we hold, published 1 August 2026 to 6 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

6 Aug 2026, 12:58 UTC250 views1 reactionsread 6 August 2026
Photo

А вот и Василий" Проверим" Казарцев получил назначение на наш матч. Посмотрим-посмотрим.

1

6 Aug 2026, 10:28 UTC228 views3 reactionsread 6 August 2026
Forwarded from @nuieptPhoto

❗️НА СТАДИОНЕ «РОСТОВ АРЕНА» ИЗ-ЗА УРАГАНА ПОСТРАДАЛ МЕДИАФАСАД, РАБОТЫ ПЛАНИРУЮТ ЗАВЕРШИТЬ В ТЕЧЕНИЕ НЕДЕЛИ «Поле в прекрасном состоянии, там никаких опасений нет. В результате урагана пострадал медиафасад, который обрамляет весь стадион. С момента строительства прошло уже 8–9 лет. Ураган был очень серьезным, последствия все видели на примере города. И сейчас на стадионе повыпадало около 20 кассет», – рассказал мин

👍3

4 Aug 2026, 15:22 UTC474 views26 reactionsread 6 August 2026
Photo

Начинаем путь в Кубке с уверенной победы. Ничего особенного сегодня делать не пришлось. Просто грамотно наказали Акрон за гигантское количество ошибок в обороне. Отличный дебют в основе нашего вратаря Петрова, несколько мячей отбил, Мадрахимов отдал голевую. Начало положено для этих парней. Ну и конечно хорош Олусегун. 1+1 на его счету. Едем дальше. Впереди очередной выезд в Москву к ЦСКА

21👍5

4 Aug 2026, 15:01 UTC445 views10 reactionsread 6 August 2026

Последние замены. Титов и Аджаса в игре

10

4 Aug 2026, 14:58 UTC450 views4 reactionsread 6 August 2026

Удар со штрафного Бистровича и Петров вытаскивает мяч из верхнего угла

4

4 Aug 2026, 14:54 UTC451 views1 reactionsread 6 August 2026

Жалко офсайд, а разыграли очень красиво

👍1

4 Aug 2026, 14:49 UTC457 views4 reactionsread 6 August 2026

Снова Аревало бьет и снова уверенно Петров забирает мяч себе

👍4

4 Aug 2026, 14:44 UTC459 views5 reactionsread 6 August 2026

Все залетает. 3 гола абсолютно одинаковых. Прохин забивает. 4-0

👏5

4 Aug 2026, 14:28 UTC466 views5 reactionsread 6 August 2026

Опять поймали Акрон на ошибке и 3-0. Имран Азнауров. Голевая на счету Олусегуна

5

4 Aug 2026, 14:23 UTC464 viewsread 6 August 2026

Замены у нас. Сако и Бабакин вышли вместо Ногейры и Мелехина. Странные замены и очень рискованные

4 Aug 2026, 14:16 UTC470 views9 reactionsread 6 August 2026

Перерыв. Выигрываем 2-0. Вот что отличает матчи Кубка так это большое количество брака. Этим грешат и мы, и Акрон. Но мы дважды забили и ведем. Акрон больше атакует, но кроме опасности на 1 минуте ничего особо не создал. Наши подходы даже поопаснее будут, а наказать тольяттинцев за ошибки мешает нехватка хладнокровия. Ждем второй тайм и игроков основы

9

4 Aug 2026, 13:32 UTC473 views11 reactionsread 6 August 2026

Удар Аревало и вступает в игру Петров отбивая мяч

11

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

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

ФК «Ростов» | Футбольный клуб «Ростов»
@fcrostov_official · 45,594
Telegram ranks this channel #46 of 98 here — alongside 97 others — read 27 August 2026

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

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Жбанов, Илья Дмитриевич (ru.wikipedia.org)
“…web|url=https://t.me/stolitsa_yuga/4603|title=Илья Жбанов. Знакомство.|website=Telegram|archive-url=https://web.archive.org/web/20241111100122/https://t.me/…”
read 13 September 2026

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

“ФК «Ростов» || Столица Юга” (@stolitsa_yuga), 1,214 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/stolitsa_yuga.

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.