Готовимся к концерту правильно 💪
custom 518833348154911363443custom 542951126690747102417custom 540465273063762345213

Channel
@srs61
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,302subscribers
+16 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002045979088 |
|---|---|
| Type | Channel |
| Username | @srs61 |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/srs61 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 21:21 | 2,302 | +17 |
| 7 Aug 2026, 15:37 | 2,285 | -1 |
| 6 Aug 2026, 22:02 | 2,286 | first reading |
13 posts held, back to 25 February 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 2 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 13 (25 February 2026 – 6 August 2026) |
| Views total | 1,053 |
| Reactions total | 220 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:43 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.
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.
1,487 reactions across 13 posts, in 9 distinct kinds. The most used accounts for 24.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5188333481549113634 | 365 | 24.5% | |
| custom 5429511266907471024 | 267 | 18.0% | |
| custom 5402145311550350810 | 213 | 14.3% | |
| custom 5372852535080000782 | 167 | 11.2% | |
| custom 5404425823220408230 | 126 | 8.47% | |
| custom 5404652730637623452 | 115 | 7.73% | |
| custom 5438121907536804305 | 109 | 7.33% | |
| custom 5239944694795886533 | 88 | 5.92% | |
| custom 5438543411332267161 | 37 | 2.49% |
Custom emoji. Every row above is a 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 13 of the 13 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,487reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 25 February 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.
Готовимся к концерту правильно 💪
custom 518833348154911363443custom 542951126690747102417custom 540465273063762345213
Пришли на треню по таю с Ростовскими пацанами
custom 542951126690747102470custom 540442582322040823037custom 540214531155035081031custom 51883334815491136349
📸 Плёночные вайбы нашего отдыха Фото @ImWombat
custom 542951126690747102452custom 518833348154911363430custom 540442582322040823020
🏕️ Не изменяя традициям, мы третий год подряд отправляемся летом в кемпинг Голубое озеро, шелест листвы и пламенный свет - вот что необходимо для перезагрузки души и тела Каждый год мы собираемся все вместе у костра, чтобы рассказать новые истории, от души посмеяться и ещё сильнее сблизиться
custom 518833348154911363434custom 540442582322040823021custom 540214531155035081017custom 54295112669074710243
CMH 22.05 Съёмка/монтаж: Фуфел
custom 540214531155035081057custom 540442582322040823036custom 542951126690747102432custom 51883334815491136345custom 54046527306376234521
Вчера отгремел концерт CMH в Ростове, а сегодня мы уже на всех парах мчимся дружить в Краснодар ☀️
custom 540214531155035081061custom 540465273063762345246custom 542951126690747102431custom 518833348154911363411
💬 Дали интервью местному новостному порталу, немного раскрыли лор СРС статью можно прочитать здесь
custom 518833348154911363476custom 540465273063762345255custom 540214531155035081046custom 540442582322040823012custom 54295112669074710244
Друзья, нам понадобилось некоторое время чтобы переварить все эмоции после концерта GSPD, и теперь мы готовы поделиться впечатлениями Мы были безумно рады видеть всех приезжих гостей и столкнуться с вами в жарком слэме 💥 На концерте наши сердца порадовали старые вайбовые треки Давида, а новые песни разогрели зал до предела! Большой респект Давиду за идею с фотобудками и дизреспект КСК экспресс за отсутствие пива 🥲…
custom 518833348154911363455custom 543812190753680430551custom 537285253508000078238custom 542951126690747102411custom 52399446947958865333custom 54021453115503508101
GSPD 18.04 Съёмка/монтаж: Фуфел
custom 537285253508000078255custom 518833348154911363440custom 542951126690747102439custom 523994469479588653312custom 54381219075368043051
Ну что, бандиты, готовы покорять Москву? Готовьтесь к настоящему безумию! Этой весной мы едем в Москву на концерт нашего кумира CMH, и это будет нечто 💥 📅 Дата выезда: 2 мая 🚌 Маршрут: Ростов-на-Дону -> Москва (Live Арена) -> Ростов-на-Дону Что вас ждет? • Комфортабельный автобус • Жаркая атмосфера ожидания и кайфа перед выступлением CMH 🎸 • После концерта мы соберем все эмоции и вернемся в Ростов с полными карман…
custom 537285253508000078241custom 543812190753680430532custom 523994469479588653327custom 54295112669074710248custom 51883334815491136344
Слава КПСС 28.02 Съёмка/монтаж: Фуфел
custom 518833348154911363445custom 537285253508000078229custom 543854341133226716120custom 54381219075368043056custom 52399446947958865334
Наши друзья делают крутую движуху! Мы будем и вас ждем 😈
custom 523994469479588653324custom 543854341133226716115custom 543812190753680430510custom 53728525350800007824
Showing the 12 most recent of 13 posts we hold for @srs61. 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 — 263,998 of 1,160,990entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Свидетели Ростовского Слэма” (@srs61), 2,302 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/srs61.
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.