Telegram RegisterThe public register of Telegram
Telegram profile photo for Повітряна Тривога

Channel

Повітряна Тривога

@air_alert_ua

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry

225,185subscribers

-25,470 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-1001766138888
TypeChannel
Username@air_alert_ua
DescriptionОфіційний канал, що інформує про повітряну тривогу в будь-якому регіоні України. Інформація надається органами виконавчої влади України. Радимо також встановити застосунок «Повітряна тривога», щоб не пропустити важливі оповіщення.
Created14 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live17 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/air_alert_ua

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 88% 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 1 other registered channel. 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
@air_alert_ua/320767 · this entry8 Aug 2026, 06:06 UTC@NikopolOperativniy/503978 Aug 2026, 06:06 UTC1.00under a minute
@air_alert_ua/321458 · this entry9 Aug 2026, 06:03 UTC@NikopolOperativniy/504389 Aug 2026, 06:04 UTC1.00under a minute
@air_alert_ua/322132 · this entry10 Aug 2026, 06:22 UTC@NikopolOperativniy/5046910 Aug 2026, 06:22 UTC1.00under a minute
@air_alert_ua/324041 · this entry13 Aug 2026, 05:18 UTC@NikopolOperativniy/5063913 Aug 2026, 05:18 UTC1.00under a minute
@air_alert_ua/326862 · this entry18 Aug 2026, 09:11 UTC@NikopolOperativniy/5088618 Aug 2026, 09:12 UTC1.00under a minute
@air_alert_ua/327437 · this entry19 Aug 2026, 09:41 UTC@NikopolOperativniy/5091019 Aug 2026, 09:43 UTC1.002 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
@NikopolOperativniy17 (8/8 hand-verifiable sample passed)0.983 daysthis entry (11–6)

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. 6 of the 6 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 284 comparable posts for this entry, running 7 August 2026 to 13 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 key clone_mutual, last confirmed 14 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

225,185250,655237,9206 August 202617 November 2026
66 measurements spanning 103 days, net -25,470. 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 221,365–254,476 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
17 Nov 2026, 10:10225,185-830
14 Nov 2026, 00:56226,015-743
11 Nov 2026, 07:41226,758-432
9 Nov 2026, 12:35227,190-369
8 Nov 2026, 07:08227,559-352
7 Nov 2026, 01:38227,911-538
6 Nov 2026, 02:35228,449-261
5 Nov 2026, 04:28228,710-401
4 Nov 2026, 00:46229,111-421
3 Nov 2026, 03:30229,532+124
2 Nov 2026, 06:44229,408+118
1 Nov 2026, 05:31229,290-172
31 Oct 2026, 03:29229,462-215
30 Oct 2026, 02:38229,677-175
29 Oct 2026, 04:17229,852-193
28 Oct 2026, 02:40230,045-203
26 Oct 2026, 22:56230,248-237
25 Oct 2026, 20:18230,485-232
24 Oct 2026, 22:15230,717-232
23 Oct 2026, 22:34230,949first reading

Engagement

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

ERR · 30 days
70.9%
avg views ÷ 225,185 subscribers
Avg views / post
160,000
6 posts measured
Reaction rate
0.635%
reactions ÷ views · ER floor
Posts in window
7
of 1,207 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 13 November 2026
Posts held1,207 (6 August 2026 – 13 November 2026)
Views total957,800
Reactions total6,085
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 14:29 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
5
Videos
1
Links
35

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. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

20,223 reactions across 945 posts, in 36 distinct kinds. The most used accounts for 44.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏8,93344.2%
🤬4,12220.4%
👍4,02919.9%
❤9854.87%
🕊3411.69%
🤔3321.64%
🫡2491.23%
👎2331.15%
🤡1490.737%
🤯1030.509%
😱1020.504%
👌980.485%
😢750.371%
😭730.361%
👀550.272%
🖕460.227%
🤝410.203%
😐400.198%
👻320.158%
😨290.143%
16 further kinds1560.771%

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 963 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 20,223 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 9 August 2026 to 13 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
38
across the posts below
Posts paid on
8
of 999 we hold a reading for · 0.8%
Most on one post
11
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @air_alert_ua. 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 9 August 2026 to 13 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: 1 of 7 posts held from the last 30 days (14.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).

13 Nov 2026, 11:38 UTC≈62,400 views734 reactionsread 17 November 2026

Застосунок «Повітряна тривога» повністю відновив роботу: на карті знову доступний рух цілей У застосунку «Повітряна тривога» повністю відновлено всі функції після несанкціонованого доступу до інтерфейсу оператора. Відтепер орієнтовний рух повітряних цілей знову відображається на карті. Команда розробників Ajax Systems і Stfalcon спільно з Міністерством цифрової трансформації України провели аудит безпеки та посили…

❤485👎133👍69🤣23🤬18🗿5🕊1

13 Nov 2026, 11:38 UTC≈46,800 views158 reactionsread 17 November 2026
Photo

Photo, posted without a caption

❤125👏14🤔11🏆4👎4

6 Nov 2026, 07:59 UTC≈94,600 views498 reactionsread 17 November 2026

Чому застосунок «Повітряна тривога» на iPhone займає близько 500 МБ? І чи є там віруси? Останнім часом у мережі поширюють дописи про те, що версія застосунку «Повітряна тривога» для iPhone займає значно більше місця, ніж версія для Android, а отже, нібито містить віруси. Це неправда. Різниця в розмірі пояснюється особливостями роботи операційної системи iOS та зберігання звукових файлів. Пояснюємо простими словами…

❤371👍70👌16👎11🙏8🤯6🗿5🤬5

3 Nov 2026, 18:30 UTCviews —

Повітряна Тривога pinned «Трохи видихнули і розгреблись з технічними питаннями, тому хочемо пояснити, що сталось в неділю ввечері з застосунком «Повітряна тривога». Перш за все, від усієї команди розробників хочемо попросити вибачення перед мільйонами українців, які користуються цим…»

3 Nov 2026, 18:30 UTC≈132,000 views1,479 reactions10 Starsread 17 November 2026

Трохи видихнули і розгреблись з технічними питаннями, тому хочемо пояснити, що сталось в неділю ввечері з застосунком «Повітряна тривога». Перш за все, від усієї команди розробників хочемо попросити вибачення перед мільйонами українців, які користуються цим застосунком. По-друге, враховуючи купу обговорень в соціальних мережах і анонімних телеграм-каналах, хочемо зупинитись на фактах і розвінчати деякі міфи. 1.⁠ ⁠…

👍1,180🫡141🙏61🕊26🤝21🤔12🤬12🎃11

1 Nov 2026, 23:52 UTC≈121,000 views1,459 reactions3 Starsread 17 November 2026

Поступово повертаємо в роботу застосунок «Повітряна тривога» після кібератаки. Наразі на карті доступна інформація про жовтий і червоний рівні небезпеки (дронова і масована дронова/ракетна відповідно). Також приходять push-сповіщення про тривоги. Тимчасово призупинено відображення цілей на карті. Команда реалізує додаткові активності для захисту застосунку, щоб запобігти подібним ситуаціям у майбутньому. Ще раз а…

👍972🙏374🤡38🤝20👌15🤬11😭10🫡6

1 Nov 2026, 22:17 UTC≈501,000 views1,757 reactions9 Starsread 17 November 2026

Сьогодні сторонні особи здійснили несанкціоноване втручання в роботу застосунку. Ми відключили пуш-сповіщення та тимчасово призупинили роботу застосунку. Застосунок не зберігає персональних даних, тож загрози для користувачів немає. Просимо в жодному разі не переходити за посиланнями з підозрілих сповіщень. Команда працює над відновленням роботи застосунку. Приносимо свої вибачення.

👍1,060🙏348🫡102🤔64🤡60😭36💔27👌21

7 Sept 2026, 06:09 UTC≈258,000 views669 reactions11 Starsread 17 November 2026

🔴 09:09 Повітряна тривога в Шосткинський район Слідкуйте за подальшими повідомленнями. #Шосткинський_район

🙏273🤬111🤔92🤯37👀32🥱26👎24😢24

7 Sept 2026, 06:08 UTC≈259,000 views279 reactions1 Starread 17 November 2026

🔴 09:08 Повітряна тривога в Лозівський район Слідкуйте за подальшими повідомленнями. #Лозівський_район

🙏120🤬55👌18🤯16👍15👎13👻12😐11

7 Sept 2026, 06:08 UTC≈254,000 views183 reactions1 Starread 17 November 2026

🔴 09:08 Повітряна тривога в Ізюмський район Слідкуйте за подальшими повідомленнями. #Ізюмський_район

🙏91🤬45🤯13🤔12😱10👌8👎2👏1

7 Sept 2026, 06:01 UTC≈235,000 views138 reactions2 Starsread 17 November 2026

🔴🔴 09:01 Загроза ударних БпЛА в м. Запоріжжя та Запорізька територіальна громада! Увага! Підвищений рівень небезпеки! Пройдіть у найближче укриття #м_Запоріжжя_та_Запорізька_територіальна_громада

🙏67🤬43👎9🤡7👍6👌2😭2❤1

7 Sept 2026, 05:59 UTC≈199,000 views82 reactionsread 17 November 2026

🔴 08:59 Повітряна тривога в Кам’янський район Слідкуйте за подальшими повідомленнями. #Камянський_район

🙏51🤬25🤡3😱2👍1

Showing the 12 most recent of 1,207 posts we hold for @air_alert_ua. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

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 10 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
monitor
@war_monitor · 956,914
#2
Лачен пише
@lachentyt · 1,576,100
#3
Реальний Київ | Украина
@kievreal1 · 1,550,018
#4
Труха⚡️Україна
@truexanewsua · 3,165,345
#5
Київ ІНФО | Новини Україна 🇺🇦
@kievinfo_kyiv · 1,261,551
#6
INSIDER UA | Україна | Новини
@insiderukr · 2,141,667
#7
Чому тривога | Радар
@raketa_trevoga · 471,573
#8
Карта повітряних тривог 🇺🇦
@alarmua · 940,548
#9
Всевидящее ОКО (миллион подписчиков)
@oko_ua · 1,751
#10
Труха⚡️Київ
@truexakyiv · 972,266
#11
Реальна Війна | Україна | Новини
@voynareal · 1,541,547
#12
🔊⚠️єРадар | Повітряна тривога | Ракетна небезпека
@eRadarrua · 411,004
#13
Куди летить? | Тривога
@radar_raketaa · 490,712
#14
ТСН новини / ТСН.ua
@tch_channel · 729,418
#15
🔊Чому тривога?🚨| Повітряна тривога | Ракетна небезпека | єРадар |
@tryvoga_chomu · 271,642
#16
Україна Online: Новини | Політика
@UaOnlii · 1,536,697
#17
Ukraine NOW
@UkraineNow · 404,377
#18
Киевский Движ
@k_dvizh · 470,624
#19
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 728,432
#20
✙DeepState✙🇺🇦
@deepstateua · 750,207
#21
УС: Україна, новини, політика, війна
@u_now · 1,403,118
#22
Вмикач Київ | Світло💡
@kiev_svet · 235,748
#23
Левый Берег Киев
@kiev_levyy_bereg · 492,701
#24
Оперативний ЗСУ
@operativnoZSU · 359,722
#25
Говорять Снайпер ꑭ
@stanislav_osman · 287,183
#26
Тотальна Зрада
@totallzrada · 265,783
#27
Український Наступ | #УкрТг ∆
@ukrnastup · 132,638
#28
monitoring
@monitorwarr · 85,150
#29
КМДА – офіційний канал
@KyivCityOfficial · 403,658
#30
🚀 РАКЕТНА неБЕЗПЕКА 🚀
@rocket_danger_lviv · 398,152
#31
✙ Київ Оперативний | Kyiv Operative ✙
@kyivoperat · 337,929
#32
Дніпро Alerts 🚀 🚨
@dnipro_alerts · 809,443
#33
ОПЕРАТИВНИЙ ІНФОРМ
@operinform · 135,692
#34
Zelenskiy / Official
@v_zelenskiy_official · 665,469
#35
Львівич | Новини
@lvivych_news · 457,994
#36
Хуйовий Харків 🇺🇦 Хуевый Харьков
@huyovy_kharkiv · 463,751
#37
✙ Перша приватна мемарня
@privatnamemarnya · 115,209
#38
Одесса INFO ⚓️ 🇺🇦 Новости | Одеса
@odessa_infonews · 989,908
#39
Андрій Смолій
@smolii_ukraine · 523,723
#40
Захід Головне
@zahid_golovne_ua · 609,899
#41
єСвітло💡Київ | Світло
@esvitlo_kyiv_ua · 167,857
#42
ДТЕК - офіційний канал
@dtek_ua · 446,799
#43
Телеграмна служба новин - Україна
@tgsn_ua · 1,108,673
#44
Укренерго
@Ukrenergo · 100,021
#45
ХДніпро 🇺🇦
@hyevuy_dnepr · 520,852
#46
ЦАПЛІЄНКО_UKRAINE FIGHTS
@Tsaplienko · 319,669
#47
XYDESSA LIVE
@xydessa_live · 583,900
#48
Київ News | Світло
@svitlo_kiyv · 150,091
#49
Лебидло
@lebigaa · 416,923
#50
Київський купол | Графіки
@nebo_raketa · 542,733
#51
УНИАН - новости Украины | война с Россией | новини України | війна з Росією | УНІАН
@uniannet · 700,473
#52
Харьков life | Харків 🇺🇦
@kharkivlife · 666,407
#53
Vitalii KIM | Official
@VitaliiKimOfficial · 250,936
#54
Віталій Кличко
@vitaliy_klitschko · 194,843
#55
Новости Одесса | Одеса
@our_odessa · 436,921
#56
🟢 Київ Новини | Live 24/7
@kyiv_novyny_24 · 237,542
#57
Українська правда
@ukrpravda_news · 204,110
#58
Андрій Єрмак 🇺🇦
@ermaka2022 · 79,747
#59
Де Ракета ?🚀 | Моніторинг
@deraketaua · 154,826
#60
ЧОРНИЙ ЛИСТ
@blacknews_ukr · 190,724
#61
Хмельницький LIVE
@khmlv · 298,996
#62
Регіоналіті
@regionality · 100,624
#63
КМВА (Київська міська військова адміністрація)
@VA_Kyiv · 54,525
#64
🚀 РАКЕТА UA | Тривога України
@war_raketaua · 85,686
#65
ГОНЧАРЕНКО
@oleksiihoncharenko · 208,987
#66
БЕЗПЕЧНИЙ РЕГІОН
@bezpechniyregion · 163,283
#67
Николаевский Ванёк
@vanek_nikolaev · 2,571,456
#68
STERNENKO
@ssternenko · 879,121
#69
Бавовна
@ukrbavovna · 800,178
#70
Скринька Пандори
@pandoras_box_ua · 157,764
#71
✙ 🔼Вертикаль
@vert2026 · 113,508
#72
ОГо!
@OGoMono · 635,159
#73
Хуевая Одесса
@xydessa · 943,764
#74
Батальйон Монако
@batalionmonako · 982
#75
Новинач
@novinach · 142,158
#76
∆✙🍒Гнила черешня🇺🇦✙∆
@gnilayachereha · 412,798
#77
NEXTA Live
@nexta_live · 765,456
#78
СУСПІЛЬНЕ НОВИНИ
@suspilnenews · 262,481
#79
Всевидящее ОКО 18 ✙
@oko18_ukr · 315,880
#80
Бахмутський Демон 👹
@bahshiddemon · 169,645
#81
ҐРУНТ
@gruntmedia · 147,873
#82
Tracking
@the_first_online · 8,054
#83
Беларускі Гаюн | Belarusian Hajun project
@Hajun_BY · 221,648
#84
Бро скинув мем
@bromeeems · 310,153
#85
Вестник Шевцова
@jolynews · 206,371
#86

Read from Telegram’s recommendation API, most recently 10 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.

Оповіщення ЦЗ
@dczloda · 344,412
Telegram ranks this channel #2 of 87 here — alongside 86 others — read 10 August 2026
❗️СИРЕНА КІРОВОГРАДЩИНА🔊
@surenakrop · 52,652
Telegram ranks this channel #6 of 60 here — alongside 59 others — read 24 August 2026
🚀 РАКЕТНА неБЕЗПЕКА 🚀
@rocket_danger_lviv · 398,152
Telegram ranks this channel #11 of 82 here — alongside 81 others — read 10 August 2026
Чому тривога | Радар
@raketa_trevoga · 471,573
Telegram ranks this channel #11 of 85 here — alongside 84 others — read 9 August 2026
‼️РАКЕТНА НЕБЕЗПЕКА ЛЬВІВ🚀⛔️
@RAKETNANEBESPEKA · 46,858
Telegram ranks this channel #12 of 77 here — alongside 76 others — read 27 August 2026
Кропивницький Ваньок
@krop_vanek · 89,510
Telegram ranks this channel #12 of 62 here — alongside 61 others — read 21 August 2026
🔊Чому тривога?🚨| Повітряна тривога | Ракетна небезпека | єРадар |
@tryvoga_chomu · 271,642
Telegram ranks this channel #12 of 86 here — alongside 85 others — read 10 August 2026
Ерудит 🇺🇦 Цікаві Опитування.
@UkrErudyt · 56,420
Telegram ranks this channel #13 of 80 here — alongside 79 others — read 24 August 2026
ЧОРНИЙ ЛИСТ
@blacknews_ukr · 190,724
Telegram ranks this channel #15 of 86 here — alongside 85 others — read 11 August 2026
Ужгород LIVE | Закарпаття
@uzhlive · 46,265
Telegram ranks this channel #18 of 78 here — alongside 77 others — read 27 August 2026
Київ News | Світло
@svitlo_kiyv · 150,091
Telegram ranks this channel #18 of 79 here — alongside 78 others — read 13 August 2026
єСвітло💡Київ | Світло
@esvitlo_kyiv_ua · 167,857
Telegram ranks this channel #19 of 78 here — alongside 77 others — read 12 August 2026
Вознесенський Вісник
@vozvisnyk · 57,514
Telegram ranks this channel #20 of 83 here — alongside 82 others — read 23 August 2026
Де Ракета ?🚀 | Моніторинг
@deraketaua · 154,826
Telegram ranks this channel #20 of 81 here — alongside 80 others — read 12 August 2026
Захід 24/7 | Моніторинг 📡
@zahid_24_7 · 74,049
Telegram ranks this channel #21 of 83 here — alongside 82 others — read 23 August 2026
Рівне Головне
@rivne_golovne · 262,522
Telegram ranks this channel #21 of 83 here — alongside 82 others — read 11 August 2026
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 728,432
Telegram ranks this channel #22 of 85 here — alongside 84 others — read 8 August 2026
Суспільне Полтава
@suspilnepoltava · 55,916
Telegram ranks this channel #23 of 90 here — alongside 89 others — read 23 August 2026
Чисте небо Київська область та Київ.
@chyste_nebo · 273,138
Telegram ranks this channel #24 of 83 here — alongside 82 others — read 14 August 2026
Куди летить? | Тривога
@radar_raketaa · 490,712
Telegram ranks this channel #24 of 86 here — alongside 85 others — read 9 August 2026
Укренерго
@Ukrenergo · 100,021
Telegram ranks this channel #25 of 91 here — alongside 90 others — read 15 August 2026
ППО радар | Напрямок ракет | Напрямок шахедів |
@mon1tor_ua · 264,080
Telegram ranks this channel #25 of 90 here — alongside 89 others — read 14 August 2026
Реальний Хмельницький | Новини
@khmelnytskyi_real · 183,828
Telegram ranks this channel #25 of 77 here — alongside 76 others — read 12 August 2026
Типовий Львів
@lvivtp · 234,243
Telegram ranks this channel #25 of 88 here — alongside 87 others — read 11 August 2026

This channel appears in 137 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.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Alerts.in.ua (uk.wikipedia.org)
“…[https://t.me/s/air_alert_ua «Повітряна тривога»] від [[Ajax Systems]], що повідомляє про повітряні тривоги та інші загрози. * API застосунку [https://t.me/s/air_alert_ua…”
read 1 November 2026

Hacker News

This handle was named once in a Hacker News comment or story, via the public Algolia search API. HN comment and story text has no confirmed reuse licence, so nothing quoted from either is reproduced here — only that a mention exists, when, and by whom, with a link to read it at the source.

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

“Повітряна Тривога” (@air_alert_ua), 225,185 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/air_alert_ua.

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.