Telegram RegisterThe public register of Telegram
Telegram profile photo for SURPRISE UA RADAR | Повітряна тривога

Channel

SURPRISE UA RADAR | Повітряна тривога

@surprise_ua_radar

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

385subscribers

+42 since we began measuring on 19 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003926015688
TypeChannel
Username@surprise_ua_radar
CreatedBetween 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 September 2026
Last confirmed live26 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/surprise_ua_radar

Growth

34338536419 September 2026 — 343 subscribers19 September 2026 — 343 subscribers26 September 2026 — 385 subscribers19 September 202626 September 2026
3 measurements spanning 7 days, net +42. 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 337–391 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 02:17385+42
19 Sept 2026, 08:22343no change
19 Sept 2026, 07:47343first reading

Engagement

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

ERR · 30 days
13.7%
avg views ÷ 385 subscribers
Avg views / post
52.6
20 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
20
of 20 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 19 September 2026
Posts held20 (19 September 2026 – 19 September 2026)
Views total1,053
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Sept 2026, 08:22 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.

Recent posts

19 Sept 2026, 08:19 UTC5 viewsread 19 September 2026

🛸 БпЛА: Ріпки (Чернігівський район, Чернігівська обл.), рухається у бік: Київщина. ➡️ Можливий напрямок: ЧЗВ → Вишгородський р-н → Катюжанка → Бородянка. ⚠️ Увага — Рибаківка (Миколаївський район, Миколаївська обл.), напрямок — Одещина. Поруч: Одеський. ➡️ Можливий напрямок: Коблево → Слобідка. Слідкуємо за обстановкою.

19 Sept 2026, 08:17 UTC8 viewsread 19 September 2026

⚠️ Увага, рухається у бік: Тростянець. Слідкуємо за обстановкою.

19 Sept 2026, 08:15 UTC12 viewsread 19 September 2026

🔴 ПОВІТРЯНА ТРИВОГА Тривогу оголошено в: - Миколаївська область - Херсонська область Пройдіть до найближчого укриття.

19 Sept 2026, 08:15 UTC11 viewsread 19 September 2026

⚠️ швидкісна ціль (тип не уточнено): Куп'янськ (Куп’янський район, Харківська обл.). Поруч: Ізюмський, Сватівський. ➡️ Можливий напрямок: Сватівський р-н → Сіверськодонецький р-н. Слідкуємо за обстановкою.

19 Sept 2026, 08:14 UTC424 viewsread 19 September 2026

⚠️ Увага: Ріпки (Чернігівський район, Чернігівська обл.), рухається у бік: Київщина. ➡️ Можливий напрямок: ЧЗВ → Вишгородський р-н → Катюжанка → Бородянка. Слідкуємо за обстановкою.

19 Sept 2026, 08:12 UTC13 viewsread 19 September 2026

🛸 Юнаківка (Сумський район, Сумська обл.): БпЛА. Слідкуємо за обстановкою.

19 Sept 2026, 08:10 UTC14 viewsread 19 September 2026

🟢 ВІДБІЙ ТРИВОГИ Відбій повітряної тривоги в: - Миколаївська область - Одеська область Слідкуємо за подальшою обстановкою.

19 Sept 2026, 08:08 UTC20 viewsread 19 September 2026

🛸 Гельмязів (Золотоніський район, Черкаська обл.): БпЛА. Поруч: Черкаський, Бориспільський. ➡️ Далі, ймовірно: Черкаський р-н → Ірдинь → Звенигородський р-н. Слідкуємо за обстановкою.

19 Sept 2026, 08:05 UTC21 viewsread 19 September 2026

🟢 ВІДБІЙ ТРИВОГИ Відбій повітряної тривоги в: - Житомирська область - Кіровоградська область Слідкуємо за подальшою обстановкою.

19 Sept 2026, 08:03 UTC22 viewsread 19 September 2026

🟢 ВІДБІЙ ТРИВОГИ Відбій повітряної тривоги у Києві. Слідкуємо за подальшою обстановкою.

19 Sept 2026, 08:02 UTC26 viewsread 19 September 2026

⚠️ Увага — напрямок: Миронівка. Слідкуємо за обстановкою.

19 Sept 2026, 07:57 UTC28 viewsread 19 September 2026

✅ Суми — загроза минула Слідкуємо за обстановкою.

Showing the 12 most recent of 20 posts we hold for @surprise_ua_radar. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Republished by

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

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.

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

“SURPRISE UA RADAR | Повітряна тривога” (@surprise_ua_radar), 385 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/surprise_ua_radar.

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.