Telegram RegisterThe public register of Telegram
Telegram profile photo for Мониторинг по всей России

Channel

Мониторинг по всей России

@rus_monitoring

On this record: Topic · Growth · Engagement · What this channel posts · Advertising · Posts · Citations · Handles named that no longer answer · Cite this entry

49,606subscribers

-976 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002634320963
TypeChannel
Username@rus_monitoring
DescriptionОперативные оповещения об угрозах, надежная информация для вашей защиты. Оставайтесь в безопасности с нами!
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 September 2026
Measurements held30
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/rus_monitoring

Topic

National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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

49,60650,58250,0946 August 2026 — 50,582 subscribers6 August 2026 — 50,582 subscribers6 August 2026 — 50,563 subscribers7 August 2026 — 50,543 subscribers8 August 2026 — 50,506 subscribers9 August 2026 — 50,469 subscribers10 August 2026 — 50,439 subscribers11 August 2026 — 50,401 subscribers12 August 2026 — 50,367 subscribers13 August 2026 — 50,348 subscribers14 August 2026 — 50,301 subscribers15 August 2026 — 50,261 subscribers17 August 2026 — 50,209 subscribers18 August 2026 — 50,180 subscribers19 August 2026 — 50,136 subscribers20 August 2026 — 50,090 subscribers21 August 2026 — 50,061 subscribers22 August 2026 — 50,027 subscribers24 August 2026 — 49,972 subscribers25 August 2026 — 49,941 subscribers26 August 2026 — 49,920 subscribers27 August 2026 — 49,868 subscribers28 August 2026 — 49,845 subscribers29 August 2026 — 49,822 subscribers30 August 2026 — 49,810 subscribers31 August 2026 — 49,765 subscribers1 September 2026 — 49,742 subscribers2 September 2026 — 49,708 subscribers3 September 2026 — 49,675 subscribers6 September 2026 — 49,606 subscribers6 August 20266 September 2026
30 measurements spanning 31 days, net -976. 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 49,460–50,728 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)SubscribersChange
6 Sept 2026, 09:0149,606-69
3 Sept 2026, 22:3649,675-33
2 Sept 2026, 13:1849,708-34
1 Sept 2026, 13:2849,742-23
31 Aug 2026, 16:3449,765-45
30 Aug 2026, 15:4349,810-12
29 Aug 2026, 14:4849,822-23
28 Aug 2026, 14:4749,845-23
27 Aug 2026, 11:5849,868-52
26 Aug 2026, 11:5349,920-21
25 Aug 2026, 11:0349,941-31
24 Aug 2026, 10:2349,972-55
22 Aug 2026, 14:5350,027-34
21 Aug 2026, 07:5750,061-29
20 Aug 2026, 07:2250,090-46
19 Aug 2026, 08:3550,136-44
18 Aug 2026, 09:1250,180-29
17 Aug 2026, 09:3650,209-52
15 Aug 2026, 14:2650,261-40
14 Aug 2026, 03:4850,301first reading

Engagement

345 posts held, back to 4 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 82 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.51%
avg views ÷ 49,606 subscribers
Avg views / post
2,240
299 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
299
of 345 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 September 2026
Posts held345 (4 August 20266 September 2026)
Views total669,300
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Sept 2026, 00:00 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
309
Videos
272
Links
111

Lifetime counters from Telegram’s own channel header, read 7 September 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
46m 34s
Average length
31s

Measured directly from 90 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.29%
1 of 345 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
1,940
over 1 measured post
Median views · rest
2,340
over 344 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.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFJ4UbPw113 August 202613 August 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 345 most recent posts we hold, published 4 August 2026 to 6 September 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

6 Sept 2026, 23:05 UTC154 viewsread 7 September 2026

Республика Татарстан Опасность по БПЛА Мониторинг по всей России | Подписаться

6 Sept 2026, 22:45 UTC203 viewsread 7 September 2026

Самарская область Опасность по БПЛА Мониторинг по всей России | Подписаться

6 Sept 2026, 21:40 UTC387 viewsread 7 September 2026

Республика Чувашия Ульяновская область Опасность по БПЛА Мониторинг по всей России | Подписаться

6 Sept 2026, 21:10 UTC582 viewsread 7 September 2026

Отбой ракетной опасности на территории Брянской и Курской области. Мониторинг по всей России | Подписаться

6 Sept 2026, 20:50 UTC729 viewsread 7 September 2026

Брянская область Курская область Ракетная опасность! Мониторинг по всей России | Подписаться

6 Sept 2026, 20:45 UTC757 viewsread 7 September 2026

Ярославская область Опасность по БПЛА Мониторинг по всей России | Подписаться

6 Sept 2026, 20:45 UTC736 viewsread 7 September 2026

Нижегородская область Республика Мордовия Опасность по БПЛА Мониторинг по всей России | Подписаться

6 Sept 2026, 20:35 UTC766 viewsread 7 September 2026

Саратовская область Рязанская область Опасность по БПЛА Мониторинг по всей России | Подписаться

6 Sept 2026, 19:35 UTC≈1,050 viewsread 7 September 2026

Чертковский район Ростовская область Тревога по БПЛА Старый Оскол И близлежащие Тревога по БПЛА Белгородская область Новоселовка Кольчугино И близлежащие Тревога по БПЛА Республика Крым Мониторинг по всей России | Подписаться

6 Sept 2026, 19:00 UTC≈1,290 viewsread 7 September 2026

Новогремяченское, ​Хохольский район, Воронежская область - пролёты БПЛА на Воронеж, Новая Усмань, Балтимор. Хреновое, Бобровский район, Воронежская область - пролёт БПЛА в сторону Бобров или Таловая. Садовое, Аннинский район, Воронежская область - пролёт БПЛА в сторону Тамбовской области. Через Нововоронеж, Воронежской области - пролёты БПЛА в сторону Воронежа. Садовое, Аннинский район, Воронежская область - прол

6 Sept 2026, 18:05 UTC≈1,430 viewsread 7 September 2026

Тамбовская область Пензенская область Опасность по БПЛА от Воронежской области Мониторинг по всей России | Подписаться

6 Sept 2026, 18:05 UTC≈1,410 viewsread 7 September 2026

Липецкая область Опасность по БПЛА Мониторинг по всей России | Подписаться

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

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.

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

“Мониторинг по всей России” (@rus_monitoring), 49,606 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/rus_monitoring.

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.