Telegram RegisterThe public register of Telegram

Channel

Дніпро Головний 🇺🇦

@dnipromonitor

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

37,302subscribers

+368 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002413674705
TypeChannel
Username@dnipromonitor
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/dnipromonitor

Growth

36,93437,30237,1187 August 2026 — 36,934 subscribers7 August 2026 — 36,934 subscribers8 August 2026 — 36,987 subscribers9 August 2026 — 37,018 subscribers10 August 2026 — 37,065 subscribers11 August 2026 — 37,143 subscribers12 August 2026 — 37,281 subscribers13 August 2026 — 37,302 subscribers7 August 202613 August 2026
8 measurements spanning 6 days, net +368. 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 36,879–37,357 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 10:2637,302+21
12 Aug 2026, 11:0537,281+138
11 Aug 2026, 10:4637,143+78
10 Aug 2026, 12:3137,065+47
9 Aug 2026, 09:5337,018+31
8 Aug 2026, 12:4736,987+53
7 Aug 2026, 14:3036,934no change
7 Aug 2026, 14:2136,934first reading

Engagement

169 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
39.3%
avg views ÷ 37,302 subscribers
Avg views / post
14,700
169 posts measured
Reaction rate
2.95%
reactions ÷ views · ER floor
Posts in window
169
of 169 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 13 August 2026
Posts held169 (6 August 202613 August 2026)
Views total2,476,380
Reactions total73,027
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 09:19 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

73,027 reactions across 169 posts, in 10 distinct kinds. The most used accounts for 70.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏51,76470.9%
12,76717.5%
🤬5,8317.98%
👀9411.29%
👍7831.07%
🫡3300.452%
😴2580.353%
🤯2350.322%
💔790.108%
🗿390.053%

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

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

Telegram Stars

Stars received
19
across the posts below
Posts paid on
8
of 169 we hold a reading for · 5%
Most on one post
10
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dnipromonitor. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 169 most recent posts we hold for this entry, published 6 August 2026 to 13 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

13 Aug 2026, 05:51 UTC≈8,830 views460 reactionsread 13 August 2026

⚡️по тривозі без загроз для нас. Там на окупованій частині Запорізької області пе ве о. Все добре.

🙏37475🫡8😴3

13 Aug 2026, 00:15 UTC≈12,900 views404 reactionsread 13 August 2026

Спіть 😴😴😴

🙏29898👍5💔2😴1

13 Aug 2026, 00:01 UTC≈13,700 views522 reactionsread 13 August 2026

⚡️підтверджено роботу пе ве о русні в Ростовській області. Там наші дрони. Були виходи С-400, не Іскандер. Зранку мають бути там гарні новини ☺️ Очікуємо відбій і спіть😴 @dnipromonitor

🙏389122🫡9🤬2

12 Aug 2026, 23:54 UTC≈14,200 views429 reactionsread 13 August 2026

❗️тривога через балістику з Шахт, Ростовська область. Там ППО по наших дронах, але уважно хв 10. Скажу. @dnipromonitor

🙏38626👀9🫡5😴3

12 Aug 2026, 21:19 UTC≈14,900 views484 reactionsread 13 August 2026

⚡️такс, ну поки можу сказати «спимо». Передумов для немає 😴 Штук х15 на Одещину, два на Запоріжжя. Це все, що є зараз. Якщо щось зміниться — скажу.

🙏41852👀6🫡5😴3

12 Aug 2026, 20:11 UTC≈15,900 views556 reactionsread 13 August 2026

ℹ️ Обстановка на 23:00. ⚠️ Стратегічна авіація не активна. Без злетів. Передумов немає сьогодні. ⚠️по шахедах — були пуски з кількох локацій. Масованих наразі немає. На Сумщині штук х10 і кілька на Павлоград. Там і падають. ❗️ по флоту — не в морі. ❗️ по балістиці вище середнього рівень небезпеки. Як і було — попередження по Києву. @dnipromonitor

🙏49841👀9🫡5🤯3

12 Aug 2026, 19:00 UTC≈16,200 views436 reactionsread 13 August 2026

Такс, по-перше, добрий вечір ❤️ По-друге, бачу у вас є питання знову. Давайте говорити 🫵🏻

🙏31887👀20👍6🗿3🤯1🫡1

12 Aug 2026, 18:23 UTC≈16,100 views439 reactionsread 13 August 2026

💥 по мопеду чисто, область без мопедів. Відпочивайте ❤️

🙏35578😴4👍2

12 Aug 2026, 18:09 UTC≈16,500 views486 reactionsread 13 August 2026

⚡️якщо шо, мопед пішов в область. Ні на який Дніпро він не крутить. Пішов на Солоне🚬

🙏41737👀14🤬13🫡3😴2

12 Aug 2026, 18:00 UTC≈16,600 views638 reactionsread 13 August 2026

ℹ️ Обстановка на 21:00. ⚠️ Стратегічна авіація не активна. Без злетів. Передумов немає, але потроху споряджаються і готуються. ⚠️по шахедах — були пуски з кількох локацій. Масованих наразі немає. Пуски були нижче середнього. ❗️ по флоту — не в морі. ❗️ по балістиці вище середнього рівень небезпеки. Знову на ніч попередження для Києва та області. По нам попереджень, як мінімум поки, не було. @dnipromonitor

🙏54169👀17👍8😴2🫡1

12 Aug 2026, 17:42 UTC≈16,300 views488 reactionsread 13 August 2026

⚠️ тривога на мопед від Криворіжжя на Кринички/Камʼянський район. Дніпро превентивно і без загроз.

🙏420🤬34👀1611🫡6😴1

12 Aug 2026, 16:38 UTC≈16,600 views525 reactionsread 13 August 2026

💥 мопед мінус, Дніпро та Камʼянське чисто. Відпочиваємо ❤️

🙏39797👍27👀3🫡1

Showing the 12 most recent of 169 posts we hold for @dnipromonitor. 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 — 242,047 of 1,169,250entries 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.

Mentions

Named by 5 registered channels — 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.

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.

“Дніпро Головний 🇺🇦” (@dnipromonitor), 37,302 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/dnipromonitor.

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.