Telegram RegisterThe public register of Telegram
Telegram profile photo for Радар Москва | БПЛА, Ракеты, Авиация | Московская область

Channel

Радар Москва | БПЛА, Ракеты, Авиация | Московская область

@bpla777

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

991subscribers

+506 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003963688720
TypeChannel
Username@bpla777
CreatedBetween 1 April 2026 and 6 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live26 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/bpla777

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

4859917387 August 2026 — 485 subscribers8 August 2026 — 485 subscribers8 August 2026 — 490 subscribers15 August 2026 — 519 subscribers22 August 2026 — 677 subscribers28 August 2026 — 729 subscribers4 September 2026 — 802 subscribers12 September 2026 — 810 subscribers26 September 2026 — 991 subscribers7 August 202626 September 2026
9 measurements spanning 49 days, net +506. 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 409–1,067 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 02:37991+181
12 Sept 2026, 20:02810+8
4 Sept 2026, 07:01802+73
28 Aug 2026, 11:14729+52
22 Aug 2026, 09:45677+158
15 Aug 2026, 13:56519+29
8 Aug 2026, 04:33490+5
8 Aug 2026, 04:32485no change
7 Aug 2026, 19:29485first reading

Engagement

20 posts held, back to 6 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 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

13 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 69.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😱969.2%
🤯323.1%
🤬17.69%

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

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

Recent posts

8 Aug 2026, 04:01 UTC13 viewsread 8 August 2026

Силами ПВО Минобороны уничтожены три беспилотника, летевших на Москву. Специалисты экстренных служб работают на месте падения обломков. 📲Сообщил Мэр Москвы

8 Aug 2026, 01:53 UTC49 viewsread 8 August 2026

Серпухов, Пущино, Ступино, Озёры, Коломна, Михнево, Чехов, Барыбино, Белые Столбы, Львовский, Климовск, Коледино(маркетплейс), Домодедово, Бронницы, Московская область - возможен налёт БПЛА. ❗️Радар Москва — @bpla777

8 Aug 2026, 01:52 UTC50 viewsread 8 August 2026

Московская область Тульская область Отбой ракетной опасности ❗️Радар Москва — @bpla777

8 Aug 2026, 01:52 UTC51 viewsread 8 August 2026

ГО Подольск Московская область Работа ПВО по БПЛА ❗️Радар Москва — @bpla777

8 Aug 2026, 01:49 UTC51 viewsread 8 August 2026

ГО Раменское Московская область Работа ПВО по БПЛА ❗️Радар Москва — @bpla777

8 Aug 2026, 01:43 UTC51 viewsread 8 August 2026

Павловский Посад, Электросталь, Ногинск, Балашиха, Реутов, Люберцы, Котельники, Московская область - внимание по возможным БПЛА от Владимирской области. ❗️Радар Москва — @bpla777

8 Aug 2026, 01:35 UTC52 viewsread 8 August 2026

ГО Серпухов Московская область Фиксация БПЛА ❗️Радар Москва — @bpla777

8 Aug 2026, 01:27 UTC52 viewsread 8 August 2026

Дубна, Клин, Солнечногорск, Поварово, Зеленоград, Истра, Волоколамск, Руза, Тучково, Звенигород, Кубинка, Архангельское, Красногорск, Химки, Долгопрудный, Чашниково, Можайск, Руза, Наро-Фоминск, Одинцово, Серпухов, Чехов, Подольск, Кашира, Ступино, Домодедово, Раменское, Серебряные пруды, Зарайск, Луховицы, Коломна, Воскресенск, Егорьевск, Шатура и близлежащие населённые пункты, Московская область - опасность по БПЛА…

8 Aug 2026, 01:11 UTC54 viewsread 8 August 2026

ГО Серебряные Пруды Московская область Фиксация группы БПЛА ❗️Радар Москва — @bpla777

8 Aug 2026, 00:53 UTC66 viewsread 8 August 2026

Серпуховский район, Чеховский район, Подольский район, Ступинский район, Раменский район, Кашарский район, Озёрский район, Коломенский район, Воскресенский район, Серебряно-Прудский район, Зарайский район, Луховицкий район, Наро-Фоминский район, Можайский район, Одинцовский район, Рузский район, Московская область - опасность по БПЛА + ракетная. ❗️Радар Москва — @bpla777

8 Aug 2026, 00:10 UTC73 viewsread 8 August 2026

Московская область Опасность по БПЛА ❗️Радар Москва — @bpla777

7 Aug 2026, 23:06 UTC99 viewsread 8 August 2026

Московская область Ракетная опасность ❗️Радар Москва — @bpla777

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

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

“Радар Москва | БПЛА, Ракеты, Авиация | Московская область” (@bpla777), 991 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/bpla777.

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.