Неклиновский район Ростовская область Опасность по БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot
Channel
Радар по всей России (Копия @radarrusmy)
@radarrusmycopy
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
3subscribers
+0 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 | -1003995147674 |
|---|---|
| Type | Channel |
| Username | @radarrusmycopy |
| Created | Between 1 April 2026 and 4 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/radarrusmycopy |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 16:17 | 3 | no change |
| 7 Aug 2026, 19:28 | 3 | first reading |
Engagement
20 posts held, back to 4 June 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 pageof 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 4 June 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- ≈3
- Videos
- ≈3
- Links
- ≈1,010
Lifetime counters from Telegram’s own channel header, read 13 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
- 10s
- Average length
- 10s
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
Острогожский район Лискинский район Воронежская область Опасность по БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot
Матвеево-Курганский район Ростовская область Опасность по БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot
Воронежская область Тревога по БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot
Саратовская область Тамбовская область Пензенская область Внимание по БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot
Липецкая область Опасность по БПЛА от Курской области ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot
Воронежская область Ростовская область Опасность по БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot
Курская область Тревога по БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot
Калужская область Смоленская область Опасность по БПЛА от Брянской области ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot
Курская область Опасность по БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot
Брянская область Орловская область Опасность по БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot
С 08:00 до 20:00 силами противоздушной обороны было уничтожено 19 БПЛА над территориями Белгородской, Брянской, Курской областей, Республики Крым и над акваторией Черного моря ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot
Showing the 12 most recent of 20 posts we hold for @radarrusmycopy. 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
Names
Channels on the register whose handles appear in this channel's posts.
@Internet_Boost_bot · 47,53318 postsРадар по всей России | БПЛА
@radarrussiia · 1,453,04418 postsSkiskimasssk
@abknlive · 71 post🚧ДТП АРХАНГЕЛЬСКА🚧
@arhangelsklive · 131 postAstrakhan.live Лайк
@Astrakhanlive · 81 postБарнаул лайв
@barnaullive · 1061 postИркутск live
@irkutsklive · 271 postКалининград | все обо всем 🌆
@kaliningradLive · 621 postKazan
@kazanlive · 181 postАндрей Савельев
@razvitie · 7211 postВладимир.Live
@vladilive · 14,2921 post
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Радар по всей России (Копия @radarrusmy)” (@radarrusmycopy), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/radarrusmycopy.
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.