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 11 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
Previous handles
@eyes_everywhere_dnipro was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
@NA_chasi_zp held 7 August 2026 – 7 August 2026
Growth
35 measurements spanning 43 days, net +2,674. 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 9,338–13,670 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)
Subscribers
Change
19 Sept 2026, 16:59
13,170
+774
17 Sept 2026, 03:56
12,396
+2,558
13 Sept 2026, 13:41
9,838
-60
12 Sept 2026, 13:41
9,898
no change
12 Sept 2026, 07:47
9,898
-236
10 Sept 2026, 15:18
10,134
-60
7 Sept 2026, 09:41
10,194
-42
4 Sept 2026, 12:00
10,236
-22
3 Sept 2026, 02:17
10,258
-16
1 Sept 2026, 23:57
10,274
-11
1 Sept 2026, 02:15
10,285
-21
31 Aug 2026, 00:17
10,306
-13
30 Aug 2026, 02:24
10,319
-17
29 Aug 2026, 02:34
10,336
-28
27 Aug 2026, 23:46
10,364
-12
26 Aug 2026, 22:17
10,376
-19
26 Aug 2026, 00:41
10,395
+50
25 Aug 2026, 03:33
10,345
-19
23 Aug 2026, 17:47
10,364
-19
22 Aug 2026, 00:46
10,383
first reading
Engagement
36 posts held, back to 2 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 38 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
135.9%
avg views ÷ 13,170 subscribers
Avg views / post
17,900
4 posts measured
Reaction rate
0.148%
reactions ÷ views · ER floor
Posts in window
4
of 36 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
Window
Rolling 30 days · latest post in window 29 August 2026
Posts held
36 (2 August 2026 – 29 August 2026)
Views total
71,570
Reactions total
106
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
29 Aug 2026, 15:14 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.
What this channel posts
Video runtime
5m 40s
Average length
1m 08s
Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
1,726 reactions across 36 posts, in 11 distinct kinds. The most used accounts for 32.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
😢
557
32.3%
🤬
441
25.6%
🙏
391
22.7%
❤
225
13.0%
💔
38
2.20%
👏
27
1.56%
👍
23
1.33%
🔥
12
0.695%
😡
5
0.29%
👌
4
0.232%
🆒
3
0.174%
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 36 of the 36 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 1,726 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 2 August 2026 to 29 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.
Кадри з евакуації в населеному пункті Новоіванівка - від нашого читача.
Евакуація продовжується в різних населених пунктах Запорізької області.
Для зв'язку:
066-461-16-31 - БФ "Допомога Нації"
068-590-65-36 - Капеланський Патруль
066-805-43-62 - ГО "Міський Центр Допомоги"
🚨 ДТП у парку Гагаріна
У парку Гагаріна сталася аварія — попередньо, автомобіль збив чоловіка.
На місці люди надають постраждалому допомогу. Інформація про його стан та обставини ДТП уточнюється.
❗️Через ворожий удар Кушугумська громада нині перебуває без електропостачання.
Відновлювальні роботи розпочнуться, як тільки дозволить безпекова ситуація.
Також пошкоджені приватні будинки. Минулося без постраждалих.
🚨 Підозрюваного держреєстратора із Запоріжжя екстрадували з Іспанії
Чоловік, який із 2022 року переховувався від слідства, підозрюється у незаконному переоформленні квартири вартістю майже 1 млн грн.
За даними слідства, він використав підроблене рішення суду та зареєстрував трикімнатне житло на жінку, яка назвалася співмешканкою померлого власника. Однак спадкоємців у чоловіка не було, тож квартира мала перейти гром…
⚡️ У Запоріжжі будують підземні енергооб’єкти та укриття для трансформаторів
На двох підстанціях зводять підземні конструкції, а понад половину ключових трансформаторів уже захищено спеціальними укриттями. До початку зими планують завершити роботи на всіх об’єктах.
•За словами голови ОВА Івана Федорова, захисні споруди вже витримали атаки «Шахедами» та удар КАБу.
Також область на 100% забезпечена резервними промисл…
❗️ДТП у Хортицькому районі
Аварія сталася біля ринку «Універсам» на вулиці Світлій. На місці працюють відповідні служби.
Інформація про постраждалих наразі уточнюється.
🙏24❤8😢4🆒2👏1
Showing the 12 most recent of 36 posts we hold for @eyes_everywhere_dnipro. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 1 registered channel — 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.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
✙ ЗСУ HUB ✙ @ukraine_3CY_HUB · 36,294 Telegram ranks this channel #8 of 77 here — alongside 76 others — read 1 September 2026
it_is_zp @it_is_zp_tg · 44,828 Telegram ranks this channel #12 of 70 here — alongside 69 others — read 28 August 2026
🚨Запоріжжя | Оперативно | Аварійка @avariyka_zaporizg · 47,644 Telegram ranks this channel #12 of 72 here — alongside 71 others — read 27 August 2026
Труха⚡️Запоріжжя @truexazaporozie · 278,065 Telegram ranks this channel #19 of 82 here — alongside 81 others — read 10 August 2026
Типичный Шевчик - Запорожье | Запоріжжя 🇺🇦 @tpshev_zp · 29,767 Telegram ranks this channel #21 of 72 here — alongside 71 others — read 8 September 2026
ЗАПОРІЖЖЯ НОВИНИ | ЗАПОРОЖЬЕ НОВОСТИ 🇺🇦 | РАДАР | CВЕТ @pro_zp_2023 · 26,544 Telegram ranks this channel #23 of 82 here — alongside 81 others — read 12 September 2026
Анатолій Куртєв @kurtievofficial · 48,499 Telegram ranks this channel #23 of 80 here — alongside 79 others — read 26 August 2026
Оперативно → by HLEP @operatyvnohlep · 169,392 Telegram ranks this channel #23 of 79 here — alongside 78 others — read 12 August 2026
ЗаБор Запоріжжя @zaborzp · 105,195 Telegram ranks this channel #26 of 90 here — alongside 89 others — read 15 August 2026
Радар⚡️Запоріжжя @radar_zaporizhzhya · 93,435 Telegram ranks this channel #30 of 83 here — alongside 82 others — read 16 August 2026
Это Запорожье 🇺🇦 Новости @eto_zp · 176,325 Telegram ranks this channel #30 of 84 here — alongside 83 others — read 12 August 2026
ЗАПОРІЖЖЯ.ІНФО @info_zp · 190,449 Telegram ranks this channel #32 of 83 here — alongside 82 others — read 11 August 2026
Хуевое Запорожье | Запоріжжя @huevoe_zaporozhye · 24,072 Telegram ranks this channel #33 of 80 here — alongside 79 others — read 17 September 2026
ЗАПОРІЗЬКА СІЧ @zaporizka_sish · 25,946 Telegram ranks this channel #36 of 81 here — alongside 80 others — read 13 September 2026
🇺🇦Запоріжжя Новини🇺🇦Запорожье Новости @etozp · 74,374 Telegram ranks this channel #36 of 88 here — alongside 87 others — read 19 August 2026
Славне Запоріжжя 🇺🇦 | Світло @slavne_zaporizhia · 22,622 Telegram ranks this channel #39 of 81 here — alongside 80 others — read 20 September 2026
Запоріжжя ⚡️Новини @zaporozhye_insider · 22,597 Telegram ranks this channel #41 of 87 here — alongside 86 others — read 20 September 2026
АТ "Запоріжжяобленерго" @Zaporizhzhyaoblenergo_news · 86,675 Telegram ranks this channel #44 of 83 here — alongside 82 others — read 17 August 2026
Типичное Запорожье @typzp · 22,180 Telegram ranks this channel #48 of 81 here — alongside 80 others — read 21 September 2026
monitorsmu @monitorsmy · 23 Telegram ranks this channel #48 of 81 here — alongside 80 others — read 27 August 2026
БЕЗ БАЙДИ @bezbaidy · 61,508 Telegram ranks this channel #49 of 86 here — alongside 85 others — read 22 August 2026
5 РЕДАКЦІЯ | Новини Запоріжжя @five_redakcia · 24,910 Telegram ranks this channel #55 of 83 here — alongside 82 others — read 15 September 2026
This channel appears in 22 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this
entry's latest reading, not the date you are reading this.
“▵ Очі Всюди | Дніпро ▵” (@eyes_everywhere_dnipro), 13,170 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/eyes_everywhere_dnipro.
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.