Telegram RegisterThe public register of Telegram
Telegram profile photo for Первый Радар РФ | БПЛА | Обстрелы

Channel

Первый Радар РФ | БПЛА | Обстрелы

@Radar_Russia_bpla

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

49,436subscribers

-234 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002771349169
TypeChannel
Username@Radar_Russia_bpla
DescriptionИнформационный источник, оповещение об угрозах и БПЛА 🔔Включите обязательно уведомления, чтобы получать точную и оперативную информацию Сотрудничество - @RadarRF7_bot Администратор: @Prizrak_0103
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 August 2026
Measurements held13
Confirmed unchanged1 time, most recently 19 August 2026
On Telegramt.me/Radar_Russia_bpla

Growth

49,41849,67049,5447 August 2026 — 49,670 subscribers7 August 2026 — 49,670 subscribers7 August 2026 — 49,666 subscribers8 August 2026 — 49,649 subscribers10 August 2026 — 49,616 subscribers10 August 2026 — 49,583 subscribers11 August 2026 — 49,551 subscribers13 August 2026 — 49,515 subscribers14 August 2026 — 49,478 subscribers16 August 2026 — 49,426 subscribers17 August 2026 — 49,418 subscribers18 August 2026 — 49,470 subscribers19 August 2026 — 49,436 subscribers49,4367 August 202619 August 2026
13 measurements spanning 12 days, net -234. 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,380–49,708 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Aug 2026, 15:4649,436-34
18 Aug 2026, 14:0749,470+52
17 Aug 2026, 12:1249,418-8
16 Aug 2026, 02:1349,426-52
14 Aug 2026, 13:0549,478-37
13 Aug 2026, 01:4449,515-36
11 Aug 2026, 22:1349,551-32
10 Aug 2026, 22:3349,583-33
10 Aug 2026, 00:5849,616-33
8 Aug 2026, 22:0049,649-17
7 Aug 2026, 20:0349,666-4
7 Aug 2026, 17:3049,670no change
7 Aug 2026, 17:1949,670first reading

Engagement

434 posts held, back to 7 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 28 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
1.46%
avg views ÷ 49,436 subscribers
Avg views / post
723
432 posts measured
Reaction rate
0.236%
reactions ÷ views · ER floor
Posts in window
434
of 434 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. It is computed over the 114 of 432 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 19 August 2026
Posts held434 (7 August 202619 August 2026)
Views total312,473
Reactions total221
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 00:38 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
554
Videos
297
Links
5,850

Lifetime counters from Telegram’s own channel header, read 20 August 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.

Video runtime
12m 54s
Average length
26s

Measured directly from 30 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.

Reaction mix

221 reactions across 89 posts, in 8 distinct kinds. The most used accounts for 30.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6730.3%
🙏5022.6%
👍4018.1%
👎2511.3%
😱135.88%
🤬125.43%
😢114.98%
💯31.36%

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 114 of the 434 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 221reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 434 most recent posts we hold, published 7 August 2026 to 19 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.

Advertising

Ad load
0.23%
1 of 434 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
842
over 1 measured post
Median views · rest
747
over 431 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
2W5zFJK5hzR117 August 202617 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 434 most recent posts we hold, published 7 August 2026 to 19 August 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

19 Aug 2026, 23:40 UTC158 viewsread 20 August 2026

Московская область Кубинка Тучково Серпухов Пущино Ступино Озёры Коломна Михнево Чехов Барыбино Белые Столбы Львовский Климовск Домодедово Бронницы Опасность по БПЛА ❗️Первый Радар РФ - @RadarRussia

19 Aug 2026, 23:30 UTC188 views1 reactionsread 20 August 2026

Тульская область Тула работа ПВО по БПЛА. Меры безопасности! ❗️Первый Радар РФ - @RadarRussia

1

19 Aug 2026, 22:50 UTC258 viewsread 20 August 2026

Калужская область Орловская область Тульская область Московская область Владимирская область Опасность по БПЛА. Над Пензенской областью массовые фиксации в сторону Ульяновской области, далее на Самарскую область, от Самарской области на Республику Татарстан. Краснодарский край Республика Крым Ростовская область Тревога по БПЛА сохраняется. ❗️Первый Радар РФ - @RadarRussia

19 Aug 2026, 22:15 UTC358 viewsread 20 August 2026

Орел Сбитие БПЛА Меры безопасности! ❗️Первый Радар РФ - @RadarRussia

19 Aug 2026, 21:55 UTC419 views2 reactionsread 20 August 2026

Рязанская область Республика Мордовия Нижегородская область Опасность по БПЛА. Брянская область Массовые пролеты в тыловые регионы Астраханская область Ахтубинск Сбитие Еще фиксации Краснодарский край Причерноморье Опасность по БПЛА Анапа Новороссийск Кабардинка Геленджик Туапсе Сочи ❗️Первый Радар РФ - @RadarRussia

2

19 Aug 2026, 21:30 UTC456 views1 reactionsread 20 August 2026

Самарская область Ульяновская область Опасность по БПЛА. Тамбовская область Курская область Орловская область Не попадите под осколки! ❗️Первый Радар РФ - @RadarRussia

1

19 Aug 2026, 21:05 UTC521 viewsread 20 August 2026

Ростовская область Миллеровский район Слобода Колодези Множественные пролеты БПЛА и сбития Находимся в укрытиях. Краснодарский край Таманский полуостров Темрюкский район Анапский район Новороссийск Геленджик Туапсе Опасность по БПЛА Астраханская область Опасность по БПЛА Белгородская область Курская область Брянская область Ростовская область Волгоградская область Воронежская область Меры безопасности ! ❗️Первый

19 Aug 2026, 20:45 UTC566 viewsread 20 August 2026

Воронежская область Аннинский район Пролеты на северо-запад ❗️Первый Радар РФ - @RadarRussia

19 Aug 2026, 20:40 UTC595 views3 reactionsread 20 August 2026

Воронежская область Липецкая область Саратовская область Тамбовская область Пензенская область Орловская область Ракетная опасность. ❗️Первый Радар РФ - @RadarRussia

🙏3

19 Aug 2026, 20:35 UTC674 views0 reactionsread 20 August 2026

Воронежская область Продолжаются фиксации от Белгородской области Соблюдаем меры безопасности БЕСПИЛОТНАЯ ОПАСНОСТЬ на территории муниципальных образований: Приморско-Ахтарский МО, Ейский, Щербиновский, Каневской, Брюховецкий районы. Ростовская область Продолжаются фиксации на Волгоградскую область Брянская область Фиксации над областью и далее в таловые регионы на: Тульскую область Смоленскую область Калужскую об

19 Aug 2026, 20:20 UTC626 viewsread 20 August 2026

Волгоградская область Нехаевская Урюпинск Суровикино Клетская Серафимович Кумылженская Алексеевский Опасность по БПЛА Фиксации по данным направлениям Будут прорываться на Саратовскую ❗️Первый Радар РФ - @RadarRussia

19 Aug 2026, 20:05 UTC640 viewsread 20 August 2026

Саратовская область Внимание по небу от Воронежской области и Волгоградской области ❗️Первый Радар РФ - @RadarRussia

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

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

“Первый Радар РФ | БПЛА | Обстрелы” (@Radar_Russia_bpla), 49,436 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/Radar_Russia_bpla.

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.