Одна людина загинула, ще одна дістала поранень через атаку росіян на приватний сектор Дніпра, – ОВА На місці триває ліквідація наслідків ворожого удару. 🏙Наше місто Дніпро
😢3

Channel
@nashemisto_dp
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
10,842subscribers
-64 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001199035757 |
|---|---|
| Type | Channel |
| Username | @nashemisto_dp |
| Description | 🔹Важливі новини Дніпра 🔹Актуальні події 🔹Фоторепортажі із гарячих місць 🔹Яскравий контент 24/7 ✅ Реклама тут 👉 @AdvDnipro |
| Created | 11 July 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 61 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/nashemisto_dp |
Local community — 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 68% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 13:16 | 10,842 | +22 |
| 6 Nov 2026, 15:18 | 10,820 | -5 |
| 5 Nov 2026, 13:18 | 10,825 | -1 |
| 4 Nov 2026, 11:16 | 10,826 | +8 |
| 3 Nov 2026, 12:45 | 10,818 | +12 |
| 2 Nov 2026, 14:16 | 10,806 | -2 |
| 1 Nov 2026, 16:17 | 10,808 | +1 |
| 31 Oct 2026, 17:25 | 10,807 | -2 |
| 30 Oct 2026, 19:08 | 10,809 | +9 |
| 29 Oct 2026, 19:28 | 10,800 | +16 |
| 28 Oct 2026, 20:19 | 10,784 | +6 |
| 27 Oct 2026, 21:30 | 10,778 | +1 |
| 27 Oct 2026, 00:36 | 10,777 | +3 |
| 26 Oct 2026, 01:30 | 10,774 | -2 |
| 24 Oct 2026, 23:19 | 10,776 | -3 |
| 24 Oct 2026, 01:38 | 10,779 | -9 |
| 22 Oct 2026, 22:39 | 10,788 | -3 |
| 21 Oct 2026, 21:31 | 10,791 | -7 |
| 20 Oct 2026, 13:45 | 10,798 | +4 |
| 19 Oct 2026, 11:10 | 10,794 | first reading |
451 posts held, back to 5 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 51 pages of 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 8 November 2026 |
|---|---|
| Posts held | 451 (5 August 2026 – 8 November 2026) |
| Views total | 118,928 |
| Reactions total | 2,783 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Nov 2026, 09:08 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 8 November 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.
Measured directly from 43 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.
10,396 reactions across 430 posts, in 22 distinct kinds. The most used accounts for 38.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4,005 | 38.5% | |
| 🙏 | 2,147 | 20.7% | |
| 👍 | 1,245 | 12.0% | |
| 😢 | 869 | 8.36% | |
| 🤬 | 514 | 4.94% | |
| 🤔 | 375 | 3.61% | |
| 🥰 | 216 | 2.08% | |
| 😱 | 172 | 1.65% | |
| 🏆 | 167 | 1.61% | |
| ❤🔥 | 152 | 1.46% | |
| 😍 | 137 | 1.32% | |
| 😭 | 123 | 1.18% | |
| 🤨 | 69 | 0.664% | |
| 💔 | 52 | 0.5% | |
| 👌 | 42 | 0.404% | |
| 🔥 | 33 | 0.317% | |
| 👏 | 22 | 0.212% | |
| 🤯 | 19 | 0.183% | |
| 🕊 | 16 | 0.154% | |
| 🤩 | 12 | 0.115% | |
| 2 further kinds | 9 | 0.087% |
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 451 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 10,593 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 451 most recent posts we hold, published 5 August 2026 to 8 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’s own ‘edited’ marker: 15 of 120 posts held from the last 30 days (12.5%) 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).
Одна людина загинула, ще одна дістала поранень через атаку росіян на приватний сектор Дніпра, – ОВА На місці триває ліквідація наслідків ворожого удару. 🏙Наше місто Дніпро
😢3
❗️Повітряні тривоги у застосунку єДніпро Під час блекауту частина вуличних сирен у Дніпрі може не працювати. Сповіщення в єДніпро працюють у штатному режимі. Щоб отримувати їх, телефон має бути підключений до інтернету. Застосунок повідомляє про початок і відбій тривоги, а також показує рівень небезпеки та причину оголошення тривоги. Перевірте, чи дозволені сповіщення для єДніпро в налаштуваннях телефону. Отримали…
❤2
У Дніпрі знову «прильот» по приватному сектору. Попередньо під завалами люди. Усі служби працюють. І так, у місті знову блекаут. На жаль, вже другий за останні два тижні. Але ви й без мене бачите, що росіяни не заспокоюються. Тож сухо й офіційно. … Стаціонарні пункти незламності працюють. За потреби розгортатимемо й пересувні. Усі тягові підстанції знеструмлені, а отже жоден електротранспорт у місті не їздить. Н…
🙏12❤7😢4😭2💔1
Ворог ударив безпілотником по передмістю Дніпра, – ОВА Зайнялася пожежа. Зруйнований щонайменше один приватний будинок. Попередньо, під завалами можуть бути люди. 🏙Наше місто Дніпро
😢13🙏6
Попередньо, є й збиття ворожого залізяччя Наразі без загроз. 🏙Наше місто Дніпро
🙏17🔥3❤1👍1
Понад 400 Пунктів незламності вже працюють у п’яти районах Дніпропетровщини, частково знеструмлених через ворожі удари. Понад 160 з них – у Дніпровському районі, – ОВА Там можна зарядити гаджети, скористатися інтернетом і зігрітися. Загалом в області – майже 1500 Пунктів незламності. У понад 60 з них за потреби можна заночувати. Усі забезпечені генераторами та запасами питної води. Якщо залишилися без світла, звер…
👍6❤1
Ще два БпЛА на Дніпро, — монітори Не покидайте укриттів!
🤬8🙏4
Вибух пролунав у Дніпрі
🙏11🤬4
Реактивні БпЛА в бік Дніпра, — монітори Перебувайте в укриттях!
🙏14🤬2
Безпечний Дніпро. У Дніпрі, за заявками громадян, щодня працює "Водоканал" На вулиці Героїв Крут відновили покриття після проведення робіт. Про це повідомив Геннадій Корбан у своєму Telegram-каналі. "Просимо допомогти відновити асфальтове покриття після ремонту водопровідної мережі біля будинку 14 на вулиці Героїв Крут. Ця ділянка має великий потік пішоходів, зокрема дітей, які йдуть до школи", - написала мешканка …
❤7🤯2🤩1
Силач із Дніпра втретє за рік побив власний рекорд на змаганнях богатирів На Кубку України з богатирського багатоборства у Рівному Дмитро Грунський встановив новий рекорд у вправі «Сходи сили Патона». У цій дисципліні учасники мають якомога швидше підняти важке знаряддя спеціальними сходами. Для Грунського це вже третє оновлення власного результату за рік. Загалом на рахунку силача понад 20 рекордів, внесених до К…
🏆17❤6
Хвилина мовчання. Пам'ять про загиблого Олега Швеця 25 жовтня поблизу Дружківки Донецької області загинув старший сержант ЗСУ Олег Миколайович Швець. У перші дні повномасштабного російського вторгнення Олег Швець став на захист України. Військовий загинув під час бойових дій на Донеччині. 31 жовтня у церкві Суламіта відбулася панахида за полеглим захисником. Після цього воїна поховали на Алеї Героїв кладовища по в…
😢53🙏15❤7💔2
Showing the 12 most recent of 451 posts we hold for @nashemisto_dp. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
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.
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 13 seed channels' Telegram-generated recommendation lists in total. 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“Наше Місто Дніпро” (@nashemisto_dp), 10,842 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/nashemisto_dp.
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.