12 Aug 2026, 06:32 UTC2 viewsread 12 August 2026
Forwarded from @zhfootballllPhoto
🇷🇺 x 🇦🇷 РОССИЯ VS АРГЕНТИНА! Стороны ведут переговоры о проведении товарищеского матча уже этой осенью, сообщает Odds ❓ Точная дата на данный момент неизвестна
Channel
Ростов
@Sakotops
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
9subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002494600402 |
|---|---|
| Type | Channel |
| Username | @Sakotops |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Sakotops |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 12:47 | 9 | no change |
| 7 Aug 2026, 16:15 | 9 | first reading |
Engagement
16 posts held, back to 1 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 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 16 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 546
- Videos
- 271
- Links
- 112
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 2m 48s
- Average length
- 17s
Measured directly from 10 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.
Recent posts
11 Aug 2026, 19:17 UTC1 viewsread 12 August 2026
Forwarded from @fcrostov_officialPhoto
Болельщики из активного сектора сегодня пришли с подарками на тренировку, чтобы поприветствовать новичков команды и поздравить Комара с круглой цифрой🎁 Как это мило – ради таких моментов мы и играем🫂 @fcrostov_official
7 Aug 2026, 08:13 UTC3 viewsread 12 August 2026
Forwarded from @transferyiPhoto
Официально: Антон Заболотный стал игроком «СКА Ростов-на-Дону» (Медиалига). Свободный агент.
6 Aug 2026, 19:10 UTC4 viewsread 12 August 2026
Forwarded from @transferyiPhoto
Официально: Винисиус Жуниор продлил контракт с «Реалом» до лета 2032 года.
4 Aug 2026, 15:18 UTC2 viewsread 12 August 2026
Forwarded from @fcrostov_officialPhoto
ПОБЕЖДАЕМ В ПЕРВОМ МАТЧЕ FONBET КУБКА РОССИИ🔥
4 Aug 2026, 14:51 UTC2 viewsread 12 August 2026
Forwarded from @fcrostov_officialVideo
Капитан отличился голом! #АкронРостов | 0️⃣*️⃣4️⃣
4 Aug 2026, 14:43 UTC1 viewsread 12 August 2026
Forwarded from @fcrostov_officialVideo
💛💛💛
4 Aug 2026, 14:31 UTC1 viewsread 12 August 2026
Forwarded from @matchpremierVideo
«Акрон» ошибся – «Ростов» наказал. Без каких-либо проблем. ⚽️ Наш футбол в MAX
4 Aug 2026, 14:31 UTC1 viewsread 12 August 2026
Forwarded from @matchpremierVideo
«Ростов» уже забил, «Акрон» уже пропустил. Путь РПЛ начался. ⚽️ Наш футбол в MAX
4 Aug 2026, 14:31 UTC1 viewsread 12 August 2026
Forwarded from @matchpremierVideo
«Ростов» забивает только издалека. По-другому нельзя сегодня. ⚽️ Наш футбол в MAX
4 Aug 2026, 14:30 UTC1 viewsread 12 August 2026
Forwarded from @fcrostov_officialVideo
Мадрахимов – первая голевая, Олусегун – первый гол😍 КЛААААСС! #АкронРостов | 0️⃣*️⃣1️⃣
4 Aug 2026, 14:30 UTC1 viewsread 12 August 2026
Forwarded from @fcrostov_officialVideo
Дебютный гол для Ярослава Михайлова за нашу команду! 😍 Нам нравится такое начало!!! #АкронРостов | 0️⃣*️⃣2️⃣
Showing the 12 most recent of 16 posts we hold for @Sakotops. 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
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Ростов” (@Sakotops), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Sakotops.
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.