Telegram RegisterThe public register of Telegram

Channel

Дніпро Alerts 🚀 🚨

@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.

Register entry

Telegram ID-1001699010379
TypeChannel
Username@dnipro_alerts
Description❗️РЕКЛАМУ НЕ ПРОДАЄМ❗️ ❗️ВЗАЄМНОЮ(🏳️‍🌈) РЕКЛАМОЮ НЕ ЗАЙМАЄМОСЬ ❗️ Для зв'язку @fireworker_support_bot 💵 Підтримка ЗСУ через наш канал 👇: 💵 USDT(TRC20) TPL63BmKhEJMiRPUAdSLkAcPzCJEsYw3dD
Created4 December 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/dnipro_alerts

Topic

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.

Growth

802,271803,332802,801.56 August 2026 — 802,271 subscribers7 August 2026 — 802,612 subscribers8 August 2026 — 802,712 subscribers9 August 2026 — 802,761 subscribers10 August 2026 — 802,697 subscribers11 August 2026 — 803,124 subscribers12 August 2026 — 803,332 subscribers13 August 2026 — 803,214 subscribers803,2146 August 202613 August 2026
8 measurements spanning 7 days, net +943. 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 802,112–803,491 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 03:38803,214-118
12 Aug 2026, 02:12803,332+208
11 Aug 2026, 03:05803,124+427
10 Aug 2026, 04:35802,697-64
9 Aug 2026, 02:51802,761+49
8 Aug 2026, 00:14802,712+100
7 Aug 2026, 01:10802,612+341
6 Aug 2026, 06:37802,271first reading

Engagement

443 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 29 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
17.5%
avg views ÷ 803,214 subscribers
Avg views / post
141,000
443 posts measured
Reaction rate
1.38%
reactions ÷ views · ER floor
Posts in window
443
of 443 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 held443 (6 August 202613 August 2026)
Views total62,389,950
Reactions total859,573
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 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.

What this channel posts

Photos
45
Videos
18
Links
18,400

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.

View velocity

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.

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/514026 Aug 2026, 19:43 UTC117 minutes17 minutes old50,300 views ~1,518 reactionsno checkpoint reading yetnot yet at 24hnot measurable yet
/514016 Aug 2026, 19:32 UTC128 minutes28 minutes old76,500 views ~1,739 reactionsno checkpoint reading yetnot yet at 24hnot measurable yet
/514006 Aug 2026, 19:26 UTC24 minutes34 minutes old90,500 views ~1,588 reactionsno checkpoint reading yetnot yet at 24h13 minutesprovisional — final view count still climbing
/513996 Aug 2026, 19:17 UTC213 minutes43 minutes old97,600 views ~1,487 reactionsno checkpoint reading yetnot yet at 24h14 minutesprovisional — final view count still climbing
/513986 Aug 2026, 19:09 UTC221 minutes51 minutes old108,000 views ~1,854 reactionsno checkpoint reading yetnot yet at 24h21 minutesupper bound — already past half at first reading · provisional — final view count still climbing
/513976 Aug 2026, 18:56 UTC34 minutes64 minutes old125,000 views ~2,280 reactions60 minutes: 120,790 interp.still climbing at last readingnot yet at 24h20 minutesprovisional — final view count still climbing
/513966 Aug 2026, 18:52 UTC37 minutes68 minutes old126,000 views ~1,708 reactions60 minutes: 119,893 interp.still climbing at last readingnot yet at 24h18 minutesprovisional — final view count still climbing
/513956 Aug 2026, 18:48 UTC312 minutes72 minutes old124,000 views ~1,524 reactions60 minutes: 116,177 interp.still climbing at last readingnot yet at 24h16 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.

Reaction mix

828,225 reactions across 423 posts, in 22 distinct kinds. The most used accounts for 75.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏626,89575.7%
🤬122,01314.7%
43,6305.27%
👍7,8240.945%
😢6,1050.737%
💩5,3730.649%
🤯4,3660.527%
😱3,2700.395%
😨1,0650.129%
👌9420.114%
🤔9420.114%
🥴8380.101%
🤨8090.098%
👏7740.093%
🤝7350.089%
👎6980.084%
🤮5150.062%
custom 53932678460777515704650.056%
🫡3580.043%
💔2730.033%
2 further kinds3350.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.

Telegram Stars

Stars received
2,015
across the posts below
Posts paid on
120
of 443 we hold a reading for · 27%
Most on one post
960
single highest reading

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.

Recent posts

13 Aug 2026, 22:16 UTC≈138,000 views2,619 reactionsread 14 August 2026

🦔 Відбій по районам області, окрім прифронтових. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок

🙏2,180308👍92💩15🤬11🫡7🤝6

13 Aug 2026, 21:38 UTC≈148,000 views1,983 reactionsread 14 August 2026

Без наявних загроз 🟨

🙏1,660202👍58🤬21🤔12💩11🤯7👏6

13 Aug 2026, 21:20 UTC≈155,000 views1,680 reactions1 Starread 14 August 2026

Додатково реактивний від Шахтарське у західному напрямку. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок

🙏1,260🤬31449😱20💩13😢12👎6👏6

13 Aug 2026, 21:16 UTC≈151,000 views1,409 reactions2 Starsread 14 August 2026

Нові реактивні дрони зі сходу тим же маршрутом. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок

🙏1,030🤬27537😢29😱16💩13🤯5👌4

13 Aug 2026, 21:11 UTC≈138,000 views1,337 reactionsread 14 August 2026

Далі в бік Перещепине. Відповідно тривожиться Самарівський район. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок

🙏1,030🤬24030😢22😨10👎4💩1

13 Aug 2026, 21:08 UTC≈132,000 views1,184 reactionsread 14 August 2026

Напрямок в бік Юріївка з південного сходу. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок

🙏901🤬21325🤯15😢15💩10😨5

13 Aug 2026, 21:05 UTC≈130,000 views1,220 reactionsread 14 August 2026

Павлоград превентивно жовтогарячий 🟧 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок

🙏977🤬18632😱14💩6🤯5

13 Aug 2026, 21:02 UTC≈124,000 views1,306 reactionsread 14 August 2026

Кілька реактивних дронів на північному сході від Петропавлівка, напрямок руху станом на зараз - північно-західний. Слідкуємо. На це тривожиться Павлоградський район 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок

🙏987🤬23843💩13😢12👎9😨4

13 Aug 2026, 20:12 UTC≈130,000 views1,802 reactionsread 14 August 2026

🦔 відбій локальних тривог. Лишається Синельниківський на прифронтову активність. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок

🙏1,530155🤬49👍32😢20🤝6💩5💔4

13 Aug 2026, 20:01 UTC≈136,000 views1,773 reactionsread 14 August 2026

+ пара дронів зі сходу в бік Петропавлівка. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок

🙏1,320🤬35837😨17😢16💩7👎6👏6

13 Aug 2026, 19:47 UTC≈144,000 views2,110 reactionsread 14 August 2026

КАБи в район Васильківка/Письменне 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок

🙏1,460🤬503😢7646💩7👍6🤔5💔4

13 Aug 2026, 19:32 UTC≈148,000 views2,106 reactions1 Starread 14 August 2026

Область жовтий 🟨. 💙 Дніпро Alerts • 💛 Київ Alerts ℹ️ Alerts Live • 🤙 Зворотний зв’язок

🙏1,770231👍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

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.

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 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.

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.

Channels Telegram recommends alongside this one

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.

ХДніпро 🇺🇦
@hyevuy_dnepr · 520,427
#1
НУ І ДНІПРО! 🇺🇦
@ny_i_dnipro · 269,535
#2
Включатель Днепр⚡️
@vklyuchatel_dnepr_svet · 180,842
#3
Лачен пише
@lachentyt · 1,564,018
#4
‼️СИРЕНА. ДНІПРО‼️
@sirena_dp · 233,158
#5
Дніпро Оперативний 🇺🇦| Війна
@dnepr_operativ · 315,731
#6
Труха⚡️Дніпро | Новини
@truexadnepr · 361,444
#7
monitor
@war_monitor · 965,383
#8
Дніпро ОПЕРАТИВНИЙ 🇺🇦
@dneproperatyv · 186,212
#9
Труха⚡️Україна
@truexanewsua · 3,167,401
#10
Всевидящее ОКО: Україна | Політика
@oko_ua · 1,146,705
#11
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 895,312
#12
Хуевый Днепр | Дніпро
@huevyi_dnepr · 166,271
#13
HKR
@hyevuy_k_r · 151,936
#14
Kyiv Alerts 🚀 🚨
@kyiv_alerts · 54,538
#15
Україна Сейчас | УС: новини, політика
@u_now · 1,406,695
#16
ДС: новини Дніпро
@dnipro_now · 119,777
#17
Бавовна
@ukrbavovna · 644,264
#18
Дніпро Аварійна служба (Світло | Графіки)
@avariykaaa · 78,787
#19
INSIDER UA
@insiderukr · 2,169,456
#20
Реальна Війна | Україна | Новини
@voynareal · 1,520,174
#21
На повестке Днепр
@napovestkeDn · 59,526
#22
STERNENKO
@ssternenko · 895,824
#23
Карта повітряних тривог 🇺🇦
@alarmua · 930,854
#24
Україна Online: Новини | Політика
@UaOnlii · 1,561,051
#25
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 713,956
#26
Куди летить? | Тривога
@radar_raketaa · 501,969
#27
✙DeepState✙🇺🇦
@deepstateua · 765,490
#28
Дніпровський пише
@dnipro_pishet · 52,747
#29
‼️СИРЕНА‼️Кривий Ріг ОФІЦІЙНИЙ
@sirena_kryvyi_rih · 129,606
#30
Інформатор Дніпро
@dp_informator_ua · 48,062
#31
Говорять Снайпер ꑭ
@stanislav_osman · 293,106
#32
Радар⚡️Дніпро
@RadarDnepr · 15,442
#33
Реальний Київ | Украина
@kievreal1 · 1,535,796
#34
Доброго вечора, ми з Дніпра👋🏻
@we_from_dnipro · 87,252
#35
∆✙🍒Гнила черешня🇺🇦✙∆
@gnilayachereha · 428,891
#36
ДТЕК - офіційний канал
@dtek_ua · 443,708
#37
ТИПОВИЙ КРИВИЙ РІГ
@typical_KR · 102,261
#38
НУ І КРИВИЙ РІГ
@ny_i_kryvyi_rih · 9,865
#39
Чому тривога | Радар
@raketa_trevoga · 486,155
#40
Труха⚡️Кривий Ріг
@truexakrivojrog · 146,843
#41
ХПобеда 🇺🇦
@hyevaya_pobeda · 12,275
#42
NEWS.GRP🇺🇦
@newsgrpua · 119,856
#43
monitoring
@monitorwarr · 86,053
#44
🔊⚠️єРадар | Повітряна тривога | Ракетна небезпека
@eRadarrua · 375,498
#45
Камʼянське Аварійка (Світло | Графіки)
@avariyka_kam · 50,628
#46
Аварійка Дніпро Світло
@svet_dnepr_sveta · 14,273
#47
Радар⚡️Запоріжжя
@radar_zaporizhzhya · 96,433
#48
🇺🇦Оборона Кривбасу
@pvoukraine7 · 36,035
#49
Український Наступ | #УкрТг ∆
@ukrnastup · 129,602
#50
Pavlograd_now | 24/7 Павлоград Терновка Першотравенск
@pavlograd_now · 92,613
#51
Хуйовий Харків 🇺🇦 Хуевый Харьков
@huyovy_kharkiv · 466,154
#52
Дніпро Обласний🔝
@dniprooblcentr · 32,083
#53
Николаевский Ванёк
@vanek_nikolaev · 2,668,273
#54
Где повестки Днепр?
@agendaDnepr · 322,244
#55
СВОЇ | Кривий Ріг
@svoiKR · 266,774
#56
Скринька Пандори
@pandoras_box_ua · 159,021
#57
ОГо!
@OGoMono · 663,052
#58
Всевидящее ОКО 18 ✙
@oko18_ukr · 307,382
#59
Сірий Кріт
@seryy_krot99 · 34,329
#60
Борис Філатов
@borys_filatovv · 79,407
#61
✙ 🔼Вертикаль
@vert2026 · 120,560
#62
Батальйон «Монако» | Україна | Новини
@batalionmonako · 716,693
#63
Это Кривой Рог, ДЕТКА😈
@ekrd_glavniy · 115,483
#64
Повестки Днепр
@povestki_dnepr_TSK · 37,376
#65
«Менора» USDT / BTC
@Menora_Crypto · 5,827
#66
ОБМІН ВАЛЮТ «МЕНОРА»
@Vkurse_dp_ua · 9,052
#67
KostyaKudo
@Konstantin_Kudo_Cryptology · 50,557
#68
NEXTA Live
@nexta_live · 761,857
#69
Бахмутський Демон 👹
@bahshiddemon · 171,897
#70
Хуевая Одесса
@xydessa · 948,070
#71
Обмін валют «Менора» 💵💶💷💴
@MenorahObmen · 28,562
#72
Аренда Квартир Днепр
@doroshenkodenis · 3,567
#73
Бро скинув мем
@bromeeems · 318,816
#74
Namomente Crypto
@namomente_crypto · 9,668
#75
Алексей Шевцов
@jolybells · 359,908
#76
arenda_novostroi_dnepr
@arenda_novostroi_dnepr · 1,443
#77
001k.Trade
@trade001k · 108,538
#78

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.

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.

ДС: новини Дніпро
@dnipro_now · 119,777
Telegram ranks this channel #1 of 86 here — alongside 85 others — read 14 August 2026
Хуевый Днепр | Дніпро
@huevyi_dnepr · 166,271
Telegram ranks this channel #1 of 82 here — alongside 81 others — read 12 August 2026
Включатель Днепр⚡️
@vklyuchatel_dnepr_svet · 180,842
Telegram ranks this channel #1 of 69 here — alongside 68 others — read 12 August 2026
Дніпро ОПЕРАТИВНИЙ 🇺🇦
@dneproperatyv · 186,212
Telegram ranks this channel #1 of 82 here — alongside 81 others — read 11 August 2026
‼️СИРЕНА. ДНІПРО‼️
@sirena_dp · 233,158
Telegram ranks this channel #1 of 75 here — alongside 74 others — read 11 August 2026
НУ І ДНІПРО! 🇺🇦
@ny_i_dnipro · 269,535
Telegram ranks this channel #1 of 72 here — alongside 71 others — read 10 August 2026
Дніпро Оперативний 🇺🇦| Війна
@dnepr_operativ · 315,731
Telegram ranks this channel #1 of 81 here — alongside 80 others — read 10 August 2026
Труха⚡️Дніпро | Новини
@truexadnepr · 361,444
Telegram ranks this channel #1 of 79 here — alongside 78 others — read 10 August 2026
ХДніпро 🇺🇦
@hyevuy_dnepr · 520,427
Telegram ranks this channel #1 of 81 here — alongside 80 others — read 9 August 2026
‼️СИРЕНА‼️Кривий Ріг ОФІЦІЙНИЙ
@sirena_kryvyi_rih · 129,606
Telegram ranks this channel #3 of 71 here — alongside 70 others — read 13 August 2026
HKR
@hyevuy_k_r · 151,936
Telegram ranks this channel #3 of 75 here — alongside 74 others — read 12 August 2026
Труха⚡️Кривий Ріг
@truexakrivojrog · 146,843
Telegram ranks this channel #6 of 80 here — alongside 79 others — read 13 August 2026
АстроОберег
@astroobere · 265,354
Telegram ranks this channel #7 of 67 here — alongside 66 others — read 12 August 2026
Волхва України Ольга Берлінська
@VolxvaUkrain · 165,776
Telegram ranks this channel #7 of 78 here — alongside 77 others — read 12 August 2026
Чому тривога | Радар
@raketa_trevoga · 486,155
Telegram ranks this channel #10 of 85 here — alongside 84 others — read 9 August 2026
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 713,956
Telegram ranks this channel #10 of 85 here — alongside 84 others — read 8 August 2026
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 895,312
Telegram ranks this channel #10 of 87 here — alongside 86 others — read 8 August 2026
ДТЕК - офіційний канал
@dtek_ua · 443,708
Telegram ranks this channel #11 of 90 here — alongside 89 others — read 10 August 2026
monitor
@war_monitor · 965,383
Telegram ranks this channel #11 of 87 here — alongside 86 others — read 8 August 2026
Повітряний простір | Напрямок ракет
@ukraine_pyxx · 187,399
Telegram ranks this channel #12 of 59 here — alongside 58 others — read 13 August 2026
Где повестки Днепр?
@agendaDnepr · 322,244
Telegram ranks this channel #12 of 70 here — alongside 69 others — read 10 August 2026
Куди летить? | Тривога
@radar_raketaa · 501,969
Telegram ranks this channel #12 of 86 here — alongside 85 others — read 9 August 2026
Карта повітряних тривог 🇺🇦
@alarmua · 930,854
Telegram ranks this channel #12 of 87 here — alongside 86 others — read 8 August 2026
Де Ракета ?🚀 | Моніторинг
@deraketaua · 154,100
Telegram ranks this channel #15 of 81 here — alongside 80 others — read 12 August 2026

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.

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.

“Дніпро 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.