Channel
@ai_radar_kyiv
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
427subscribers
+388 since we began measuring on 29 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004468197890 |
|---|---|
| Type | Channel |
| Username | @ai_radar_kyiv |
| Created | Between 1 June 2026 and 29 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 1 November 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 1 November 2026 |
| On Telegram | t.me/ai_radar_kyiv |
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 22 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Nov 2026, 12:35 | 427 | -3 |
| 25 Oct 2026, 07:10 | 430 | -7 |
| 19 Oct 2026, 05:18 | 437 | -9 |
| 13 Oct 2026, 05:49 | 446 | -6 |
| 2 Oct 2026, 17:38 | 452 | +73 |
| 16 Sept 2026, 19:38 | 379 | +20 |
| 8 Sept 2026, 00:58 | 359 | +320 |
| 29 Aug 2026, 19:00 | 39 | no change |
| 29 Aug 2026, 18:45 | 39 | first reading |
20 posts held, back to 29 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 1 page 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 20 posts for this entry, the most recent from 29 August 2026. An engagement rate over an empty window would be a number about nothing.
🛸 БПЛА: кількість уточнюється 📍 Загроза: Лівий берег (Троєщина) Джерела: @kievreal1 · 21:58:13 По 1 на Троєщину, Лебедівку та Димер Надіслати новину @kyiv_radar_ua · 21:59:41 Наступний реактивний підлітає на Троєщину
📝 Повідомляють про вибух у столиці Джерела: @radar_raketaa · 21:55:50 Повідомляють про вибух у Столиці.
🛸 БПЛА: кількість уточнюється 📍 Загроза: Лівий берег (Троєщина) 📝 БПЛА пролетів Київську ГЕС · ще один — із Вишгорода в бік Києва Джерела: @ukraine_pyxx · 21:46:11 Є, пролетів Київську ГЕС курсом на Троєщину. @AerisRimor · 21:46:21 Вишгород на Київ Правий БПЛА.
📍 Загроза: Правий берег (Оболонь) 📝 Перший — на Оболонь Джерела: @kievreal1 · 21:44:34 Троєщина, Вишгород увага ㅤ Надіслати новину @kyiv_radar_ua · 21:45:34 Перший на Оболонь
⚠️ Тривога в Києві.
✅ Відбій тривоги в Києві. Моніторинг зупинено.
📝 Попередньо збитий, без фіксації Джерела: @kievreal1 · 19:40:35 Оболонь далі ㅤ Надіслати новину @k_dvizh · 19:40:38 БпЛА на Троєщину. Присылайте контент в анонимный бот ⬅ @kiev_levyy_bereg · 19:40:40 Оболонь далі
🛸 БПЛА: кількість уточнюється 📍 Загроза: Лівий берег (Деснянський) 📝 Реактивний БПЛА заходить у Київ з боку Вишгорода Джерела: @ukraine_pyxx · 19:39:00 від Вишгорода реактивний залітає в Київ, курс Деснянський район.
⚠️ Тривога в Києві.
✅ Відбій тривоги в Києві. Моніторинг зупинено.
📝 Цілі не фіксуються Джерела: @k_dvizh · 18:35:46 Реактив на Троєщину. ➡️ ПОДПИСАТЬСЯ Присылайте контент в анонимный бот ➡️ @Obstanovka_kyiv_bot ⬅️ @kyiv_radar_ua · 18:36:14 Дарниця @kiev_levyy_bereg · 18:36:27 Поділ @kievreal1 · 18:36:35 Поділ ㅤ Надіслати новину @novosti_kieva_bot 👉 ПІДПИСАТИСЯ
🛸 БПЛА: кількість уточнюється 📍 Загроза: Лівий берег (Троєщина) 📝 Один реактивний БпЛА повертається в Київ · ще один курсом на Калиту Джерела: @ukraine_pyxx · 18:34:45 Київщина: 1х реактивний на керуванні повертається в Київ (Троєщина) повз Погреби. 1х реактивний курсом на Калиту.
Showing the 12 most recent of 20 posts we hold for @ai_radar_kyiv. 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.
Named by 4 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 1 November 2026 — this entry's latest reading, not the date you are reading this.
“Bybem Bot | AI Radar Київ” (@ai_radar_kyiv), 427 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/ai_radar_kyiv.
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.