🦔 Відбій по районам області, окрім прифронтових. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок
🙏2,180❤308👍92💩15🤬11🫡7🤝6

Channel
@dnipro_alerts
On this record: Topic · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
803,214subscribers
+943 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 316,228–1,000,000.
| Telegram ID | -1001699010379 |
|---|---|
| Type | Channel |
| Username | @dnipro_alerts |
| Description | ❗️РЕКЛАМУ НЕ ПРОДАЄМ❗️ ❗️ВЗАЄМНОЮ(🏳️🌈) РЕКЛАМОЮ НЕ ЗАЙМАЄМОСЬ ❗️ Для зв'язку @fireworker_support_bot 💵 Підтримка ЗСУ через наш канал 👇: 💵 USDT(TRC20) TPL63BmKhEJMiRPUAdSLkAcPzCJEsYw3dD |
| Created | 4 December 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/dnipro_alerts |
National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 74% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 03:38 | 803,214 | -118 |
| 12 Aug 2026, 02:12 | 803,332 | +208 |
| 11 Aug 2026, 03:05 | 803,124 | +427 |
| 10 Aug 2026, 04:35 | 802,697 | -64 |
| 9 Aug 2026, 02:51 | 802,761 | +49 |
| 8 Aug 2026, 00:14 | 802,712 | +100 |
| 7 Aug 2026, 01:10 | 802,612 | +341 |
| 6 Aug 2026, 06:37 | 802,271 | first reading |
443 posts held, back to 6 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 29 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 13 August 2026 |
|---|---|
| Posts held | 443 (6 August 2026 – 13 August 2026) |
| Views total | 62,389,950 |
| Reactions total | 859,573 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 06:02 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.
Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /514026 Aug 2026, 19:43 UTC | 117 minutes – 17 minutes old | 50,300 views ~1,518 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /514016 Aug 2026, 19:32 UTC | 128 minutes – 28 minutes old | 76,500 views ~1,739 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /514006 Aug 2026, 19:26 UTC | 24 minutes – 34 minutes old | 90,500 views ~1,588 reactions | no checkpoint reading yet | not yet at 24h | 13 minutesprovisional — final view count still climbing |
| /513996 Aug 2026, 19:17 UTC | 213 minutes – 43 minutes old | 97,600 views ~1,487 reactions | no checkpoint reading yet | not yet at 24h | 14 minutesprovisional — final view count still climbing |
| /513986 Aug 2026, 19:09 UTC | 221 minutes – 51 minutes old | 108,000 views ~1,854 reactions | no checkpoint reading yet | not yet at 24h | 21 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /513976 Aug 2026, 18:56 UTC | 34 minutes – 64 minutes old | 125,000 views ~2,280 reactions | 60 minutes: 120,790 interp.still climbing at last reading | not yet at 24h | 20 minutesprovisional — final view count still climbing |
| /513966 Aug 2026, 18:52 UTC | 37 minutes – 68 minutes old | 126,000 views ~1,708 reactions | 60 minutes: 119,893 interp.still climbing at last reading | not yet at 24h | 18 minutesprovisional — final view count still climbing |
| /513956 Aug 2026, 18:48 UTC | 312 minutes – 72 minutes old | 124,000 views ~1,524 reactions | 60 minutes: 116,177 interp.still climbing at last reading | not yet at 24h | 16 minutesprovisional — final view count still climbing |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed viewsis the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
828,225 reactions across 423 posts, in 22 distinct kinds. The most used accounts for 75.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🙏 | 626,895 | 75.7% | |
| 🤬 | 122,013 | 14.7% | |
| ❤ | 43,630 | 5.27% | |
| 👍 | 7,824 | 0.945% | |
| 😢 | 6,105 | 0.737% | |
| 💩 | 5,373 | 0.649% | |
| 🤯 | 4,366 | 0.527% | |
| 😱 | 3,270 | 0.395% | |
| 😨 | 1,065 | 0.129% | |
| 👌 | 942 | 0.114% | |
| 🤔 | 942 | 0.114% | |
| 🥴 | 838 | 0.101% | |
| 🤨 | 809 | 0.098% | |
| 👏 | 774 | 0.093% | |
| 🤝 | 735 | 0.089% | |
| 👎 | 698 | 0.084% | |
| 🤮 | 515 | 0.062% | |
| custom 5393267846077751570 | 465 | 0.056% | |
| 🫡 | 358 | 0.043% | |
| 💔 | 273 | 0.033% | |
| 2 further kinds | 335 | 0.04% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.
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 443 of the 443 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 859,573reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 443 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dnipro_alerts. 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 443 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.
🦔 Відбій по районам області, окрім прифронтових. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок
🙏2,180❤308👍92💩15🤬11🫡7🤝6
Без наявних загроз 🟨
🙏1,660❤202👍58🤬21🤔12💩11🤯7👏6
Додатково реактивний від Шахтарське у західному напрямку. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок
🙏1,260🤬314❤49😱20💩13😢12👎6👏6
Нові реактивні дрони зі сходу тим же маршрутом. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок
🙏1,030🤬275❤37😢29😱16💩13🤯5👌4
Далі в бік Перещепине. Відповідно тривожиться Самарівський район. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок
🙏1,030🤬240❤30😢22😨10👎4💩1
Напрямок в бік Юріївка з південного сходу. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок
🙏901🤬213❤25🤯15😢15💩10😨5
Павлоград превентивно жовтогарячий 🟧 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок
🙏977🤬186❤32😱14💩6🤯5
Кілька реактивних дронів на північному сході від Петропавлівка, напрямок руху станом на зараз - північно-західний. Слідкуємо. На це тривожиться Павлоградський район 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок
🙏987🤬238❤43💩13😢12👎9😨4
🦔 відбій локальних тривог. Лишається Синельниківський на прифронтову активність. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок
🙏1,530❤155🤬49👍32😢20🤝6💩5💔4
+ пара дронів зі сходу в бік Петропавлівка. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок
🙏1,320🤬358❤37😨17😢16💩7👎6👏6
КАБи в район Васильківка/Письменне 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок
🙏1,460🤬503😢76❤46💩7👍6🤔5💔4
Область жовтий 🟨. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок
🙏1,770❤231👍75💩11🤔10🤬9
Showing the 12 most recent of 443 posts we hold for @dnipro_alerts. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 25,418 of 1,189,255entries 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.
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.
Named by 9 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
Telegram’s own answer, not this register’s.When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 8 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 66 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“Дніпро Alerts 🚀 🚨” (@dnipro_alerts), 803,214 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/dnipro_alerts.
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.