Telegram RegisterThe public register of Telegram
Telegram profile photo for 👉Наблюдатель Харьковськой Области👈

Channel

👉Наблюдатель Харьковськой Области👈

@Nabludatel_kh

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

1subscribers

+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-1003712243055
TypeChannel
Username@Nabludatel_kh
DescriptionНовості Присилаются От Radar Богодухів,Kharkiv News,Наблюдатель Харьков! Отправлятимутся З 10:00 До 20:00 Можуть Бути Задержки!!
Created22 February 2026measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live18 September 2026
Measurements held2
On Telegramt.me/Nabludatel_kh

Growth

17 August 2026 — 1 subscribers14 August 2026 — 1 subscribers7 August 202614 August 2026
2 measurements spanning 7 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 22:311no change
7 Aug 2026, 18:381first reading

Engagement

9 posts held, back to 22 February 2026the 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 9 posts for this entry, the most recent from 22 February 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

22 Feb 2026, 17:43 UTC1 viewsread 14 August 2026
Forwarded from @Nablydatel_Dozor

❗⚠️ Харьковская область. БпЛА в районе Старый Мерчик

22 Feb 2026, 17:42 UTC1 viewsread 14 August 2026
Forwarded from @Nablydatel_Dozor

❗⚠️ Харьковская область. Шахеды над Слатино курсом на Дергачи

22 Feb 2026, 17:42 UTC1 viewsread 14 August 2026
Forwarded from @Nablydatel_Dozor

❗⚠️ Харьковская область. FPV-дроны: ➡️Гусинка ➡️Моначиновка ➡️между Староверовка и Гусинка БпЛА-разведчик ⚠️Зала - Березники ⚠️Орлан - Волчанск

22 Feb 2026, 17:42 UTC2 viewsread 14 August 2026
Forwarded from @KharkovNews2023

⚠️⚠️Сообщают о мопеде в р=не Дергачей

22 Feb 2026, 17:42 UTC2 viewsread 14 August 2026
Forwarded from @KharkovNews2023

⚠️⚠️Пуски мопедов с Приморск-Ахтарска и Брянска

22 Feb 2026, 17:41 UTCviews —

Channel name was changed to «👉Наблюдатель Харьковськой Области👈»

Showing the 9 most recent of 9 posts we hold for @Nabludatel_kh. 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

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

“👉Наблюдатель Харьковськой Области👈” (@Nabludatel_kh), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Nabludatel_kh.

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.