Telegram RegisterThe public register of Telegram
Telegram profile photo for 🚀МОНІТОРИНГ🇺🇦😔💔🕯️

Channel

🚀МОНІТОРИНГ🇺🇦😔💔🕯️

@monitorynh_24

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

1,824subscribers

-141 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001796506569
TypeChannel
Username@monitorynh_24
Created9 October 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live12 October 2026
Measurements held15
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/monitorynh_24

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 16 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

1,8241,9661,8957 August 2026 — 1,965 subscribers7 August 2026 — 1,966 subscribers14 August 2026 — 1,964 subscribers17 August 2026 — 1,960 subscribers21 August 2026 — 1,953 subscribers24 August 2026 — 1,948 subscribers27 August 2026 — 1,943 subscribers30 August 2026 — 1,935 subscribers2 September 2026 — 1,918 subscribers7 September 2026 — 1,900 subscribers11 September 2026 — 1,892 subscribers15 September 2026 — 1,887 subscribers28 September 2026 — 1,849 subscribers5 October 2026 — 1,838 subscribers12 October 2026 — 1,824 subscribers7 August 202612 October 2026
15 measurements spanning 66 days, net -141. 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 1,803–1,987 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 11:371,824-14
5 Oct 2026, 20:381,838-11
28 Sept 2026, 15:391,849-38
15 Sept 2026, 16:171,887-5
11 Sept 2026, 17:151,892-8
7 Sept 2026, 11:381,900-18
2 Sept 2026, 14:551,918-17
30 Aug 2026, 16:231,935-8
27 Aug 2026, 08:531,943-5
24 Aug 2026, 17:231,948-5
21 Aug 2026, 02:421,953-7
17 Aug 2026, 16:471,960-4
14 Aug 2026, 13:381,964-2
7 Aug 2026, 20:201,966+1
7 Aug 2026, 09:161,965first reading

Engagement

40 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 2 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 40 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

14 reactions across 14 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏14100.0%

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

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

7 Aug 2026, 17:04 UTC1 viewsread 7 August 2026

🚨 Броварський район (Київська область) Повітряна тривога

Signed 🚀МОНІТОРИНГ🇺🇦😔💔🕯

7 Aug 2026, 16:52 UTC31 viewsread 7 August 2026

🚨 м. Запоріжжя та Запорізька територіальна громада (Запорізька область) Повітряна тривога

Signed 🚀МОНІТОРИНГ🇺🇦😔💔🕯

7 Aug 2026, 16:52 UTC33 viewsread 7 August 2026

🚨 Запорізький район (Запорізька область) Повітряна тривога

Signed 🚀МОНІТОРИНГ🇺🇦😔💔🕯

7 Aug 2026, 16:41 UTC47 viewsread 7 August 2026

🟢 Миколаївський район (Миколаївська область) Відбій повітряної тривоги

Signed 🚀МОНІТОРИНГ🇺🇦😔💔🕯

7 Aug 2026, 16:41 UTC47 viewsread 7 August 2026

🟢 Криворізький район (Дніпропетровська область) Відбій повітряної тривоги

Signed 🚀МОНІТОРИНГ🇺🇦😔💔🕯

7 Aug 2026, 16:41 UTC47 viewsread 7 August 2026

🟢 Дніпровський район (Дніпропетровська область) Відбій повітряної тривоги

Signed 🚀МОНІТОРИНГ🇺🇦😔💔🕯

7 Aug 2026, 16:40 UTC18 viewsread 7 August 2026

🟢 Херсонський район (Херсонська область) Відбій повітряної тривоги

Signed 🚀МОНІТОРИНГ🇺🇦😔💔🕯

7 Aug 2026, 16:27 UTC52 viewsread 7 August 2026

🚀 м. Полтава та Полтавська територіальна громада (Полтавська область) Загроза застосування високошвидкісних цілей. Негайно прямуйте в укриття!

Signed 🚀МОНІТОРИНГ🇺🇦😔💔🕯

7 Aug 2026, 16:27 UTC53 viewsread 7 August 2026

🚨 Полтавський район (Полтавська область) Повітряна тривога

Signed 🚀МОНІТОРИНГ🇺🇦😔💔🕯

7 Aug 2026, 16:08 UTC77 viewsread 7 August 2026

🚨 Миколаївський район (Миколаївська область) Повітряна тривога

Signed 🚀МОНІТОРИНГ🇺🇦😔💔🕯

7 Aug 2026, 16:08 UTC76 viewsread 7 August 2026

🚨 Херсонський район (Херсонська область) Повітряна тривога

Signed 🚀МОНІТОРИНГ🇺🇦😔💔🕯

7 Aug 2026, 16:03 UTC79 viewsread 7 August 2026

🚨 Дніпровський район (Дніпропетровська область) Повітряна тривога

Signed 🚀МОНІТОРИНГ🇺🇦😔💔🕯

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

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

“🚀МОНІТОРИНГ🇺🇦😔💔🕯️” (@monitorynh_24), 1,824 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/monitorynh_24.

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.