Telegram RegisterThe public register of Telegram
Telegram profile photo for КУПОЛ РОССИИ

Channel

КУПОЛ РОССИИ

@kupolrussia

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

217,473subscribers

+3,962 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1002319552152
TypeChannel
Username@kupolrussia
DescriptionОтблагодарить админов https://pay.cloudtips.ru/p/991df385 Оперативное оповещение населения об угрозах атаки БПЛА, ракетами и авиационных опасностях. Наш чат бот - https://t.me/KupolRussiabot РКН: https://clck.ru/3QXVf7
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live19 September 2026
Measurements held36
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/kupolrussia

Topic

National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 59% 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

213,511217,473215,4926 August 2026 — 213,511 subscribers6 August 2026 — 213,511 subscribers6 August 2026 — 213,593 subscribers7 August 2026 — 213,675 subscribers8 August 2026 — 213,716 subscribers9 August 2026 — 213,796 subscribers10 August 2026 — 213,811 subscribers11 August 2026 — 213,953 subscribers12 August 2026 — 213,923 subscribers13 August 2026 — 213,951 subscribers14 August 2026 — 214,052 subscribers15 August 2026 — 214,220 subscribers17 August 2026 — 214,260 subscribers18 August 2026 — 214,503 subscribers19 August 2026 — 214,611 subscribers20 August 2026 — 214,810 subscribers21 August 2026 — 214,822 subscribers22 August 2026 — 214,860 subscribers24 August 2026 — 215,067 subscribers25 August 2026 — 215,022 subscribers26 August 2026 — 215,239 subscribers27 August 2026 — 215,500 subscribers28 August 2026 — 215,522 subscribers29 August 2026 — 215,559 subscribers30 August 2026 — 215,780 subscribers31 August 2026 — 215,888 subscribers1 September 2026 — 215,918 subscribers2 September 2026 — 215,940 subscribers3 September 2026 — 216,112 subscribers5 September 2026 — 216,124 subscribers9 September 2026 — 216,267 subscribers11 September 2026 — 217,156 subscribers13 September 2026 — 217,119 subscribers15 September 2026 — 217,320 subscribers17 September 2026 — 217,378 subscribers19 September 2026 — 217,473 subscribers6 August 202619 September 2026
36 measurements spanning 45 days, net +3,962. 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 212,917–218,067 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 36
Measured (UTC)SubscribersChange
19 Sept 2026, 16:58217,473+95
17 Sept 2026, 02:40217,378+58
15 Sept 2026, 05:38217,320+201
13 Sept 2026, 11:40217,119-37
11 Sept 2026, 17:58217,156+889
9 Sept 2026, 02:57216,267+143
5 Sept 2026, 20:40216,124+12
3 Sept 2026, 20:17216,112+172
2 Sept 2026, 10:56215,940+22
1 Sept 2026, 08:28215,918+30
31 Aug 2026, 07:38215,888+108
30 Aug 2026, 07:16215,780+221
29 Aug 2026, 09:53215,559+37
28 Aug 2026, 08:34215,522+22
27 Aug 2026, 10:12215,500+261
26 Aug 2026, 12:28215,239+217
25 Aug 2026, 15:23215,022-45
24 Aug 2026, 14:25215,067+207
22 Aug 2026, 18:34214,860+38
21 Aug 2026, 09:34214,822first reading

Engagement

2,078 posts held, back to 5 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 104 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.63%
avg views ÷ 217,473 subscribers
Avg views / post
3,540
1,180 posts measured
Reaction rate
0.269%
reactions ÷ views · ER floor
Posts in window
1,180
of 2,078 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. It is computed over the 1,158 of 1,180 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 25 September 2026
Posts held2,078 (5 August 2026 – 25 September 2026)
Views total4,173,208
Reactions total11,213
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken25 Sept 2026, 19:54 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
≈64,700
Videos
≈244
Links
≈1,230

Lifetime counters from Telegram’s own channel header, read 25 September 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
3s
Average length
1s

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

Reaction mix

9,558 reactions across 965 posts, in 12 distinct kinds. The most used accounts for 69.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬6,68469.9%
❤1,42514.9%
👍95610.0%
😱1521.59%
🤝820.858%
😭610.638%
😢600.628%
🤔570.596%
💯290.303%
👀230.241%
🫡160.167%
✍130.136%

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 980 of the 1,000 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 9,558 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 31 August 2026 to 25 September 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

25 Sept 2026, 19:52 UTC5 views0 reactionsread 25 September 2026

Приморск Бердянск Осипенко И близлежащие Тревога по БПЛА сохраняется Соблюдайте меры безопасности

25 Sept 2026, 19:49 UTC6 views11 reactionsread 25 September 2026

Клинцовский район Брянская область Тревога по БПЛА, повторно

🤬10👍1

25 Sept 2026, 19:48 UTC7 views9 reactionsread 25 September 2026

Брянск и близлежащие Тревога по БПЛА сохраняется Брянская область

🤬8👍1

25 Sept 2026, 19:45 UTC313 views10 reactionsread 25 September 2026
Photo

Рыково Геническ и близлежащие Херсонская область РФ

🤬9👍1

25 Sept 2026, 19:44 UTC616 views8 reactionsread 25 September 2026

Новоалексеевка Азовское и близлежащие Тревога по БПЛА Херсонская область РФ

🤬7👍1

25 Sept 2026, 19:41 UTC≈9,980 views17 reactionsread 25 September 2026

Калужская область Срочно принять меры безопасности Множественные фиксации

🤬14😢2🤝1

25 Sept 2026, 19:40 UTC≈1,220 views12 reactionsread 25 September 2026

Сокологорное и близлежащие Тревога по БПЛА Херсонская область РФ

🤬11👍1

25 Sept 2026, 19:40 UTC≈10,300 views19 reactionsread 25 September 2026
Photo

Смоленская область Московская область Тревога по БПЛА

🤬17👍2

25 Sept 2026, 19:39 UTC≈1,220 views11 reactionsread 25 September 2026
Photo

Ивот , Брянская область И далее на Калужскую область направление Людиново

🤬11

25 Sept 2026, 19:39 UTC≈1,220 views7 reactionsread 25 September 2026

Ивот , Брянская область тревога по БПЛА И далее на Калужскую область направление Людиново

🤬7

25 Sept 2026, 19:38 UTC≈1,220 views8 reactionsread 25 September 2026
Photo

Рыково Новогригоровка и близлежащие Херсонская область РФ

🤬8

25 Sept 2026, 19:38 UTC≈1,520 views5 reactionsread 25 September 2026
Photo

Донецк и близлежащие ДНР

🤬5

Showing the 12 most recent of 2,078 posts we hold for @kupolrussia. 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Lpr 1
@lpr1_treugolnik · 933,015
248 posts
LPR оповещения, тревоги, отмены режима тревог
@LPRalarm · 155,320
188 posts
Темы. Главное (ГлавМедиа)
@glavmedia · 66,576
25 posts
БПЛА по Приволжскому федеральному округу
@Kazan_BPLA_716 · 16,543
23 posts
Оновной
@osnvperes · 3
4 posts
Записки резидента
@zapiski_rezidenta · 1,190
4 posts
Краснодар, адыгея
@kkperes · 7
3 posts
Бариста Кунислав ☕️🚴🛴
@BaristaKunislav · 65
2 posts
🍀Волноваха инфо 🍀🍀VolnoVaha info🍀
@VolnoVaha_info_rus · 1,968
2 posts
🗞️Новости в авоське🗞️
@NewsinAvosk · 136
1 post
Радар Приволжского федерального округа
@Radarpf · 27,871
1 post
Приграничье
@atypicalday · 64,418
1 post
DM57🚨
@dm57orel · 2,762
1 post
Брянская область оповещения и тревоги
@lpr1_Bryansk_alarm · 44,186
1 post
Курская область оповещения и тревоги
@lpr1_Kursk_alarm · 25,249
1 post
Луганская Донецкая Народные Республики оповещения, тревоги
@lpr1_LDPR_alarm · 36,974
1 post
Ростовская область тревоги оповещения
@lpr1_Rostov_alarm · 52,183
1 post
Воронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,398
1 post
Небо Ростова | Новости, радар, тревоги, оповещения
@nebo_rostova · 33,564
1 post
Уголок шизы Рамиля
@podvalRamilka · 19
1 post
Просто ЖопА
@popafm · 11
1 post
Автограф Бердина
@sibirskiy_led_official · 154
1 post
ВОЛОГДАЧ
@vologdach_35 · 9
1 post
Volvo
@volvo_remont · 205
1 post

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

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

“КУПОЛ РОССИИ” (@kupolrussia), 217,473 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/kupolrussia.

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.