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

Channel

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

@SputnikRussia_radar

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

19,400subscribers

-953 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-1002257159698
TypeChannel
Username@SputnikRussia_radar
DescriptionОперативное оповещение мирного населения о надвигающихся воздушных угрозах. Сирены, ракеты, работа ПВО и все тому подобное — только здесь. 🤝🏻 Сотрудничество - @m1khailromanov
CreatedBetween 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 November 2026
Measurements held58
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/SputnikRussia_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 10 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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

19,40020,35319,876.57 August 2026 — 20,353 subscribers7 August 2026 — 20,353 subscribers8 August 2026 — 20,344 subscribers9 August 2026 — 20,332 subscribers10 August 2026 — 20,322 subscribers11 August 2026 — 20,306 subscribers12 August 2026 — 20,288 subscribers13 August 2026 — 20,266 subscribers15 August 2026 — 20,249 subscribers16 August 2026 — 20,237 subscribers17 August 2026 — 20,219 subscribers18 August 2026 — 20,206 subscribers19 August 2026 — 20,198 subscribers20 August 2026 — 20,180 subscribers21 August 2026 — 20,167 subscribers23 August 2026 — 20,161 subscribers24 August 2026 — 20,144 subscribers25 August 2026 — 20,140 subscribers26 August 2026 — 20,134 subscribers27 August 2026 — 20,127 subscribers28 August 2026 — 20,117 subscribers29 August 2026 — 20,102 subscribers30 August 2026 — 20,098 subscribers31 August 2026 — 20,089 subscribers1 September 2026 — 20,069 subscribers3 September 2026 — 20,051 subscribers5 September 2026 — 20,030 subscribers8 September 2026 — 20,006 subscribers11 September 2026 — 19,969 subscribers13 September 2026 — 19,947 subscribers14 September 2026 — 19,927 subscribers16 September 2026 — 19,898 subscribers18 September 2026 — 19,867 subscribers2 October 2026 — 19,729 subscribers7 October 2026 — 19,677 subscribers11 October 2026 — 19,631 subscribers14 October 2026 — 19,599 subscribers15 October 2026 — 19,590 subscribers16 October 2026 — 19,578 subscribers17 October 2026 — 19,571 subscribers19 October 2026 — 19,580 subscribers20 October 2026 — 19,563 subscribers21 October 2026 — 19,551 subscribers22 October 2026 — 19,543 subscribers23 October 2026 — 19,531 subscribers24 October 2026 — 19,522 subscribers25 October 2026 — 19,514 subscribers26 October 2026 — 19,507 subscribers27 October 2026 — 19,494 subscribers28 October 2026 — 19,487 subscribers29 October 2026 — 19,473 subscribers30 October 2026 — 19,454 subscribers31 October 2026 — 19,443 subscribers1 November 2026 — 19,436 subscribers2 November 2026 — 19,422 subscribers3 November 2026 — 19,416 subscribers4 November 2026 — 19,406 subscribers5 November 2026 — 19,400 subscribers7 August 20265 November 2026
58 measurements spanning 90 days, net -953. 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 19,257–20,496 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 58
Measured (UTC)SubscribersChange
5 Nov 2026, 17:4919,400-6
4 Nov 2026, 18:3619,406-10
3 Nov 2026, 20:5619,416-6
2 Nov 2026, 20:4719,422-14
1 Nov 2026, 18:5819,436-7
31 Oct 2026, 17:0619,443-11
30 Oct 2026, 14:2819,454-19
29 Oct 2026, 10:5619,473-14
28 Oct 2026, 08:5819,487-7
27 Oct 2026, 09:1619,494-13
26 Oct 2026, 09:0619,507-7
25 Oct 2026, 08:5619,514-8
24 Oct 2026, 10:2819,522-9
23 Oct 2026, 08:1719,531-12
22 Oct 2026, 09:5119,543-8
21 Oct 2026, 00:4719,551-12
20 Oct 2026, 00:1619,563-17
19 Oct 2026, 02:3019,580+9
17 Oct 2026, 23:0619,571-7
16 Oct 2026, 23:5619,578first reading

Engagement

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

ERR · 30 days
1.32%
avg views ÷ 19,400 subscribers
Avg views / post
257
117 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
117
of 957 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 held957 (7 August 2026 – 6 November 2026)
Views total30,074
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 03:21 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
≈28
Videos
≈34
Links
≈67,300

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

Measured directly from 1 video 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 117 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, 02:42 UTC59 viewsread 6 November 2026

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

6 Nov 2026, 02:21 UTC76 viewsread 6 November 2026

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

6 Nov 2026, 02:21 UTC76 viewsread 6 November 2026

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

6 Nov 2026, 02:18 UTC82 viewsread 6 November 2026

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

6 Nov 2026, 02:15 UTC81 viewsread 6 November 2026

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

6 Nov 2026, 02:15 UTC80 viewsread 6 November 2026

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

6 Nov 2026, 01:21 UTC109 viewsread 6 November 2026

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

5 Nov 2026, 22:39 UTC172 viewsread 6 November 2026

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

5 Nov 2026, 22:33 UTC182 viewsread 6 November 2026

Астраханская область Республика Калмыкия Опасность по БПЛА 📲 Наш канал в МАХ - ❗️Спутник по всей России - @sputnik_radar

5 Nov 2026, 21:30 UTC234 viewsread 6 November 2026

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

5 Nov 2026, 21:12 UTC246 viewsread 6 November 2026

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

5 Nov 2026, 20:48 UTC273 viewsread 6 November 2026

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

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“Спутник по России | БПЛА, ПВО, Обстрелы” (@SputnikRussia_radar), 19,400 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/SputnikRussia_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.