Telegram RegisterThe public register of Telegram
Telegram profile photo for Копия

Channel

Копия

@radarcopyrusmy

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

2subscribers

+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-1003906568499
TypeChannel
Username@radarcopyrusmy
CreatedBetween 1 April 2026 and 6 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live16 September 2026
Measurements held2
On Telegramt.me/radarcopyrusmy

Growth

27 August 2026 — 2 subscribers14 August 2026 — 2 subscribers7 August 202614 August 2026
2 measurements spanning 6 days. 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 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 03:182no change
7 Aug 2026, 19:302first reading

Engagement

20 posts held, back to 6 July 2026the 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 6 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1
Videos
3
Links
1,670

Lifetime counters from Telegram’s own channel header, read 14 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.

Recent posts

6 Jul 2026, 23:22 UTC1 viewsread 14 August 2026

Задонский район Липецкая область Фиксация БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot

6 Jul 2026, 23:21 UTC1 viewsread 14 August 2026

Щекино Тульская область Работа ПВО по БПЛА Меры безопасности ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot

6 Jul 2026, 23:18 UTC1 viewsread 14 August 2026

Калуга Калужская область Фиксация БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot

6 Jul 2026, 23:18 UTC1 viewsread 14 August 2026

Урицкий район Шаблыкинский район Дмитровский район Орловская область Фиксации БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot

6 Jul 2026, 23:15 UTC1 viewsread 14 August 2026

Угранский район Вяземский район Смоленская область Фиксация БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot

6 Jul 2026, 23:15 UTC1 viewsread 14 August 2026

Кировский район Жиздринский район Людиновский район Мещовский район Калужская область Фиксации БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot

6 Jul 2026, 23:13 UTC1 viewsread 14 August 2026

Ленинский район Суворовский район Киреевский район Тепло-Огаревский район Каменский район Новомосковский район Тульская область Фиксации БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot

6 Jul 2026, 23:09 UTC1 viewsread 14 August 2026

МО Шатура Московская область Фиксация БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot

6 Jul 2026, 23:07 UTC1 viewsread 14 August 2026

МО Зарайск Московская область Фиксация БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot

6 Jul 2026, 23:06 UTC1 viewsread 14 August 2026

Саратовский район Саратовская область Фиксация от 2 БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot

6 Jul 2026, 23:03 UTC1 viewsread 14 August 2026

Орел Орловская область Фиксация БПЛА ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot

6 Jul 2026, 23:02 UTC1 viewsread 14 August 2026

Алексин Тульская область Работа ПВО по БПЛА Меры безопасности ❗️Радар по всей России - @radarrussiia 🌐 Обход белых списков - @Internet_Boost_bot

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

“Копия” (@radarcopyrusmy), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/radarcopyrusmy.

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.