Telegram RegisterThe public register of Telegram
Telegram profile photo for ПОВІТРЯНА ТРИВОГА КАРТА

Channel

ПОВІТРЯНА ТРИВОГА КАРТА

@vozdushnaya_trevogaa

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

7,092subscribers

-172 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001261650960
TypeChannel
Username@vozdushnaya_trevogaa
Created10 January 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/vozdushnaya_trevogaa

Topic

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

7,0787,2657,171.57 August 2026 — 7,264 subscribers7 August 2026 — 7,264 subscribers7 August 2026 — 7,265 subscribers10 August 2026 — 7,258 subscribers13 August 2026 — 7,246 subscribers16 August 2026 — 7,221 subscribers20 August 2026 — 7,198 subscribers23 August 2026 — 7,184 subscribers27 August 2026 — 7,165 subscribers30 August 2026 — 7,146 subscribers2 September 2026 — 7,135 subscribers6 September 2026 — 7,115 subscribers11 September 2026 — 7,104 subscribers14 September 2026 — 7,078 subscribers18 September 2026 — 7,092 subscribers7,0927 August 202618 September 2026
15 measurements spanning 42 days, net -172. 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 7,050–7,293 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 11:157,092+14
14 Sept 2026, 14:387,078-26
11 Sept 2026, 11:387,104-11
6 Sept 2026, 08:027,115-20
2 Sept 2026, 11:467,135-11
30 Aug 2026, 01:047,146-19
27 Aug 2026, 02:367,165-19
23 Aug 2026, 22:447,184-14
20 Aug 2026, 01:397,198-23
16 Aug 2026, 21:337,221-25
13 Aug 2026, 07:447,246-12
10 Aug 2026, 15:167,258-7
7 Aug 2026, 12:047,265+1
7 Aug 2026, 09:307,264no change
7 Aug 2026, 09:247,264first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 260 posts for this entry, the most recent from 20 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

124 reactions across 101 posts, in 4 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬9375.0%
🙏1512.1%
👎1310.5%
❤32.42%

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 101 of the 260 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 124 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 260 most recent posts we hold, published 7 August 2026 to 20 August 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

20 Aug 2026, 11:39 UTC61 viewsread 20 August 2026

🛸 Городня (Чернігівська обл.) Загроза застосування БПЛА. Перейдіть в укриття!

20 Aug 2026, 10:48 UTC136 views1 reactionsread 20 August 2026

🛸 Харків (Харківська обл.) Загроза застосування БПЛА. Перейдіть в укриття!

🤬1

20 Aug 2026, 10:38 UTC151 views1 reactionsread 20 August 2026

🛸 Тростянець (Вінницька обл.) Загроза застосування БПЛА. Перейдіть в укриття!

🤬1

20 Aug 2026, 10:27 UTC168 views1 reactionsread 20 August 2026

🛸 Чечельник (Вінницька обл.) Загроза застосування БПЛА. Перейдіть в укриття!

🤬1

20 Aug 2026, 10:26 UTC169 views1 reactionsread 20 August 2026

🛸 Славутич (Київська обл.) Загроза застосування БПЛА. Перейдіть в укриття!

🤬1

20 Aug 2026, 09:44 UTC229 views1 reactionsread 20 August 2026

🛸 Запоріжжя (Запорізька обл.) Загроза застосування БПЛА. Перейдіть в укриття!

🤬1

20 Aug 2026, 09:38 UTC235 views1 reactionsread 20 August 2026

🛸 Київ Загроза застосування БПЛА. Перейдіть в укриття! 🛸 Вишгород (Київська обл.) Загроза застосування БПЛА. Перейдіть в укриття!

🤬1

20 Aug 2026, 09:24 UTC232 views1 reactionsread 20 August 2026

🛸 Херсон (Херсонська обл.) Загроза застосування БПЛА. Перейдіть в укриття!

🤬1

20 Aug 2026, 09:22 UTC225 views1 reactionsread 20 August 2026

🛸 Бориспіль (Київська обл.) Загроза застосування БПЛА. Перейдіть в укриття!

🤬1

20 Aug 2026, 09:19 UTC224 views1 reactionsread 20 August 2026

🛸 Марганець (Дніпропетровська обл.) Загроза застосування БПЛА. Перейдіть в укриття! 🛸 Бровари (Київська обл.) Загроза застосування БПЛА. Перейдіть в укриття! 🛸 Нікополь (Дніпропетровська обл.) Загроза застосування БПЛА. Перейдіть в укриття!

🤬1

20 Aug 2026, 09:17 UTC201 views1 reactionsread 20 August 2026

🛸 Славутич (Київська обл.) Загроза застосування БПЛА. Перейдіть в укриття!

🤬1

20 Aug 2026, 09:12 UTC206 views1 reactionsread 20 August 2026

🛸 Циркуни (Харківська обл.) Загроза застосування БПЛА. Перейдіть в укриття! 🛸 Харків (Харківська обл.) Загроза застосування БПЛА. Перейдіть в укриття!

🤬1

Showing the 12 most recent of 260 posts we hold for @vozdushnaya_trevogaa. 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

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“ПОВІТРЯНА ТРИВОГА КАРТА” (@vozdushnaya_trevogaa), 7,092 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/vozdushnaya_trevogaa.

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.