Telegram RegisterThe public register of Telegram
Telegram profile photo for Российский Купол

Channel

Российский Купол

@russiakupol_radar_bpla

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

16,979subscribers

-174 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-1002309835412
TypeChannel
Username@russiakupol_radar_bpla
DescriptionОперативное оповещение гражданского населения о угрозах атаки БПЛА и авиационых опасностях. Обратная связь — @malikk116
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 November 2026
Measurements held56
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/russiakupol_radar_bpla

Topic

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 43% 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 the other topics.

Growth

16,97917,38517,1827 August 2026 — 17,153 subscribers8 August 2026 — 17,158 subscribers9 August 2026 — 17,155 subscribers10 August 2026 — 17,146 subscribers11 August 2026 — 17,143 subscribers12 August 2026 — 17,134 subscribers13 August 2026 — 17,129 subscribers14 August 2026 — 17,125 subscribers16 August 2026 — 17,113 subscribers17 August 2026 — 17,367 subscribers18 August 2026 — 17,382 subscribers19 August 2026 — 17,385 subscribers20 August 2026 — 17,370 subscribers21 August 2026 — 17,365 subscribers22 August 2026 — 17,363 subscribers24 August 2026 — 17,355 subscribers25 August 2026 — 17,345 subscribers26 August 2026 — 17,340 subscribers27 August 2026 — 17,335 subscribers28 August 2026 — 17,325 subscribers29 August 2026 — 17,322 subscribers30 August 2026 — 17,315 subscribers31 August 2026 — 17,305 subscribers1 September 2026 — 17,292 subscribers1 September 2026 — 17,284 subscribers3 September 2026 — 17,277 subscribers4 September 2026 — 17,273 subscribers7 September 2026 — 17,263 subscribers10 September 2026 — 17,236 subscribers12 September 2026 — 17,221 subscribers14 September 2026 — 17,235 subscribers16 September 2026 — 17,218 subscribers18 September 2026 — 17,206 subscribers30 September 2026 — 17,138 subscribers5 October 2026 — 17,101 subscribers10 October 2026 — 17,075 subscribers13 October 2026 — 17,054 subscribers15 October 2026 — 17,051 subscribers16 October 2026 — 17,049 subscribers17 October 2026 — 17,051 subscribers18 October 2026 — 17,059 subscribers19 October 2026 — 17,052 subscribers20 October 2026 — 17,047 subscribers21 October 2026 — 17,044 subscribers22 October 2026 — 17,049 subscribers23 October 2026 — 17,036 subscribers24 October 2026 — 17,035 subscribers25 October 2026 — 17,032 subscribers26 October 2026 — 17,028 subscribers27 October 2026 — 17,020 subscribers28 October 2026 — 17,016 subscribers29 October 2026 — 17,011 subscribers30 October 2026 — 17,003 subscribers31 October 2026 — 16,992 subscribers1 November 2026 — 16,989 subscribers2 November 2026 — 16,979 subscribers7 August 20262 November 2026
56 measurements spanning 87 days, net -174. 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 16,918–17,446 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 56
Measured (UTC)SubscribersChange
2 Nov 2026, 19:4716,979-10
1 Nov 2026, 16:3016,989-3
31 Oct 2026, 18:4716,992-11
30 Oct 2026, 20:2717,003-8
29 Oct 2026, 19:2617,011-5
28 Oct 2026, 18:0817,016-4
27 Oct 2026, 19:4117,020-8
26 Oct 2026, 17:4617,028-4
25 Oct 2026, 15:3117,032-3
24 Oct 2026, 17:0417,035-1
23 Oct 2026, 14:5617,036-13
22 Oct 2026, 13:4917,049+5
21 Oct 2026, 09:0917,044-3
20 Oct 2026, 06:5017,047-5
19 Oct 2026, 08:5917,052-7
18 Oct 2026, 05:5717,059+8
17 Oct 2026, 02:3917,051+2
16 Oct 2026, 02:4717,049-2
15 Oct 2026, 01:4017,051-3
13 Oct 2026, 18:4717,054first reading

Engagement

863 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 54 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.749%
avg views ÷ 16,979 subscribers
Avg views / post
127
20 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
20
of 863 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 3 November 2026
Posts held863 (7 August 2026 – 3 November 2026)
Views total2,545
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Nov 2026, 03:36 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
≈476
Videos
≈273
Links
≈12,500

Lifetime counters from Telegram’s own channel header, read 3 November 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
3m 08s
Average length
21s

Measured directly from 9 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.116%
1 of 863 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
713
over 1 measured post
Median views · rest
351
over 862 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
2W5zFJ4UbPw114 August 202614 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 863 most recent posts we hold, published 7 August 2026 to 3 November 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

3 Nov 2026, 03:16 UTC45 viewsread 3 November 2026

Вологодская область Опасность по БПЛА Российский Купол | Подписаться

3 Nov 2026, 02:36 UTC101 viewsread 3 November 2026

Владимирская область Волгоградская область Воронежская область Ивановская область Липецкая область Московская область Нижегородская область Пензенская область Республика Мордовия Республика Татарстан Республика Чувашия Ростовская область Рязанская область Саратовская область Ставропольский край Тамбовская область Тульская область Ульяновская область Ярославская область Отбой ракетной опасности Российский Купол | По…

3 Nov 2026, 02:36 UTC95 viewsread 3 November 2026

Самарская область ракетная опасность! Российский Купол | Подписаться

3 Nov 2026, 02:24 UTC106 viewsread 3 November 2026

Ярославская область Ульяновская область Отбой ракетной опасности Российский Купол | Подписаться

3 Nov 2026, 02:22 UTC109 viewsread 3 November 2026

Саратовская область Волгоградская область Ставропольский край Ростовская область Воронежская область Липецкая область Тамбовская область Пензенская область Республика Чувашия Отбой ракетной опасности Российский Купол | Подписаться

3 Nov 2026, 01:48 UTC131 viewsread 3 November 2026

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

3 Nov 2026, 01:20 UTC129 viewsread 3 November 2026

Тамбовская область Саратовская область Волгоградская область Ставропольский край Липецкая область Ракетная опасность Российский Купол | Подписаться

3 Nov 2026, 01:04 UTC157 viewsread 3 November 2026

Курба Мышкин Космодемьянск Продолжаются фиксации в сторону Ярославля Тревога сохраняется! Берегите себя! При работе ПВО соблюдайте меры безопасности! Российский Купол | Подписаться

3 Nov 2026, 00:48 UTC166 viewsread 3 November 2026

Ярославль НПЗ Скорее всего вы цель БПЛА. Принять меры безопасности! Российский Купол | Подписаться

3 Nov 2026, 00:36 UTC151 viewsread 3 November 2026

Пролет в сторону Черемисиново Курская область Советский район Российский Купол | Подписаться

3 Nov 2026, 00:34 UTC148 viewsread 3 November 2026

Московская область Истра Клин Дубна Химки Нагорное Мытищи Королёв Опасность по БПЛА Тверская область Редкино Тверь Конаково Опасность по БПЛА г.Ярославль и близлежащие Внимание к возможному налёту БПЛА с юго-запада Запада Российский Купол | Подписаться

3 Nov 2026, 00:08 UTC127 viewsread 3 November 2026

Брянская область Белгородская область Курская область Смоленская область Калужская область Орловская область Тверская область Тульская область Липецкая область Московская область Рязанская область Нижегородская область Владимирская область Ивановская область Ярославская область Вологодская область Псковская область Новгородская область Краснодарский край Республика Крым Опасность по БПЛА сохраняется Берегите себя и …

Showing the 12 most recent of 863 posts we hold for @russiakupol_radar_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 2 November 2026 — this entry's latest reading, not the date you are reading this.

“Российский Купол” (@russiakupol_radar_bpla), 16,979 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/russiakupol_radar_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.