Орловский район Орловская область Фиксация группы БПЛА в направлении Калужская область, Тульская область ❗️РСЧС по Всей России — @radar_rschs

Channel
РСЧС по Всей России | БПЛА, Обстрелы, ПВО
@radar_rschs
On this record: Topic · Growth · Engagement · What this channel posts · Advertising · Posts · Citations · Handles named that no longer answer · Cite this entry
24,421subscribers
-1,450 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002879990154 |
|---|---|
| Type | Channel |
| Username | @radar_rschs |
| Description | Информационный российский источник для оповещения населения о воздушной угрозе. 🔔Включите обязательно уведомления, чтобы получать точную и оперативную информацию По вопросам: @Liza_reklama @ktoktoktoktooo |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 36 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/radar_rschs |
Topic
Other / unclassifiable — 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 62% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 22:55 | 24,421 | -68 |
| 8 Oct 2026, 14:00 | 24,489 | -65 |
| 4 Oct 2026, 02:57 | 24,554 | -167 |
| 25 Sept 2026, 07:40 | 24,721 | -125 |
| 18 Sept 2026, 22:16 | 24,846 | -54 |
| 16 Sept 2026, 10:18 | 24,900 | -40 |
| 14 Sept 2026, 16:15 | 24,940 | -30 |
| 13 Sept 2026, 00:41 | 24,970 | -50 |
| 11 Sept 2026, 02:58 | 25,020 | -110 |
| 8 Sept 2026, 07:37 | 25,130 | -64 |
| 5 Sept 2026, 02:20 | 25,194 | -32 |
| 3 Sept 2026, 06:44 | 25,226 | -31 |
| 2 Sept 2026, 04:01 | 25,257 | -48 |
| 1 Sept 2026, 02:18 | 25,305 | -19 |
| 30 Aug 2026, 23:54 | 25,324 | -16 |
| 30 Aug 2026, 02:45 | 25,340 | -33 |
| 29 Aug 2026, 03:24 | 25,373 | -21 |
| 28 Aug 2026, 06:38 | 25,394 | -30 |
| 27 Aug 2026, 04:24 | 25,424 | -26 |
| 26 Aug 2026, 05:48 | 25,450 | first reading |
Engagement
1,492 posts held, back to 7 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 88 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.11%
- avg views ÷ 24,421 subscribers
- Avg views / post
- 514
- 607 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 607
- of 1,492 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.
| Window | Rolling 30 days · latest post in window 13 October 2026 |
|---|---|
| Posts held | 1,492 (7 August 2026 – 13 October 2026) |
| Views total | 312,205 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Oct 2026, 02:56 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
- Photos
- 33
- Videos
- 18
- Links
- 5
Lifetime counters from Telegram’s own channel header, read 13 October 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
- 3m 36s
- Average length
- 22s
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.
Advertising
- Ad load
- 0.1%
- 1 of 1,000 posts carry an ad marker
- Regulatory tokens
- 1
- posts carrying an erid · 1 distinct token
- Median views · ads
- 527
- over 1 measured post
- Median views · rest
- 654
- over 999 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2W5zFJmvbt5 | 1 | 7 October 2026 | 7 October 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 22 August 2026 to 13 October 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
Ржакса о Тамбовская бласть Фиксации от 2 БПЛА в сторону Котовск, Тамбов, Рассказово ❗️РСЧС по Всей России — @radar_rschs
Наро-Фоминск Кубинка Тучково Одинцово Руза Истра Красногорск Зеленоград Клин Дубна И близлежащие города и населённые пункты Московская область Опасность по БПЛА сохраняется Продолжаются сбития по направлению Дзержинский район Ферзиковский район г.Калуга Малоярославецкий район Жуковский район Калужская область Опасность по БПЛА сохраняется и в направлении Московской области Продолжаются фиксации ударных БПЛА ❗️РСЧС …
Восточная часть Костромской области Опасность по БПЛА Палех Ивановская область Фиксации ударных БПЛА на север Дмитров Яхрома Краснозаводск Сергиев Посад Красноармейск Пушкино Королёв Щёлково Черноголовка Московская область Внимание по возможным БПЛА противника ❗️РСЧС по Всей России — @radar_rschs
Костромская область Ярославская область Опасность по БПЛА Смоленская область Опасность по БПЛА от Сураж Унеча Невинномысск Ставропольский край Продолжается массовый налёт БПЛА Остаёмся в безопасных местах ❗️РСЧС по Всей России — @radar_rschs
Архангельская область Опасность по БПЛА от Вологодской области Плахино Захаровский район Рязанская область Фиксации ударных БПЛА на север в сторону юго-восточной части Московской области посёлок имени Желябова Устюженский район Вологодская область Предварительно пролёты ударных БПЛА на север Северо-восток Продолжаются пролёты ударных БПЛА от госграницы В сторону Брянской области Курской области Белгородской област…
Отбой ракетной опасности! ❗️РСЧС по Всей России — @radar_rschs
Ивановская область Владимирская область Нижегородская область Опасность по БПЛА Смоленская область Ярцево Сафоново Дорогобуж Вязьма и близлежащие Опасность по БПЛА от Десногорск Рославль Смоленская область Фиксации ударных БПЛА в сторону Десногорск Московская область Ивантеевка Мытищи Особое внимание по БПЛА ближайшее время ❗️РСЧС по Всей России — @radar_rschs
Краснодарский край Ракетная опасность! Особое внимание Новороссийск и близлежащие ❗️РСЧС по Всей России — @radar_rschs
Орловская область Лубянки Дмитровский район Пролёты БПЛА в сторону Орёл Стальной Конь Отрадинское Мценск И далее на Тульскую область Рязанская область Малинки Михайловский район Пролёты БПЛА в сторону Московской области Калуга Детчино Малоярославец Обнинск Жуков Боровск и близлежащие Калужская область Опасность по БПЛА сохраняется Очередной пролёт БПЛА в сторону Московской области Троицкий административный округ М…
Вся территория Ставропольского края Опасность по БПЛА от Краснодарского края Много идёт Липецк и район В т.ч. аэ.Липецк-2 Липецкая область Опасность по БПЛА сохраняется Мценск и близлежащие Орловская область Фиксации БПЛА в сторону Чернь Плавск Тёплое Щёкино Тульской области И далее в тыл Ростов-Великий Ярославская область Предварительно фиксация 1 БПЛА в сторону Семибратово Красные Ткачи Ярославль ❗️РСЧС по Всей…
ТРЕВОГА ПО БПЛА на территории муниципальных образований: Красногвардейский округ Изобильненский округ Новоалександровский округ Ипатовский округ Труновский округ Грачёвский округ Петровский округ Шпаковский округ Кочубеевский округ Андроповский округ Апанасенковский округ г. Невинномысск и г. Ставрополь ❗️РСЧС по Всей России — @radar_rschs
Showing the 12 most recent of 1,492 posts we hold for @radar_rschs. 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
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.
@vpnsave · 252,4794 postsSkiskimasssk
@abknlive · 73 posts🚧ДТП АРХАНГЕЛЬСКА🚧
@arhangelsklive · 143 postsAstrakhan.live Лайк
@Astrakhanlive · 93 postsБарнаул лайв
@barnaullive · 1073 postsИркутск live
@irkutsklive · 253 postsКалининград | все обо всем 🌆
@kaliningradLive · 623 postsKazan
@kazanlive · 183 postsКУРСК (БЕЗ ОПОВЕЩЕНИЙ) Школьная жизнь
@kurskLIVE · 403 postsЛипецк LIVE
@lipetsklive · 1,4893 postsМагнитогорск лайв
@magnitogorsklive · 83 postsНижний Новгород лайв
@nizhnynovlive · 233 postsНовоалтайск Live ДТП и ЧС
@novoaltaisklive · 183 postsНВКЗ
@novokuznetsklive · 103 postsНОВОРОССИЯ
@novorussialive · 283 postsNskLive
@NovosibirskLIVE · 173 postsПермь LIVE
@permlive · 113 postsПетрозаводск Live
@petrozavodsklive · 2583 postsАндрей Савельев
@razvitie · 7373 postsSAHALIN LIVE
@SAHALINLIVE · 103 postsПыльный Сратов
@saratovlive · 2,1003 postsСтаврополь LIVE
@Stavropollive · 593 postsTonPlay
@tonplay · 437,0213 postsUNSTOP VPN
@unstop_vpn_bot · 20,5072 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.
Handles this channel named that no longer answer
- Dead references
- 41
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 41
- vacant every time we have ever looked
@radar_rschs named 41 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 360 posts, 8 August 2026 – 4 September 2026
named in 1 post, 3 October 2026 – 3 October 2026
named in 1 post, 1 October 2026 – 1 October 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 2026
named in 1 post, 18 August 2026 – 18 August 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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“РСЧС по Всей России | БПЛА, Обстрелы, ПВО” (@radar_rschs), 24,421 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/radar_rschs.
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.