Telegram RegisterThe public register of Telegram
Telegram profile photo for Повітряний простір | Напрямок ракет

Channel

Повітряний простір | Напрямок ракет

@ukraine_pyxx

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

195,032subscribers

+9,120 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002133315828
TypeChannel
Username@ukraine_pyxx
DescriptionОперативна інформація про стратегічну авіацію, ударні БпЛА та рух ракет. ❗️Рекламу не продаєм ❗️ Для зв'язку в тому числі якщо видали бан у чаті: @ukraine_zvyazok_bot
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held31
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/ukraine_pyxx

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 8 August 2026 and assigned it the closest of 31 fixed categories, at 76% 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

185,912195,032190,4727 August 2026 — 185,912 subscribers7 August 2026 — 185,912 subscribers8 August 2026 — 186,057 subscribers9 August 2026 — 186,264 subscribers10 August 2026 — 186,739 subscribers11 August 2026 — 187,017 subscribers12 August 2026 — 187,236 subscribers13 August 2026 — 187,399 subscribers14 August 2026 — 187,598 subscribers16 August 2026 — 187,846 subscribers17 August 2026 — 187,983 subscribers18 August 2026 — 188,220 subscribers19 August 2026 — 188,467 subscribers20 August 2026 — 189,121 subscribers22 August 2026 — 189,247 subscribers23 August 2026 — 189,481 subscribers25 August 2026 — 189,769 subscribers26 August 2026 — 189,842 subscribers27 August 2026 — 190,034 subscribers28 August 2026 — 190,212 subscribers29 August 2026 — 190,397 subscribers30 August 2026 — 190,699 subscribers31 August 2026 — 190,869 subscribers1 September 2026 — 191,104 subscribers2 September 2026 — 191,386 subscribers3 September 2026 — 191,914 subscribers6 September 2026 — 192,239 subscribers9 September 2026 — 192,833 subscribers11 September 2026 — 193,739 subscribers14 September 2026 — 194,680 subscribers17 September 2026 — 195,032 subscribers7 August 202617 September 2026
31 measurements spanning 41 days, net +9,120. 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 184,544–196,400 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)SubscribersChange
17 Sept 2026, 11:19195,032+352
14 Sept 2026, 10:58194,680+941
11 Sept 2026, 21:01193,739+906
9 Sept 2026, 11:01192,833+594
6 Sept 2026, 06:38192,239+325
3 Sept 2026, 21:22191,914+528
2 Sept 2026, 12:37191,386+282
1 Sept 2026, 12:18191,104+235
31 Aug 2026, 09:06190,869+170
30 Aug 2026, 12:05190,699+302
29 Aug 2026, 10:11190,397+185
28 Aug 2026, 11:28190,212+178
27 Aug 2026, 02:35190,034+192
26 Aug 2026, 05:42189,842+73
25 Aug 2026, 02:34189,769+288
23 Aug 2026, 19:44189,481+234
22 Aug 2026, 01:49189,247+126
20 Aug 2026, 19:35189,121+654
19 Aug 2026, 18:35188,467+247
18 Aug 2026, 17:27188,220first reading

Engagement

1,627 posts held, back to 7 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 82 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
7.10%
avg views ÷ 195,032 subscribers
Avg views / post
13,800
880 posts measured
Reaction rate
1.02%
reactions ÷ views · ER floor
Posts in window
880
of 1,627 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 878 of 880 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 22 September 2026
Posts held1,627 (7 August 2026 – 22 September 2026)
Views total12,177,827
Reactions total123,838
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Sept 2026, 19:04 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
≈1,570
Videos
≈27
Links
≈1,060

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

Reaction mix

154,430 reactions across 994 posts, in 27 distinct kinds. The most used accounts for 73.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏114,00873.8%
🤬31,86020.6%
❤4,0032.59%
👎4950.321%
😢4590.297%
👍4420.286%
😨3700.24%
😭3330.216%
custom 52424272159577296983240.21%
🫡2930.19%
🤷‍♂2810.182%
🕊2660.172%
😐2530.164%
😡1940.126%
❤‍🔥1910.124%
🤯1500.097%
🆒1270.082%
👀1260.082%
🔥1260.082%
💘510.033%
7 further kinds780.051%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.

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 998 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 154,430 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 23 August 2026 to 22 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.

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
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ukraine_pyxx. 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 23 August 2026 to 22 September 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

22 Sept 2026, 18:55 UTC≈5,040 views103 reactionsread 22 September 2026

Запорізька область: БпЛА курсом на Кушугум. Харківщина: БпЛА курсом на Балаклію. БпЛА курсом на Козачу Лопань. БпЛА курсом на Золочів. Дніпропетровщина: БпЛА курсом на Кривий Ріг.

🙏73🤬25😭4❤1

22 Sept 2026, 18:46 UTC≈10,100 views142 reactionsread 22 September 2026

Донеччина: БпЛА курсом на Словʼянськ. Сумщина: БпЛА курсом на Суми.

🙏107🤬29❤3👎1🤷‍♂1😐1

22 Sept 2026, 18:44 UTC≈11,100 views143 reactionsread 22 September 2026

❗️ Пуски керованих авіаційних бомб тактичною авіацією на південь Харківщини.

🙏97🤬36😨6❤4

22 Sept 2026, 18:42 UTC≈12,400 views177 reactionsread 22 September 2026

❗️ Пуски керованих авіаційних бомб тактичною авіацією на Запорізьку область.

🙏131🤬43❤2👍1

22 Sept 2026, 18:38 UTC≈13,400 views134 reactionsread 22 September 2026

Черкащина: БпЛА курсом на Черкаси. Запорізька область: БпЛА курсом на Розумівку. БпЛА курсом на Запоріжжя.

🙏99🤬27😭4❤1👎1🤷‍♂1😐1

22 Sept 2026, 18:00 UTC≈28,700 views868 reactions1 Starread 22 September 2026

По ситуації на цю ніч: На сьогодні масованих пусків балістики не передбачається. Звичайні пуски можуть відбуватися, впринципі як і завжди. Ворогу тепер треба мінімум 4 дні на підготовку до атаки, тим більше, що ворог зараз в процесі накопичення ракет. По дронах ситуація як завжди, масованих пусків поки немає, але реактивні пускають по декілька штук стабільно. Щодо стратегічної авіації, то на сьогодні загроз немає…

🙏711🤬77❤40😐9👀6👍5💘5🕊5

22 Sept 2026, 17:52 UTC≈27,400 views146 reactions1 Starread 22 September 2026

Зараз буде вечірній пост по загрозах, але треба ще 18 тисяч щоб закрити збір. Будь-ласка підкиньте пару гривень, не так багато лишилось щоб закрити його щоб все поїхало хлопцям. https://send.monobank.ua/jar/5d1oMg36i3 4874 1000 3279 5661

🙏103❤33🙉3👌2👍2🕊2🤯1

22 Sept 2026, 17:48 UTC≈25,600 views161 reactionsread 22 September 2026

реактивний вилетів з Києва, курс Глеваха.

🙏133🤬23👀3❤2

22 Sept 2026, 17:47 UTC≈25,600 views182 reactionsread 22 September 2026

Також на Вінниччині є добрі звуки, на зараз в області дронів немає.

🙏172🤬10

22 Sept 2026, 17:45 UTC≈24,100 views152 reactionsread 22 September 2026

Далі летить у бік центру Києва

🙏110🤬34😢6❤1❤‍🔥1

22 Sept 2026, 17:43 UTC≈24,300 views163 reactionsread 22 September 2026

реактивний залетів в Київ, курс Троєщина

🙏129🤬17😢9👍3❤1👎1🔥1😡1

22 Sept 2026, 17:42 UTC≈22,400 views164 reactionsread 22 September 2026

На Вінниччині по реактивному попередньо мінус

🙏153❤8🤬3

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

Republished by

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

Republishes

Channels on the register whose posts this channel has forwarded.

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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

monitor
@war_monitor · 971,692
#1
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 905,765
#2
Лачен пише
@lachentyt · 1,554,565
#3
Київ ІНФО | Новини Україна 🇺🇦
@kievinfo_kyiv · 1,229,237
#4
Чому тривога | Радар
@raketa_trevoga · 486,538
#5
✈️Стратегічна авіація
@StrategicaviationT · 113,044
#6
Тотальна Зрада
@totallzrada · 266,323
#7
Карта повітряних тривог 🇺🇦
@alarmua · 941,699
#8
Київський купол | Графіки
@nebo_raketa · 445,226
#9
Реальна Війна | Україна | Новини
@voynareal · 1,522,485
#10
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 725,843
#11
Дніпро Alerts 🚀 🚨
@dnipro_alerts · 809,501
#12
Куди летить? | Тривога
@radar_raketaa · 502,859
#13
ОПЕРАТИВНИЙ ІНФОРМ
@operinform · 138,578
#14
🔊⚠️єРадар | Повітряна тривога | Ракетна небезпека
@eRadarrua · 394,900
#15
monitoring
@monitorwarr · 85,960
#16
INFOКИЇВ . новини 🇺🇦
@mistokyivnews · 31,567
#17
Україна Online: Новини | Політика
@UaOnlii · 1,575,421
#18
Ринда моніторить
@kudy_letyt · 143,342
#19
Андрій Смолій
@smolii_ukraine · 504,040
#20
Повітряна тривога️ | Бережіть себе!
@raketna_neb · 213,458
#21
HKR
@hyevuy_k_r · 153,625
#22
Авіа Моніторинг
@avia_monitoring · 797
#23
Труха⚡️Черкаси
@truexacherkasi · 174,614
#24
monitorwar
@monitoringwar · 26,550
#25
ЧП СтратАвиа 🇺🇦
@CPSTRATAVIA · 466
#26
∆✙🍒Гнила черешня🇺🇦✙∆
@gnilayachereha · 422,427
#27
Повітряна Тривога
@air_alert_ua · 240,756
#28
✙DeepState✙🇺🇦
@deepstateua · 761,011
#29
News of the war in Ukraine
@newsofthewarukraine · 58
#30
НУ І ДНІПРО! 🇺🇦
@ny_i_dnipro · 275,953
#31
Николаевский Ванёк
@vanek_nikolaev · 2,636,316
#32
Труха⚡️Україна
@truexanewsua · 3,127,306
#33
Реальний Київ | Украина
@kievreal1 · 1,554,012
#34
Левый Берег Киев
@kiev_levyy_bereg · 468,584
#35
INSIDER UA | Україна | Новини
@insiderukr · 2,183,396
#36
Всевидящее ОКО: Україна
@oko_ua · 1,178,797
#37
Труха⚡️Київ
@truexakyiv · 918,218
#38
Вмикач Київ | Світло💡
@kiev_svet · 234,861
#39
Одесса INFO ⚓️ 🇺🇦 Новости | Одеса
@odessa_infonews · 990,649
#40
STERNENKO
@ssternenko · 882,036
#41
Хуевая Одесса
@xydessa · 953,526
#42
Скринька Пандори
@pandoras_box_ua · 158,995
#43
Киевский Движ
@k_dvizh · 465,905
#44
Бавовна
@ukrbavovna · 701,096
#45
✙ 🔼Вертикаль
@vert2026 · 117,714
#46
Новости Одесса | Одеса
@our_odessa · 447,077
#47
Батальйон «Монако» | Україна | Новини
@batalionmonako · 710,211
#48
Говорять Снайпер ꑭ
@stanislav_osman · 289,232
#49
Tracking
@the_first_online · 8,125
#50
Захід Головне
@zahid_golovne_ua · 522,822
#51
Івано-Франківськ 24/7📱
@blacklist2477 · 290,515
#52
Правий Берег Київ | Киев
@kiev_pravyy_bereg · 180,809
#53
ОДЕССА ИНФО LIVE - радар Одеса
@odessa_inform · 381,669
#54
Новини Волкова
@Volkov_news_ua · 6,089
#55
ТСН новини / ТСН.ua
@tch_channel · 737,756
#56
News⚡️Cherkassy
@news_chrkssy · 160,068
#57
Ту-95МС
@tu95mc · 1,706
#58
Оперативний ЗСУ
@operativnoZSU · 366,524
#59

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

monitoring захід
@monitoring_zaxid · 99,866
Telegram ranks this channel #10 of 77 here — alongside 76 others — read 23 August 2026
Повітряний простір України 🇺🇦
@monikppy · 229,093
Telegram ranks this channel #11 of 80 here — alongside 79 others — read 14 August 2026
INFOКИЇВ . новини 🇺🇦
@mistokyivnews · 31,567
Telegram ranks this channel #26 of 80 here — alongside 79 others — read 5 September 2026
Ukraine 24/7 ⚠️
@Ukraine_UA_24_7 · 72,776
Telegram ranks this channel #32 of 84 here — alongside 83 others — read 20 August 2026
Твій Володимир🇺🇦
@tvoe_v_v · 59,925
Telegram ranks this channel #34 of 75 here — alongside 74 others — read 23 August 2026
✈️Стратегічна авіація
@StrategicaviationT · 113,044
Telegram ranks this channel #42 of 84 here — alongside 83 others — read 15 August 2026
Каменський Пацюк 🇺🇦🫡
@stone_rat · 26,297
Telegram ranks this channel #48 of 78 here — alongside 77 others — read 14 September 2026
Strategic Control
@strategicontrol · 26,128
Telegram ranks this channel #51 of 80 here — alongside 79 others — read 13 September 2026
РЕАЛЬНИЙ ФРАНКІВСЬК🚨
@realfrankivsk · 29,526
Telegram ranks this channel #51 of 65 here — alongside 64 others — read 8 September 2026
🚨 Радар ракет 📡
@ua_radar_raket · 36,247
Telegram ranks this channel #52 of 83 here — alongside 82 others — read 1 September 2026
monitorsmu
@monitorsmy · 23
Telegram ranks this channel #54 of 81 here — alongside 80 others — read 27 August 2026
КОРАБЕЛИ
@korabely_media · 149,183
Telegram ranks this channel #54 of 87 here — alongside 86 others — read 14 August 2026
Ринда моніторить
@kudy_letyt · 143,342
Telegram ranks this channel #59 of 72 here — alongside 71 others — read 13 August 2026
Око України - Захід.
@eyeukrainew · 26,161
Telegram ranks this channel #60 of 82 here — alongside 81 others — read 13 September 2026
Тривога Старкон !!!!
@grup223m · 28,178
Telegram ranks this channel #60 of 75 here — alongside 74 others — read 10 September 2026
Volynblog (Луцьк•Ковель•Володимир)
@volynblog · 112,272
Telegram ranks this channel #71 of 82 here — alongside 81 others — read 15 August 2026

This channel appears in 16 seed channels' Telegram-generated recommendation lists in total. 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Повітряний простір | Напрямок ракет” (@ukraine_pyxx), 195,032 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/ukraine_pyxx.

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.