Telegram RegisterThe public register of Telegram

Channel

🇺🇦 Олександр Саюк / Міський голова Нікополя

@NikopolOperativniy

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

37,713subscribers

-122 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001711880080
TypeChannel
Username@NikopolOperativniy
Created24 February 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/NikopolOperativniy

Growth

37,71337,83537,7746 August 2026 — 37,835 subscribers7 August 2026 — 37,819 subscribers8 August 2026 — 37,790 subscribers9 August 2026 — 37,779 subscribers10 August 2026 — 37,765 subscribers11 August 2026 — 37,752 subscribers12 August 2026 — 37,730 subscribers13 August 2026 — 37,713 subscribers6 August 202613 August 2026
8 measurements spanning 7 days, net -122. 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 37,695–37,853 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 05:0637,713-17
12 Aug 2026, 04:4237,730-22
11 Aug 2026, 02:3337,752-13
10 Aug 2026, 04:2037,765-14
9 Aug 2026, 02:5137,779-11
8 Aug 2026, 01:5637,790-29
7 Aug 2026, 05:2137,819-16
6 Aug 2026, 09:4837,835first reading

Engagement

192 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
14.6%
avg views ÷ 37,713 subscribers
Avg views / post
5,520
192 posts measured
Reaction rate
1.03%
reactions ÷ views · ER floor
Posts in window
192
of 192 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 12 August 2026
Posts held192 (6 August 202612 August 2026)
Views total1,059,842
Reactions total10,892
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 20:44 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.

Reaction mix

10,892 reactions across 192 posts, in 11 distinct kinds. The most used accounts for 49.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏5,39349.5%
🤬2,45922.6%
😢2,00818.4%
5034.62%
👍2492.29%
😱1351.24%
🔥580.533%
🥰390.358%
🤔300.275%
👏170.156%
👌10.009%

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

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

12 Aug 2026, 18:19 UTC≈3,480 views66 reactionsread 12 August 2026

🔴 21:19 Загроза артобстрілу! Зараз у м. Нікополь та Нікопольська територіальна громада артилерійський обстріл. Пройдіть в укриття! #м_Нікополь_та_Нікопольська_територіальна_громада

🙏38🤬225😢1

12 Aug 2026, 15:32 UTC≈6,710 views87 reactionsread 12 August 2026

🔴 Повітряна тривога в Нікопольський район Слідкуйте за подальшими повідомленнями. #Нікопольський_район

🙏50🤬322🔥1😢1😱1

12 Aug 2026, 15:32 UTC≈8,280 views184 reactionsread 12 August 2026
Photo

Інформація станом на вечір 12 серпня 2026р: Шановні нікопольці! Від ранку місто перебувало під обстрілом дронів-камікадзе та двічі зі ствольної артилерії. Минулось без поранених та загиблих. Пошкоджено приватний житловий будинок. Внаслідок обстрілу сталася пожежа. Також внаслідок ранкового обстрілу було пошкоджено ще 3 багатоквартирні житлові будинки, 2 магазини. Інформація уточнюється. Якщо вам потрібна допомога,

😢71🤬54🙏4113😱3👍1👏1

12 Aug 2026, 14:35 UTC≈6,540 views62 reactionsread 12 August 2026

🔴 17:35 Повітряна тривога в Нікопольський район Слідкуйте за подальшими повідомленнями. #Нікопольський_район

🙏35🤬17😢6😱21🔥1

12 Aug 2026, 13:44 UTC≈6,750 views69 reactionsread 12 August 2026

🟠 16:43 Увага! Атака дронів-камікадзе! #м_Нікополь_та_Нікопольська_територіальна_громада

🙏40🤬26😱2😢1

12 Aug 2026, 13:13 UTC≈6,840 views65 reactionsread 12 August 2026

🟠 16:06 Увага! Атака дронів-камікадзе #м_Нікополь_та_Нікопольська_територіальна_громада

🙏40🤬202😱2😢1

12 Aug 2026, 13:13 UTC≈6,780 views51 reactionsread 12 August 2026

🔴 16:05 Повітряна тривога в м. Нікополь та Нікопольська територіальна громада Слідкуйте за подальшими повідомленнями. #м_Нікополь_та_Нікопольська_територіальна_громада

🙏32🤬151🔥1😢1😱1

12 Aug 2026, 12:07 UTC≈7,080 views64 reactionsread 12 August 2026

🟢 15:07 Відбій тривоги в м. Нікополь та Нікопольська територіальна громада. Слідкуйте за подальшими повідомленнями. #м_Нікополь_та_Нікопольська_територіальна_громада

🙏49👍76🤔1🥰1

12 Aug 2026, 12:07 UTC≈6,900 views47 reactionsread 12 August 2026

🟢 15:06 Відбій тривоги в Нікопольський район. Слідкуйте за подальшими повідомленнями. #Нікопольський_район

🙏34👍62👏2🤔2🥰1

12 Aug 2026, 11:54 UTC≈6,830 views55 reactionsread 12 August 2026

🟠 14:53 Увага! Атака ударних БПЛА #м_Нікополь_та_Нікопольська_територіальна_громада

🙏32🤬18😱2👍1👏1😢1

12 Aug 2026, 11:44 UTC≈6,830 views52 reactionsread 12 August 2026

🟠 14:44 Увага! Атака ударних БПЛА #м_Нікополь_та_Нікопольська_територіальна_громада

🙏29🤬16😢3😱21🔥1

12 Aug 2026, 11:42 UTC≈6,610 views45 reactionsread 12 August 2026

🟠 14:41 Увага! Атака дронів-камікадзе #м_Нікополь_та_Нікопольська_територіальна_громада

🙏27🤬15👏1😢1😱1

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

Citation-graph rank

Citation-graph rank — 410,355 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“🇺🇦 Олександр Саюк / Міський голова Нікополя” (@NikopolOperativniy), 37,713 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/NikopolOperativniy.

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.