Telegram RegisterThe public register of Telegram
Telegram profile photo for 🚀 РАКЕТА UA | Тривога України

Channel

🚀 РАКЕТА UA | Тривога України

@war_raketaua

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

85,686subscribers

-4,800 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001663940683
TypeChannel
Username@war_raketaua
Description🚀 Моніторинг ворожої авіації та ракет Посилання - https://t.me/+qQV8wsZ5RkRhYmZi ❎ Канал не є офіційним джерелом, ми лише прагнемо максимально швидко та точно сповіщати населення
Created2 September 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held67
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/war_raketaua

Topic

International 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 20 August 2026 and assigned it the closest of 31 fixed categories, at 86% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 12 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@zsuwar/710785 Nov 2026, 12:41 UTC@war_raketaua/92541 · this entry5 Nov 2026, 12:47 UTC0.997 minutes
@zsuwar/700383 Sept 2026, 11:21 UTC@war_raketaua/90412 · this entry3 Sept 2026, 12:08 UTC0.9847 minutes
@zsuwar/7075817 Oct 2026, 15:37 UTC@war_raketaua/92025 · this entry17 Oct 2026, 23:48 UTC0.988.2 hours
@zsuwar/7075517 Oct 2026, 12:29 UTC@war_raketaua/92013 · this entry17 Oct 2026, 12:29 UTC0.98under a minute
@zsuwar/700433 Sept 2026, 19:00 UTC@war_raketaua/90426 · this entry3 Sept 2026, 19:01 UTC0.97under a minute
@zsuwar/710072 Nov 2026, 15:10 UTC@war_raketaua/92429 · this entry2 Nov 2026, 16:31 UTC0.9781 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@zsuwar63 (8/8 hand-verifiable sample passed)0.9820 minutes@zsuwar (63–0)
@monitorwarr59 (8/8 hand-verifiable sample passed)0.97under a minute@monitorwarr (58–1)
@monitor_ukr55 (8/8 hand-verifiable sample passed)0.95under a minutethis entry (40–15)
@war_monitor17 (8/8 hand-verifiable sample passed)0.962 minutes@war_monitor (15–2)
@radar_raketaa16 (8/8 hand-verifiable sample passed)0.9772 seconds@radar_raketaa (11–5)
@esvitlo_kyiv_oblast20 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (14–6)
@kuptg13 (8/8 hand-verifiable sample passed)0.9789 minutesthis entry (7–6)
@lachentyt13 (8/8 hand-verifiable sample passed)0.9672 seconds@lachentyt (12–1)
@dnipro_informator9 (8/8 hand-verifiable sample passed)0.972 minutes@dnipro_informator (6–3)
@esvitlo_kyiv_ua22 (8/8 hand-verifiable sample passed)1.00under a minute@esvitlo_kyiv_ua (14–8)
@xlozova8 (8/8 hand-verifiable sample passed)0.9775 minutesthis entry (8–0)
@kudy_letyt7 (7/7 hand-verifiable sample passed)0.975 days@kudy_letyt (7–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 208 of the 208 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 818 comparable posts for this entry, running 5 August 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

85,68690,48688,0866 August 202615 November 2026
67 measurements spanning 101 days, net -4,800. 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 84,966–91,206 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 67
Measured (UTC)SubscribersChange
15 Nov 2026, 17:1185,686-182
12 Nov 2026, 11:2185,868-97
10 Nov 2026, 07:4185,965-86
8 Nov 2026, 16:3986,051-58
7 Nov 2026, 07:1586,109-44
6 Nov 2026, 08:4586,153-65
5 Nov 2026, 05:2786,218-34
4 Nov 2026, 05:1186,252-40
3 Nov 2026, 06:0686,292-39
2 Nov 2026, 09:0986,331-54
1 Nov 2026, 11:2686,385-53
31 Oct 2026, 08:4086,438-48
30 Oct 2026, 10:1486,486-24
29 Oct 2026, 06:3886,510-36
28 Oct 2026, 02:2586,546-44
27 Oct 2026, 02:5886,590-50
26 Oct 2026, 02:4686,640-39
25 Oct 2026, 01:1886,679-45
23 Oct 2026, 22:4486,724-52
23 Oct 2026, 01:0786,776first reading

Engagement

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

ERR · 30 days
20.1%
avg views ÷ 85,686 subscribers
Avg views / post
17,300
695 posts measured
Reaction rate
0.866%
reactions ÷ views · ER floor
Posts in window
695
of 2,650 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 17 November 2026
Posts held2,650 (5 August 2026 – 17 November 2026)
Views total11,998,253
Reactions total103,851
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 07:19 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
≈6,020
Videos
≈3,140
Links
≈16,800

Lifetime counters from Telegram’s own channel header, read 17 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
13m 30s
Average length
20s

Measured directly from 41 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

151,028 reactions across 1,000 posts, in 41 distinct kinds. The most used accounts for 38.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬57,57438.1%
🙏44,26829.3%
🔥13,9429.23%
❤9,2996.16%
😭8,1095.37%
👍5,5313.66%
😢2,5441.68%
😡2,3161.53%
🤣2,0841.38%
😱1,0800.715%
😁8960.593%
👎7160.474%
🎉3190.211%
👀2770.183%
💔2460.163%
🥱2350.156%
🤯2250.149%
💯2000.132%
🕊1870.124%
🤪1850.122%
21 further kinds7950.526%

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 1,000 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 151,028 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 6 October 2026 to 17 November 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.

Telegram Stars

Stars received
22
across the posts below
Posts paid on
15
of 1,000 we hold a reading for · 2%
Most on one post
4
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @war_raketaua. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 6 October 2026 to 17 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 662 of 695 posts held from the last 30 days (95.3%) 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).

17 Nov 2026, 07:01 UTC≈5,910 views186 reactionsread 17 November 2026
Photo

Кримський міст, 2026 🚀@war_raketaua

❤101👍33🎉27🔥10🥱7👎4👌2🏆1

17 Nov 2026, 06:26 UTC≈11,500 views114 reactionsread 17 November 2026

‼️Крилата ракета в напрямку Полтави. 🚀@war_raketaua

🙏66🤬43😭3❤1🔥1

17 Nov 2026, 03:46 UTC≈19,600 views223 reactionsread 17 November 2026

❗️~20х ударних БпЛА повз Чернігівщину в напрямку Києва/області. 🚀@war_raketaua

🤬112🙏95❤9👍5👎1😭1

17 Nov 2026, 03:40 UTC≈20,200 views138 reactionsread 17 November 2026

💥Повідомляють про вибухи у Столиці. 🚀@war_raketaua

🙏72🤬44😭10❤8👎2👍1💯1

17 Nov 2026, 03:39 UTC≈20,000 views105 reactionsread 17 November 2026

‼️Балістика в напрямку Києва/околиць. 🚀@war_raketaua

🤬55🙏38❤4😡3😱2👍1👏1😭1

16 Nov 2026, 23:46 UTC≈20,800 views81 reactionsread 17 November 2026

⚠️ 8 БпЛА на Черінігвщині у бік Київщини, Вишгородський р-н. ⚠️ 2 БпЛА на Коростень з півночі. 🚀@war_raketaua

🤬39🙏29❤10😡3

16 Nov 2026, 23:27 UTC≈20,000 views60 reactionsread 17 November 2026

⚠️ 4 БпЛА на півночі Житомирщини західним курсом. ⚠️ 9 БпЛА перелітають з Чернігівщини на Київщину, Вишгородський р-н. ⚠️ 3 БпЛА над Білоруссю, рухаються вглиб Мозирського р-ну. ⚠️ 1 реактив на межі Дніпропетровщини та Кіровоградщини. 🚀@war_raketaua

🙏32🤬17❤9😡2

16 Nov 2026, 22:05 UTC≈19,600 views172 reactionsread 17 November 2026

💥 Вибухи у Харкові. Ще виходи на Харків! 🚀@war_raketaua

🙏109🤬55😡4😭4

16 Nov 2026, 22:01 UTC≈19,800 views155 reactionsread 17 November 2026

Вихід з Бєлгорода у бік Харкова. 🚀@war_raketaua

🙏78🤬70❤3😭2👎1😡1

16 Nov 2026, 21:58 UTC≈19,100 views131 reactionsread 17 November 2026

Мінус 🚀@war_raketaua

🙏112❤13👍5👌1

16 Nov 2026, 21:57 UTC≈18,600 views111 reactionsread 17 November 2026

❗️Далі на Смілу 🚀@war_raketaua

🤬61🙏46❤1👎1😡1😭1

16 Nov 2026, 21:56 UTC≈17,800 views108 reactionsread 17 November 2026

Балістика на Черкаси. 🚀@war_raketaua

🙏58🤬42😱5❤1👎1😡1

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

Posts recorded as deleted after publishing

We recorded 1 post on @war_raketaua as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
14 September 2026
Most recent seen missing
14 September 2026
Median time before seen missing
13 hours
Seen missing in the last 30 days
0

Forward network

Republished by

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

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 2 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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 938,170
#1
Лачен пише
@lachentyt · 1,576,100
#2
Труха⚡️Україна
@truexanewsua · 3,165,345
#3
monitor
@war_monitor · 958,023
#4
Де Ракета ?🚀 | Моніторинг
@deraketaua · 154,826
#5
Київ ІНФО | Новини Україна 🇺🇦
@kievinfo_kyiv · 1,261,551
#6
Дніпро Alerts 🚀 🚨
@dnipro_alerts · 809,443
#7
🔊⚠️єРадар | Повітряна тривога | Ракетна небезпека
@eRadarrua · 411,004
#8
Куди летить? | Тривога
@radar_raketaa · 490,712
#9
Вибухи та бавовна
@vybuhy_bavovna · 81,983
#10
Карта повітряних тривог 🇺🇦
@alarmua · 940,548
#11
🚀 Ракетна небезпека | України | шахеди | вибухи |
@vibuxaviasia · 56,554
#12
Киевский Движ
@k_dvizh · 470,624
#13
Україна Online: Новини | Політика
@UaOnlii · 1,536,697
#14
Чому тривога | Радар
@raketa_trevoga · 471,573
#15
Тривога України | Радар
@kiev_nebo · 539,280
#16
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 728,432
#17
НУ І ДНІПРО! 🇺🇦
@ny_i_dnipro · 289,947
#18
Радар⚡️Запоріжжя
@radar_zaporizhzhya · 88,544
#19
∆✙🍒Гнила черешня🇺🇦✙∆
@gnilayachereha · 412,798
#20
STERNENKO
@ssternenko · 879,121
#21
🔊Чому тривога?🚨| Повітряна тривога | Ракетна небезпека | єРадар |
@tryvoga_chomu · 271,642
#22
Тотальна Зрада
@totallzrada · 265,783
#23
✈️Стратегічна авіація ворога
@strategic_aviationRF · 189
#24
Strategic Control
@strategicontrol · 27,117
#25
ОПЕРАТИВНИЙ ІНФОРМ
@operinform · 135,692
#26
TLk News
@tlknewsua · 640,966
#27
Труха⚡️Дніпро | Новини
@truexadnepr · 399,271
#28
✙DeepState✙🇺🇦
@deepstateua · 750,207
#29
monitoring
@monitorwarr · 85,150
#30
Андрій Смолій
@smolii_ukraine · 523,723
#31
Київський купол | Графіки
@nebo_raketa · 542,733
#32
Хуйовий Харків 🇺🇦 Хуевый Харьков
@huyovy_kharkiv · 463,751
#33
Розвідка України
@Ukrainian_Intelligence · 66,242
#34
✈️Стратегічна авіація
@StrategicaviationT · 132,886
#35
ЦАПЛІЄНКО_UKRAINE FIGHTS
@Tsaplienko · 319,669
#36
ЗАПОРІЖЖЯ.ІНФО🍁
@info_zp · 191,930
#37
#SK# говорить🇺🇦
@SK_DM_SK · 191,904
#38
Труха⚡️Запоріжжя
@truexazaporozie · 284,647
#39
Український Наступ | #УкрТг ∆
@ukrnastup · 132,638
#40
Моніторинг UA | Тривоги 🚨
@raketna_nebespeka_truvoga · 28,264
#41
Ukraine NOW
@UkraineNow · 404,377
#42
ППО радар | Напрямок ракет | Напрямок шахедів |
@mon1tor_ua · 264,080
#43
Збройні Сили України. Війна з окупантами
@zsuwar · 108,947
#44
Тривога INFO ⚠️ Авіація рф
@avia_radar_info · 23,456
#45
Україна⚡️Новини⚡️
@uanova · 565,035
#46
Повітряна Тривога 🚀 Карта Київська
@ukrainar · 97,007
#47
Правий Берег Київ | Киев
@kiev_pravyy_bereg · 181,285
#48
Tracking
@the_first_online · 8,054
#49
Реальний Київ | Украина
@kievreal1 · 1,550,018
#50
INSIDER UA | Україна | Новини
@insiderukr · 2,141,667
#51
Всевидящее ОКО (миллион подписчиков)
@oko_ua · 1,751
#52
Реальна Війна | Україна | Новини
@voynareal · 1,541,547
#53
Труха⚡️Київ
@truexakyiv · 972,266
#54
✙ 🔼Вертикаль
@vert2026 · 113,508
#55
УС: Україна, новини, політика, війна
@u_now · 1,403,118
#56
ХДніпро 🇺🇦
@hyevuy_dnepr · 520,852
#57
Бавовна
@ukrbavovna · 800,178
#58
Батальйон Монако
@batalionmonako · 982
#59
Скринька Пандори
@pandoras_box_ua · 157,764
#60
Левый Берег Киев
@kiev_levyy_bereg · 492,701
#61
Говорять Снайпер ꑭ
@stanislav_osman · 287,183
#62
ТСН новини / ТСН.ua
@tch_channel · 729,418
#63
Оперативний ЗСУ
@operativnoZSU · 359,722
#64
✙ Київ Оперативний | Kyiv Operative ✙
@kyivoperat · 337,929
#65
Дніпро Оперативний 🇺🇦| Війна
@dnepr_operativ · 312,948
#66
Всевидящее ОКО 18 ✙
@oko18_ukr · 315,880
#67
КМДА – офіційний канал
@KyivCityOfficial · 403,658
#68
Бахмутський Демон 👹
@bahshiddemon · 169,645
#69
Включатель Днепр⚡️
@vklyuchatel_dnepr_svet · 197,131
#70
Хуевая Одесса
@xydessa · 943,764
#71
Харьков life | Харків 🇺🇦
@kharkivlife · 666,407
#72
Это Запорожье 🇺🇦 Новости
@eto_zp · 174,523
#73
Дніпро ОПЕРАТИВНИЙ 🇺🇦
@dneproperatyv · 189,195
#74
Телеграмна служба новин - Україна
@tgsn_ua · 1,108,673
#75
Одесса INFO ⚓️ 🇺🇦 Новости | Одеса
@odessa_infonews · 989,908
#76
NEXTA Live
@nexta_live · 765,456
#77
Захід Головне
@zahid_golovne_ua · 609,899
#78
Офіцер
@officer_33 · 179,267
#79
🟢 Київ Новини | Live 24/7
@kyiv_novyny_24 · 237,542
#80
УНИАН - новости Украины | война с Россией | новини України | війна з Росією | УНІАН
@uniannet · 700,473
#81
Новости Одесса | Одеса
@our_odessa · 436,921
#82
‼️СИРЕНА. ДНІПРО‼️
@sirena_dp · 242,739
#83
AviMonitor
@avimonitor · 2,922
#84
єСвітло💡Київ | Світло
@esvitlo_kyiv_ua · 167,857
#85
Вмикач Київ | Світло💡
@kiev_svet · 235,748
#86
Київ News | Світло
@svitlo_kiyv · 150,091
#87

Read from Telegram’s recommendation API, most recently 17 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Моніторинг UA | Тривоги 🚨
@raketna_nebespeka_truvoga · 28,264
Telegram ranks this channel #4 of 78 here — alongside 77 others — read 9 September 2026
Де Ракета ?🚀 | Моніторинг
@deraketaua · 154,826
Telegram ranks this channel #5 of 81 here — alongside 80 others — read 12 August 2026
🚀 Ракетна небезпека | України | шахеди | вибухи |
@vibuxaviasia · 56,554
Telegram ranks this channel #9 of 87 here — alongside 86 others — read 22 August 2026
Вибухи та бавовна
@vybuhy_bavovna · 81,983
Telegram ranks this channel #10 of 86 here — alongside 85 others — read 18 August 2026
💥ОБЕРЕЖНО ВИБУХИ l НОВИНИ l РАДАР | СВІТЛО
@oberezhnovibuhi · 27,852
Telegram ranks this channel #14 of 80 here — alongside 79 others — read 9 September 2026
НАШЕ ППО 🇺🇦 | Радар ракет, шахедів
@nashe_ppo_monitoring · 42,920
Telegram ranks this channel #21 of 86 here — alongside 85 others — read 28 August 2026
Радар ППО🚀| Карта тривог
@raketa_rakety_de · 51,075
Telegram ranks this channel #21 of 78 here — alongside 77 others — read 24 August 2026
Радар⚡️Запоріжжя
@radar_zaporizhzhya · 88,544
Telegram ranks this channel #22 of 83 here — alongside 82 others — read 16 August 2026
Дніпро Радар | Тривога
@dnipro_alertsx · 53,281
Telegram ranks this channel #23 of 58 here — alongside 57 others — read 11 September 2026
Тривога INFO ⚠️ Авіація рф
@avia_radar_info · 23,456
Telegram ranks this channel #24 of 86 here — alongside 85 others — read 17 September 2026
Ветеран Доповідає
@veteran_dopoviday · 113,730
Telegram ranks this channel #24 of 83 here — alongside 82 others — read 13 August 2026
ППО РАДАР 🇺🇦 | Карта тривог | Моніторинг
@PpoUaRadar · 27,374
Telegram ranks this channel #26 of 81 here — alongside 80 others — read 9 September 2026
Куди летить? | Тривога
@radar_raketaa · 490,712
Telegram ranks this channel #26 of 86 here — alongside 85 others — read 9 August 2026
Україна тут | Новини
@UkrainaTut1 · 48,993
Telegram ranks this channel #27 of 82 here — alongside 81 others — read 11 September 2026
🔊Чому тривога?🚨| Повітряна тривога | Ракетна небезпека | єРадар |
@tryvoga_chomu · 271,642
Telegram ranks this channel #27 of 86 here — alongside 85 others — read 10 August 2026
‼️РАКЕТНА НЕБЕЗПЕКА ЛЬВІВ🚀⛔️
@RAKETNANEBESPEKA · 46,858
Telegram ranks this channel #28 of 77 here — alongside 76 others — read 27 August 2026
Повітряна Тривога 🚀 Карта Київська
@ukrainar · 97,007
Telegram ranks this channel #29 of 87 here — alongside 86 others — read 19 August 2026
Де ракета Тривога
@trivoga6 · 36,562
Telegram ranks this channel #30 of 80 here — alongside 79 others — read 31 August 2026
Моніторинг Київ | Аналітика
@kyiv_m0nitoring · 112,572
Telegram ranks this channel #30 of 84 here — alongside 83 others — read 16 August 2026
Ракети
@ua_rockets · 71,776
Telegram ranks this channel #32 of 81 here — alongside 80 others — read 21 August 2026
‼️‼️‼️ Повітряна тривога Павлоград🚨‼️‼️
@pavlogradsirena · 26,529
Telegram ranks this channel #33 of 56 here — alongside 55 others — read 13 September 2026
🇺🇦НАШЕ ППО 🚀Де Ракета|Де Шахед📡
@Nashee_PPO · 33,202
Telegram ranks this channel #33 of 78 here — alongside 77 others — read 3 September 2026
Тривога України | Радар
@kiev_nebo · 539,280
Telegram ranks this channel #34 of 86 here — alongside 85 others — read 14 August 2026
Важливе Умань | Уманщина
@VazhlyveUman · 30,763
Telegram ranks this channel #35 of 73 here — alongside 72 others — read 11 September 2026

This channel appears in 96 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“🚀 РАКЕТА UA | Тривога України” (@war_raketaua), 85,686 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/war_raketaua.

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.