❗Ракетная опасность объявлена в Ростовской области. Ранее также предупреждали о беспилотной.
🙏7

Channel
@rostov_chp_61
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
27,662subscribers
-196 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001736152696 |
|---|---|
| Type | Channel |
| Username | @rostov_chp_61 |
| Description | Все горячие события Ростова и области! Прислать новость/Реклама: @Reklama_rnd |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/rostov_chp_61 |
National news — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 00:58 | 27,662 | +10 |
| 16 Sept 2026, 15:19 | 27,652 | -10 |
| 14 Sept 2026, 19:40 | 27,662 | -6 |
| 13 Sept 2026, 06:00 | 27,668 | -8 |
| 11 Sept 2026, 08:36 | 27,676 | -36 |
| 8 Sept 2026, 16:00 | 27,712 | +42 |
| 5 Sept 2026, 09:40 | 27,670 | -23 |
| 3 Sept 2026, 09:44 | 27,693 | -5 |
| 2 Sept 2026, 06:37 | 27,698 | -10 |
| 1 Sept 2026, 05:16 | 27,708 | -5 |
| 31 Aug 2026, 07:54 | 27,713 | +2 |
| 30 Aug 2026, 09:57 | 27,711 | -2 |
| 29 Aug 2026, 11:56 | 27,713 | +32 |
| 28 Aug 2026, 14:56 | 27,681 | -5 |
| 27 Aug 2026, 17:25 | 27,686 | -8 |
| 26 Aug 2026, 20:54 | 27,694 | -5 |
| 25 Aug 2026, 22:14 | 27,699 | -12 |
| 25 Aug 2026, 00:59 | 27,711 | -5 |
| 23 Aug 2026, 12:14 | 27,716 | -16 |
| 22 Aug 2026, 00:23 | 27,732 | first reading |
739 posts held, back to 6 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 61 pages of 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. It is computed over the 231 of 340 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 19 September 2026 |
|---|---|
| Posts held | 739 (6 August 2026 – 19 September 2026) |
| Views total | 224,599 |
| Reactions total | 1,289 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 19 Sept 2026, 19:51 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.
Lifetime counters from Telegram’s own channel header, read 19 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 366 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.
2,997 reactions across 505 posts, in 26 distinct kinds. The most used accounts for 10.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😢 | 320 | 10.7% | |
| 🤬 | 319 | 10.6% | |
| ❤ | 297 | 9.91% | |
| 🙏 | 274 | 9.14% | |
| 🤡 | 252 | 8.41% | |
| 👍 | 240 | 8.01% | |
| 🤯 | 229 | 7.64% | |
| 😱 | 165 | 5.51% | |
| 😁 | 153 | 5.11% | |
| 🔥 | 128 | 4.27% | |
| 🤣 | 120 | 4.00% | |
| 👎 | 76 | 2.54% | |
| 😭 | 72 | 2.40% | |
| 💯 | 71 | 2.37% | |
| 👀 | 41 | 1.37% | |
| 💊 | 38 | 1.27% | |
| 🤪 | 38 | 1.27% | |
| 🤔 | 33 | 1.10% | |
| 🕊 | 30 | 1.00% | |
| 😐 | 29 | 0.968% | |
| 6 further kinds | 72 | 2.40% |
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 521 of the 739 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 2,997 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 739 most recent posts we hold, published 6 August 2026 to 19 September 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.
❗Ракетная опасность объявлена в Ростовской области. Ранее также предупреждали о беспилотной.
🙏7
🚨 Мальчика на электросамокате сбили в парке Островского. По словам очевидцев, у ребёнка сломана кисть, потребовалась помощь медиков
😢3
🤬 "Ничего не меняется уже в течение месяца! Этот мусорный коллапс наблюдаем по адресу Оганова между домами 7 и 11. Когда это прекратится?! Неужели нельзя добавить хотя бы пару мусорных баков, чтобы хлам хотя бы частично переместился с земли в контейнеры?! Когда же нас заметят и примут меры?!", — негодует подписчица.
❤1
⚠️ Курьера Яндекса сбили на Нансена/Будённовском. Парень лежит в крови, разбил голову. Помощь оказывают очевидцы и другие водители
❤1
🔪🩸 Резня возле Сбера на Будённовском. Тротуар залит кровью, на месте экстренные службы. Подробности уточняются Дополнение: мужика несколько раз пырнули в ногу, попали в артерию. Его забрала реанимация
😱4
😳 11-летний школьник на электровелосипеде сбил восьмилетнюю девочку в п. Матвеев Курган. Ребёнок ехал на мощном электровелосипеде и не успел затормозить перед девочкой, которая двигалась в том же направлении. Пострадавшую с травмами доставили в больницу
⚠️ Беспилотная опасность объявлена по южной части Ростовской области. Самый оперативный мониторинг в резервном канале: max.ru/glavnyi_rostov
🙏2😁1
🐋 Акулу заметили в центре Ростова! Будьте аккуратнее!
🤣7❤3👍3🤡1
🚕 Таксист решил прокатиться по лестнице в центре, но, видимо, что-то пошло не по плану...
🤡2❤1
🕊 "Восьмого сентября в зоне СВО погиб наш герой Волков Сергей Александрович, уроженец Волгодонска! Служил в звании рядового. Был воином всю жизнь: с 18 лет! Помним, любим, скорбим...", — пишет наша читательница.
😭8🕊2
🐐 Ростовский "козёл" на 2-й Краснодарской
😁5🤔1
🚨 Водитель купил «права» за 180 тысяч — и получил уголовное дело в Ростовской области. Всё началось с обычной остановки: инспекторы ДПС в Волгодонске тормознули Peugeot. Когда попросили показать водительское удостоверение, водитель вдруг сильно занервничал. Документ сразу показался полицейским подозрительным: данные в нём не совпадали с личностью водителя. Проверка по базам всё подтвердила: права с такими серией и …
Showing the 12 most recent of 739 posts we hold for @rostov_chp_61. 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.
@rostov_chp_61 edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Типичный Ростов - новости Ростова-на-Дону” (@rostov_chp_61), 27,662 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/rostov_chp_61.
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.