Telegram RegisterThe public register of Telegram
Telegram profile photo for Дніпровський пише

Channel

Дніпровський пише

@dnipro_pishet

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

52,273subscribers

-559 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-1001865286185
TypeChannel
Username@dnipro_pishet
DescriptionЗвʼязок- @Dnipro_pishet_bot
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/dnipro_pishet

Topic

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 7 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@kramatorskiy_pishet/908357 Aug 2026, 08:10 UTC@dnipro_pishet/77378 · this entry7 Aug 2026, 08:10 UTC1.00under a minute
@kramatorskiy_pishet/9111213 Aug 2026, 18:30 UTC@dnipro_pishet/77592 · this entry13 Aug 2026, 18:30 UTC1.00under a minute
@kramatorskiy_pishet/9111313 Aug 2026, 19:30 UTC@dnipro_pishet/77593 · this entry13 Aug 2026, 19:30 UTC1.00under a minute
@kramatorskiy_pishet/9134119 Aug 2026, 17:30 UTC@dnipro_pishet/77756 · this entry19 Aug 2026, 17:30 UTC1.00under a minute
@kramatorskiy_pishet/9134519 Aug 2026, 19:30 UTC@dnipro_pishet/77758 · this entry19 Aug 2026, 19:30 UTC1.00under a minute
@kramatorskiy_pishet/9140120 Aug 2026, 19:30 UTC@dnipro_pishet/77781 · this entry20 Aug 2026, 19:30 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@kramatorskiy_pishet12 (8/8 hand-verifiable sample passed)1.00under a minute@kramatorskiy_pishet (11–1)
@suspilnednipro12 (8/8 hand-verifiable sample passed)0.9672 seconds@suspilnednipro (12–0)
@dniprotv9 (8/8 hand-verifiable sample passed)0.9872 seconds@dniprotv (9–0)
@fan_avrora7 (7/7 hand-verifiable sample passed)1.00under a minutethis entry (4–3)
@kharkiv_pishet5 (5/5 hand-verifiable sample passed)1.00under a minute@kharkiv_pishet (3–2)
@Dnepr_ppo5 (5/5 hand-verifiable sample passed)0.9817 minutes@Dnepr_ppo (3–2)
@pokrovsk_operativv5 (5/5 hand-verifiable sample passed)0.98under a minute@pokrovsk_operativv (4–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 45 of the 45 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 953 comparable posts for this entry, running 6 August 2026 to 15 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the keys clone_copy · clone_mutual, last confirmed 16 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

52,22752,83252,529.552,2737 August 202616 November 2026
65 measurements spanning 101 days, net -559. 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 52,136–52,923 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
16 Nov 2026, 01:0152,273-59
12 Nov 2026, 14:1552,332+35
10 Nov 2026, 09:0052,297-2
8 Nov 2026, 18:0952,299-18
7 Nov 2026, 08:1652,317-3
6 Nov 2026, 09:2652,320+29
5 Nov 2026, 12:5052,291-8
4 Nov 2026, 11:4752,299+21
3 Nov 2026, 11:3952,278+51
2 Nov 2026, 08:2752,227-22
1 Nov 2026, 07:5752,249-21
31 Oct 2026, 07:0652,270-20
30 Oct 2026, 06:4452,290-24
29 Oct 2026, 05:0852,314-17
28 Oct 2026, 00:5652,331-13
27 Oct 2026, 03:5552,344-9
26 Oct 2026, 05:0152,353-10
25 Oct 2026, 01:3752,363-17
24 Oct 2026, 02:5552,380-23
23 Oct 2026, 00:0952,403first reading

Engagement

1,594 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 210 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
14.8%
avg views ÷ 52,273 subscribers
Avg views / post
7,720
578 posts measured
Reaction rate
0.898%
reactions ÷ views · ER floor
Posts in window
578
of 1,594 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. It is computed over the 577 of 578 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 November 2026
Posts held1,594 (6 August 2026 – 15 November 2026)
Views total4,464,780
Reactions total40,087
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 04:31 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
578
Videos
111
Links
633

Lifetime counters from Telegram’s own channel header, read 16 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
6h 01m
Average length
2m 30s

Measured directly from 145 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

72,438 reactions across 999 posts, in 23 distinct kinds. The most used accounts for 29.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏21,63029.9%
😢19,85027.4%
🤬19,19926.5%
❤3,6495.04%
😭2,2293.08%
👍1,6292.25%
👎1,2211.69%
😁8911.23%
🙈4560.63%
🔥3410.471%
💔3300.456%
👀2650.366%
😨2450.338%
💯1890.261%
🤩1130.156%
🌚760.105%
🥰610.084%
🍾330.046%
❤‍🔥130.018%
🐳80.011%
3 further kinds100.014%

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 999 of the 1,000 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 72,438 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 17 September 2026 to 15 November 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
6
across the posts below
Posts paid on
4
of 1,000 we hold a reading for · 0.4%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dnipro_pishet. 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 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 17 September 2026 to 15 November 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

Telegram’s own ‘edited’ marker: 1 of 578 posts held from the last 30 days (0.173%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

15 Nov 2026, 21:23 UTC≈4,580 views71 reactionsread 16 November 2026

⚡Дніпро - вибухи Підписатись на Дніпровського

🙏47🤬18😢5❤1

15 Nov 2026, 21:07 UTC≈5,690 views71 reactionsread 16 November 2026

⚡ Тернівка. вибух. Підписатись на Дніпровського

🙏45🤬14😢12

15 Nov 2026, 20:01 UTC≈7,900 views141 reactionsread 16 November 2026

⚡ Павлоград. Ще один вибух. Вже 5 за останні 5 хвилин

🙏80🤬49😢7❤3😁2

15 Nov 2026, 20:00 UTC≈8,060 views83 reactionsread 16 November 2026

⚡ Павлоград. Ще 2 сильних вибухи. Ворог атакує місто ударними БПЛА

🙏51🤬23😢7👍1🔥1

15 Nov 2026, 19:58 UTC≈8,100 views65 reactionsread 16 November 2026

⚡ Павлоград. Ще один сильний вибух пролунав щойно

🙏35🤬23😢7

15 Nov 2026, 19:56 UTC≈8,160 views58 reactionsread 16 November 2026

⚡ Павлоград. Вибух. Атака БПЛА Підписатись на Дніпровського

🤬29🙏22😢5❤2

15 Nov 2026, 19:55 UTC≈8,460 views61 reactionsread 16 November 2026

⚡ Шахтарське. Повідомляють, що вже четвертий вибух пролунав.

🙏35😢18❤4👍2🤬2

15 Nov 2026, 19:43 UTC≈8,180 views66 reactionsread 16 November 2026

⚡Вибух в Дніпрі Підписатись на Дніпровського

🙏45🤬14😢4❤3

15 Nov 2026, 19:42 UTC≈7,880 views64 reactionsread 16 November 2026

⚡ Шахтарське. Ще один вибух.

🙏44🤬17😢2😁1

15 Nov 2026, 19:41 UTC≈7,690 views58 reactionsread 16 November 2026

⚡ Шахтарське. Повідомляють про вибух. Підписатись на Дніпровського

🙏38🤬14❤2😁2😢2

15 Nov 2026, 19:26 UTC≈7,590 views47 reactionsread 16 November 2026
Video

⚡У селищі Солоне п'яний водій влетів у двір і пошкодив будинок Аварія сталася під час комендантської години. За словами місцевих жителів, за кермом був 23–24-річний хлопець із 2,1 проміле алкоголю в крові. Унаслідок ДТП знесло паркан і пошкодило частину будинку. Мешканці вимагають, щоб винний відповів за завдані збитки. Підписатись на Дніпровського

😨29🤬14❤4

15 Nov 2026, 19:16 UTC≈6,580 views52 reactionsread 16 November 2026

⚡З вересня Дніпропетровщина пережила найбільше ударів РФ серед усіх регіонів. Було зафіксовано 131 влучання, повідомив президент Зеленський під час вечірнього звернення. Підписатись на Дніпровського

😢40🤬8❤4

Showing the 12 most recent of 1,594 posts we hold for @dnipro_pishet. 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.

Posts edited after publishing

@dnipro_pishet edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
10 November 2026
Most recent edit
10 November 2026

Posts recorded as deleted after publishing

We recorded 6 posts on @dnipro_pishet as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
31 August 2026
Most recent seen missing
17 October 2026
Median time before seen missing
29 hours
Seen missing in the last 30 days
0

Mentions

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.

Включатель Днепр⚡️
@vklyuchatel_dnepr_svet · 197,131
#1
Дніпро Alerts 🚀 🚨
@dnipro_alerts · 809,443
#2
ХДніпро 🇺🇦
@hyevuy_dnepr · 520,760
#3
НУ І ДНІПРО! 🇺🇦
@ny_i_dnipro · 289,947
#4
Труха⚡️Дніпро | Новини
@truexadnepr · 395,125
#5
Дніпро Оперативний 🇺🇦| Війна
@dnepr_operativ · 312,964
#6
Дніпро ОПЕРАТИВНИЙ 🇺🇦
@dneproperatyv · 189,122
#7
‼️СИРЕНА. ДНІПРО‼️
@sirena_dp · 242,739
#8
Лачен пише
@lachentyt · 1,576,100
#9
Труха⚡️Україна
@truexanewsua · 3,165,061
#10
Хуевый Днепр | Дніпро
@huevyi_dnepr · 168,217
#11
ДС: новини Дніпро
@dnipro_now · 765
#12
Доброго вечора, ми з Дніпра👋🏻
@we_from_dnipro · 240
#13
INSIDER UA | Україна | Новини
@insiderukr · 2,141,667
#14
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 938,428
#15
Pavlograd_now | 24/7 Павлоград Терновка Першотравенск
@pavlograd_now · 99,292
#16
Інформатор Дніпро | Радар
@dnipro_informator · 29,600
#17
Радар⚡️Дніпро
@RadarDnepr · 14,807
#18
Где повестки Днепр?
@agendaDnepr · 402,505
#19
Реальна Війна | Україна | Новини
@voynareal · 1,541,547
#20
УС: Україна, новини, політика, війна
@u_now · 1,403,118
#21
На повестке Днепр
@napovestkeDn · 61,520
#22
НУ І ПАВЛОГРАД 🇺🇦
@ny_i_pavlograd · 12,801
#23
Інформатор Дніпро
@dp_informator_ua · 47,516
#24
Україна Online: Новини | Політика
@UaOnlii · 1,536,697
#25
НУ І НОВІК
@ny_i_novik · 20,902
#26
Карта повітряних тривог 🇺🇦
@alarmua · 940,548
#27
ПРОСТО ДНЕПРОДЗЕРЖИНСК (Каменское)
@prosto_dnz · 64,897
#28
Батальйон Монако
@batalionmonako · 712
#29
ДНІПРО LIVE 24/7 🇺🇦 ДНЕПР РАДАР ТРИВОГА
@live_dnepr · 25,401
#30
HKR
@hyevuy_k_r · 154,014
#31
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 728,432
#32
Дніпро Обласний🔝
@dniprooblcentr · 31,163
#33
Ебанутый Днепр 🇺🇦
@ebanutiy_dnepr · 20,524
#34
ХПобеда 🇺🇦
@hyevaya_pobeda · 16,376
#35
‼️‼️‼️ Повітряна тривога Павлоград🚨‼️‼️
@pavlogradsirena · 26,529
#36
Дніпро TV | Новини | Україна
@dniprotv · 17,387
#37
Тривога України | Радар
@kiev_nebo · 539,280
#38
Типичный Днепр 🇺🇦
@typical_dnepr · 24,177
#39
НУ І КРИВИЙ РІГ
@ny_i_kryvyi_rih · 9,484
#40
Радар⚡️Запоріжжя
@radar_zaporizhzhya · 88,544
#41
ОПЕРАТИВНИЙ ПОКРОВСЬК | ДОБРОПІЛЛЯ
@pokrovsk_operativv · 21,877
#42
UA HiMARS 18+🫡
@war_ua_22 · 19,436
#43
⚡️ВКЛЮЧАТЕЛЬ КАМЕНСКОЕ⚡️
@kamenskoe_svitlo · 31,416
#44
СВОЇ | Кривий Ріг
@svoiKR · 276,929
#45
Это Кривой Рог, ДЕТКА😈
@ekrd_glavniy · 116,747
#46
Всевидящее ОКО 18 ✙
@oko18_ukr · 315,880
#47
news pavlograd 📰🔝
@news_pavlograd · 37,490
#48
Говорять Снайпер ꑭ
@stanislav_osman · 287,836
#49
Україна 24/7 - новини
@ukraina_novosti · 1,377,848 (as read 24 August 2026)
#50
💙💛ОПЕРАТИВНА БІЛКА 🐿️
@operativnabilka · 7,596
#51
✙DeepState✙🇺🇦
@deepstateua · 750,849
#52
Труха⚡️Київ
@truexakyiv · 972,266
#53
Kyiv Alerts 🚀 🚨
@kyiv_alerts · 48,942
#54
Тотальна Зрада
@totallzrada · 265,783
#55
Оперативний ЗСУ
@operativnoZSU · 359,722
#56
Это Днепр 🇺🇦
@eto_dnepr · 6,502
#57
ТИПОВИЙ КРИВИЙ РІГ
@typical_KR · 105,388
#58
Труха⚡️Кривий Ріг
@truexakrivojrog · 163,598
#59
Донбас Оперативний
@Operatyvnyi_Donbas · 82,137
#60
Олександр Ганжа / Дніпропетровська ОДА (ОВА)
@dnipropetrovskaODA · 47,162
#61
Дніпропетровський Купол
@alerts_dniproo · 38,628
#62
pavlograd_today
@pavlograd_today · 7,476
#63
monitoring
@monitorwarr · 85,177
#64
ХДніпро 🇺🇦Хуевый Днепр
@hyeviy_dnipro · 1,904
#65
Україна⚡️Новини⚡️
@uanova · 565,035
#66
ПТРК — Павлоградська телерадіокомпанія
@ptrkmedia · 15,738
#67
Николаевский Ванёк
@vanek_nikolaev · 2,571,456
#68
monitor
@war_monitor · 958,023
#69
Куди летить? | Тривога
@radar_raketaa · 490,712
#70
∆✙🍒Гнила черешня🇺🇦✙∆
@gnilayachereha · 412,798
#71
Бавовна
@ukrbavovna · 800,178
#72
✙ 🔼Вертикаль
@vert2026 · 113,508
#73
Чому тривога | Радар
@raketa_trevoga · 472,563
#74
🔊⚠️єРадар | Повітряна тривога | Ракетна небезпека
@eRadarrua · 410,667
#75
🚀 РАКЕТА UA | Тривога України
@war_raketaua · 85,686
#76
Скринька Пандори
@pandoras_box_ua · 157,815
#77
Де Ракета ?🚀 | Моніторинг
@deraketaua · 154,826
#78
Повестки Днепр
@povestki_dnepr_TSK · 39,713
#79

Read from Telegram’s recommendation API, most recently 24 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.

‼️‼️‼️ Повітряна тривога Павлоград🚨‼️‼️
@pavlogradsirena · 26,529
Telegram ranks this channel #8 of 56 here — alongside 55 others — read 13 September 2026
Pavlograd_now | 24/7 Павлоград Терновка Першотравенск
@pavlograd_now · 99,292
Telegram ranks this channel #9 of 75 here — alongside 74 others — read 16 August 2026
Где повестки Днепр?
@agendaDnepr · 402,505
Telegram ranks this channel #9 of 70 here — alongside 69 others — read 10 August 2026
Включатель Днепр⚡️
@vklyuchatel_dnepr_svet · 197,131
Telegram ranks this channel #10 of 69 here — alongside 68 others — read 12 August 2026
Дніпро⚡️Незламний
@dnipro_nez · 22,852
Telegram ranks this channel #12 of 74 here — alongside 73 others — read 18 September 2026
Дніпро UA
@dnipro1776 · 18,958
Telegram ranks this channel #14 of 72 here — alongside 71 others — read 2 October 2026
news pavlograd 📰🔝
@news_pavlograd · 37,490
Telegram ranks this channel #15 of 72 here — alongside 71 others — read 31 August 2026
Інформатор Дніпро | Радар
@dnipro_informator · 29,600
Telegram ranks this channel #16 of 77 here — alongside 76 others — read 6 September 2026
ПРОСТО ДНЕПРОДЗЕРЖИНСК (Каменское)
@prosto_dnz · 64,897
Telegram ranks this channel #16 of 78 here — alongside 77 others — read 21 August 2026
Дніпро ⚡️Новини
@dnipro_insider · 39,263
Telegram ranks this channel #17 of 81 here — alongside 80 others — read 30 August 2026
ХДніпро 🇺🇦 Хуевый Днепр
@huevuy_dnepr · 22,722
Telegram ranks this channel #18 of 69 here — alongside 68 others — read 19 September 2026
‼️СИРЕНА. ДНІПРО‼️
@sirena_dp · 242,739
Telegram ranks this channel #18 of 75 here — alongside 74 others — read 11 August 2026
ДНІПРО LIVE 24/7 🇺🇦 ДНЕПР РАДАР ТРИВОГА
@live_dnepr · 25,401
Telegram ranks this channel #19 of 78 here — alongside 77 others — read 14 September 2026
Доброго вечора, ми з Дніпра👋🏻
@we_from_dnipro · 240
Telegram ranks this channel #19 of 85 here — alongside 84 others — read 18 August 2026
НУ І НОВІК
@ny_i_novik · 20,902
Telegram ranks this channel #21 of 78 here — alongside 77 others — read 30 September 2026
НУ І ДНІПРО! 🇺🇦
@ny_i_dnipro · 289,947
Telegram ranks this channel #21 of 72 here — alongside 71 others — read 10 August 2026
Ебанутый Днепр 🇺🇦
@ebanutiy_dnepr · 20,524
Telegram ranks this channel #22 of 73 here — alongside 72 others — read 26 September 2026
Дніпро ОПЕРАТИВНИЙ 🇺🇦
@dneproperatyv · 189,122
Telegram ranks this channel #22 of 82 here — alongside 81 others — read 11 August 2026
Труха⚡️Камʼянське
@truexakam · 37,138
Telegram ranks this channel #23 of 63 here — alongside 62 others — read 4 September 2026
Кам'янське | Каменское - Новини міста
@kmnskoe · 22,111
Telegram ranks this channel #24 of 59 here — alongside 58 others — read 24 September 2026
Типичный Днепр 🇺🇦
@typical_dnepr · 24,177
Telegram ranks this channel #24 of 73 here — alongside 72 others — read 16 September 2026
На повестке Днепр
@napovestkeDn · 61,520
Telegram ranks this channel #24 of 70 here — alongside 69 others — read 22 August 2026
Хуевый Днепр | Дніпро
@huevyi_dnepr · 168,217
Telegram ranks this channel #24 of 82 here — alongside 81 others — read 12 August 2026
ХДніпро 🇺🇦
@hyevuy_dnepr · 520,760
Telegram ranks this channel #25 of 81 here — alongside 80 others — read 9 August 2026

This channel appears in 48 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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“Дніпровський пише” (@dnipro_pishet), 52,273 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/dnipro_pishet.

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.