Telegram RegisterThe public register of Telegram
Telegram profile photo for Балачка Чернігів⚠️

Channel

Балачка Чернігів⚠️

@balachkachernihiv

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

3subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003144264745
TypeChannel
Username@balachkachernihiv
DescriptionТГК про загрози для Чернігіва/області, працює цілодобово
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live9 November 2026
Measurements held2
On Telegramt.me/balachkachernihiv

Growth

37 August 2026 — 3 subscribers13 August 2026 — 3 subscribers7 August 202613 August 2026
2 measurements spanning 6 days. 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 17:313no change
7 Aug 2026, 17:243first reading

Engagement

20 posts held, back to 30 July 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 2 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
≈106
Videos
≈6
Links
≈3,690

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

Recent posts

2 Aug 2026, 02:42 UTC1 viewsread 13 August 2026

🛵 Чернігівщина: реактивний БпЛА повз Славутич курсом на південь; реактивний БпЛА повз Корюківку курсом на південний захід. Інформація з https://t.me/kpszsu ❗️ПЕРЕСЛАЛА❗️ @BALACHKACHERNIHIV⚠️

2 Aug 2026, 02:35 UTC1 viewsread 13 August 2026

Ще один реактивний на Чернігівщині на Холми / Понорницю Інформація з https://t.me/eRadarrua ❗️ПЕРЕСЛАЛА❗️ @BALACHKACHERNIHIV⚠️

2 Aug 2026, 00:38 UTC1 viewsread 13 August 2026

🛵Чернігівщина: БпЛА в районі Городні. Інформація з https://t.me/kpszsu ❗️ПЕРЕСЛАЛА❗️ @BALACHKACHERNIHIV⚠️

1 Aug 2026, 09:06 UTC1 viewsread 13 August 2026

🛵 Новий на Чернігівщині курсом на Славутич Інформація з https://t.me/eRadarrua ❗️ПЕРЕСЛАЛА❗️ @BALACHKACHERNIHIV⚠️

1 Aug 2026, 08:04 UTC1 viewsread 13 August 2026

🛵 Чернігівщина - реактивні БпЛА повз Славутич курсом на Десну. Інформація з https://t.me/kpszsu ❗️ПЕРЕСЛАЛА❗️ @BALACHKACHERNIHIV⚠️

1 Aug 2026, 03:19 UTC1 viewsread 13 August 2026

Чернігів: БПЛА над містом Інформація з https://t.me/eRadarrua ❗️ПЕРЕСЛАЛА❗️ @BALACHKACHERNIHIV⚠️

31 Jul 2026, 23:29 UTC1 viewsread 13 August 2026

Наш канал по Чернігівщині де ми пишемо про рух ворожих БпЛА - https://t.me/+4bsYYhyoc25mZDEy Інформація з https://t.me/monikppy ❗️ПЕРЕСЛАЛА❗️ @BALACHKACHERNIHIV⚠️

31 Jul 2026, 23:19 UTC1 viewsread 13 August 2026

🛵 Наступна пара реактивних повз Козелець на Чернігівщині курсом на столицю Інформація з https://t.me/eRadarrua ❗️ПЕРЕСЛАЛА❗️ @BALACHKACHERNIHIV⚠️

31 Jul 2026, 22:42 UTC1 viewsread 13 August 2026

Ціль на / повз Чернігів Інформація з https://t.me/eRadarrua ❗️ПЕРЕСЛАЛА❗️ @BALACHKACHERNIHIV⚠️

31 Jul 2026, 22:29 UTC1 viewsread 13 August 2026

Ціль на Сумщині курс на Чернігівщину Інформація з https://t.me/monikppy ❗️ПЕРЕСЛАЛА❗️ @BALACHKACHERNIHIV⚠️

31 Jul 2026, 09:01 UTC1 viewsread 13 August 2026

🛵 Чернігівщина: реактивні БпЛА ➡️ у напрямку Прилук, Ніжина, Линовиці. Інформація з https://t.me/kpszsu ❗️ПЕРЕСЛАЛА❗️ @BALACHKACHERNIHIV⚠️

31 Jul 2026, 08:48 UTC1 viewsread 13 August 2026

🛸 Чернігівщина: на півночі від Чернігова та біля н.п.Семенівка, Холми працюють розвідувальні БпЛА противника, які можуть бути навідниками ворожих засобів ураження! Залучено засоби для їх збиття. Інформація з https://t.me/kpszsu ❗️ПЕРЕСЛАЛА❗️ @BALACHKACHERNIHIV⚠️

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

Mentions

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

“Балачка Чернігів⚠️” (@balachkachernihiv), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/balachkachernihiv.

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.