Telegram RegisterThe public register of Telegram
Telegram profile photo for Спутник по России | БПЛА, ПВО, Обстрелы

Channel

Спутник по России | БПЛА, ПВО, Обстрелы

@sputnik_radar

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

11,314subscribers

-488 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-1002512096320
TypeChannel
Username@sputnik_radar
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/sputnik_radar

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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

11,31411,80211,5587 August 2026 — 11,802 subscribers7 August 2026 — 11,802 subscribers7 August 2026 — 11,800 subscribers8 August 2026 — 11,791 subscribers9 August 2026 — 11,785 subscribers10 August 2026 — 11,788 subscribers11 August 2026 — 11,796 subscribers12 August 2026 — 11,794 subscribers13 August 2026 — 11,784 subscribers15 August 2026 — 11,768 subscribers16 August 2026 — 11,753 subscribers17 August 2026 — 11,745 subscribers18 August 2026 — 11,742 subscribers19 August 2026 — 11,740 subscribers20 August 2026 — 11,731 subscribers21 August 2026 — 11,722 subscribers23 August 2026 — 11,710 subscribers25 August 2026 — 11,706 subscribers25 August 2026 — 11,692 subscribers26 August 2026 — 11,685 subscribers27 August 2026 — 11,681 subscribers29 August 2026 — 11,675 subscribers30 August 2026 — 11,663 subscribers1 September 2026 — 11,653 subscribers2 September 2026 — 11,650 subscribers3 September 2026 — 11,644 subscribers5 September 2026 — 11,641 subscribers8 September 2026 — 11,626 subscribers11 September 2026 — 11,606 subscribers13 September 2026 — 11,594 subscribers14 September 2026 — 11,583 subscribers16 September 2026 — 11,574 subscribers19 September 2026 — 11,570 subscribers25 September 2026 — 11,537 subscribers4 October 2026 — 11,478 subscribers8 October 2026 — 11,451 subscribers13 October 2026 — 11,438 subscribers14 October 2026 — 11,435 subscribers15 October 2026 — 11,438 subscribers16 October 2026 — 11,428 subscribers17 October 2026 — 11,422 subscribers18 October 2026 — 11,427 subscribers19 October 2026 — 11,424 subscribers20 October 2026 — 11,416 subscribers22 October 2026 — 11,408 subscribers23 October 2026 — 11,397 subscribers24 October 2026 — 11,393 subscribers25 October 2026 — 11,391 subscribers26 October 2026 — 11,388 subscribers27 October 2026 — 11,385 subscribers28 October 2026 — 11,378 subscribers29 October 2026 — 11,367 subscribers30 October 2026 — 11,365 subscribers31 October 2026 — 11,358 subscribers1 November 2026 — 11,348 subscribers2 November 2026 — 11,338 subscribers3 November 2026 — 11,333 subscribers4 November 2026 — 11,327 subscribers5 November 2026 — 11,319 subscribers6 November 2026 — 11,314 subscribers7 August 20266 November 2026
60 measurements spanning 91 days, net -488. 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 11,241–11,875 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
6 Nov 2026, 08:1811,314-5
5 Nov 2026, 11:1611,319-8
4 Nov 2026, 11:0011,327-6
3 Nov 2026, 13:1111,333-5
2 Nov 2026, 12:0811,338-10
1 Nov 2026, 13:3811,348-10
31 Oct 2026, 10:1111,358-7
30 Oct 2026, 09:3511,365-2
29 Oct 2026, 11:1511,367-11
28 Oct 2026, 06:5011,378-7
27 Oct 2026, 06:5611,385-3
26 Oct 2026, 06:2511,388-3
25 Oct 2026, 03:0611,391-2
24 Oct 2026, 04:2711,393-4
23 Oct 2026, 06:1811,397-11
22 Oct 2026, 08:2811,408-8
20 Oct 2026, 23:2111,416-8
19 Oct 2026, 20:4611,424-3
18 Oct 2026, 19:5711,427+5
17 Oct 2026, 18:5511,422first reading

Engagement

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

ERR · 30 days
2.72%
avg views ÷ 11,314 subscribers
Avg views / post
308
129 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
129
of 1,016 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 November 2026
Posts held1,016 (7 August 2026 – 6 November 2026)
Views total39,748
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 07:58 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

Video runtime
45s
Average length
11s

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

Recent posts

Telegram’s own ‘edited’ marker: 0 of 129 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

6 Nov 2026, 06:36 UTC139 viewsread 6 November 2026

Армавир Краснодарский край Фиксация БПЛА ❗️Спутник по всей России - @sputnik_radar

6 Nov 2026, 06:36 UTC139 viewsread 6 November 2026

Ставропольский край Опасность по БПЛА ❗️Спутник по всей России - @sputnik_radar

6 Nov 2026, 06:34 UTC144 viewsread 6 November 2026

Карачаево-Черкесская Республика Кабардино-Балкарская Республика Республика Северная Осетия Республика Ингушетия Республика Дагестан Чеченская Республика Опасность по БПЛА ❗️Спутник по всей России - @sputnik_radar

6 Nov 2026, 05:58 UTC202 viewsread 6 November 2026

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

6 Nov 2026, 05:50 UTC192 viewsread 6 November 2026

Воронежская область Опасность по БПЛА ❗️Спутник по всей России - @sputnik_radar

6 Nov 2026, 05:48 UTC204 viewsread 6 November 2026

За прошедшую ночь силами противовоздушной обороны было уничтожено 142 БПЛА над территориями Курской, Белгородской, Тульской, Орловской, Ростовской, Астраханской областей, Московского региона, Краснодарского края, Республики Крым и над акваториями Черного и Азовского морей. ❗️Спутник по всей России - @sputnik_radar

6 Nov 2026, 05:36 UTC223 viewsread 6 November 2026

Ростовская область Волгоградская область Саратовская область Самарская область Отбой опасности по БПЛА ❗️Спутник по всей России - @sputnik_radar

6 Nov 2026, 03:48 UTC291 viewsread 6 November 2026

Краснодарский край Республика Адыгея Ракетная опасность ❗️Спутник по всей России - @sputnik_radar

6 Nov 2026, 03:30 UTC293 viewsread 6 November 2026

Московская область Отбой опасности по БПЛА ❗️Спутник по всей России - @sputnik_radar

6 Nov 2026, 03:22 UTC296 viewsread 6 November 2026

Липецкая область Отбой опасности по БПЛА ❗️Спутник по всей России - @sputnik_radar

6 Nov 2026, 02:42 UTC307 viewsread 6 November 2026

Тульская область Орловская область Отбой опасности по БПЛА ❗️Спутник по всей России - @sputnik_radar

6 Nov 2026, 02:20 UTC320 viewsread 6 November 2026

Калужская область Отбой опасности по БПЛА ❗️Спутник по всей России - @sputnik_radar

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

“Спутник по России | БПЛА, ПВО, Обстрелы” (@sputnik_radar), 11,314 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/sputnik_radar.

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.