Channel
@we_from_dnipro
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
86,681subscribers
-759 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001245586711 |
|---|---|
| Type | Channel |
| Username | @we_from_dnipro |
| Description | Останні новини Дніпра, новини онлайн. 📩 За рекламою звертатись до @dobrogovechoraeastmanager_bot Зробимо найкращу рекламу вашому продукту! Посилання для друзів – https://t.me/+FzVXPfe0jis0Zjhi |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/we_from_dnipro |
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 21 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 2 Sept 2026, 11:05 | 86,681 | -37 |
| 1 Sept 2026, 14:14 | 86,718 | -67 |
| 31 Aug 2026, 11:35 | 86,785 | +44 |
| 30 Aug 2026, 13:17 | 86,741 | -16 |
| 29 Aug 2026, 14:58 | 86,757 | -8 |
| 28 Aug 2026, 12:22 | 86,765 | -42 |
| 27 Aug 2026, 13:44 | 86,807 | -28 |
| 26 Aug 2026, 12:37 | 86,835 | -24 |
| 25 Aug 2026, 12:37 | 86,859 | +3 |
| 24 Aug 2026, 10:55 | 86,856 | -63 |
| 22 Aug 2026, 20:48 | 86,919 | -46 |
| 21 Aug 2026, 12:47 | 86,965 | -27 |
| 20 Aug 2026, 10:12 | 86,992 | -4 |
| 19 Aug 2026, 09:55 | 86,996 | -29 |
| 18 Aug 2026, 10:52 | 87,025 | -19 |
| 17 Aug 2026, 11:14 | 87,044 | -104 |
| 15 Aug 2026, 19:57 | 87,148 | -69 |
| 14 Aug 2026, 13:14 | 87,217 | -35 |
| 13 Aug 2026, 02:58 | 87,252 | -44 |
| 12 Aug 2026, 03:18 | 87,296 | first reading |
536 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 82 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. It is computed over the 535 of 536 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 536 (6 August 2026 – 3 September 2026) |
| Views total | 5,891,100 |
| Reactions total | 65,786 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 07:54 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 3 September 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 103 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.
65,786 reactions across 535 posts, in 15 distinct kinds. The most used accounts for 26.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤬 | 17,664 | 26.9% | |
| 🙏 | 16,977 | 25.8% | |
| 😢 | 12,728 | 19.3% | |
| ❤ | 7,970 | 12.1% | |
| 👍 | 2,975 | 4.52% | |
| 💩 | 1,537 | 2.34% | |
| 😁 | 1,303 | 1.98% | |
| 🤯 | 1,091 | 1.66% | |
| 😱 | 1,027 | 1.56% | |
| 🤡 | 884 | 1.34% | |
| 🔥 | 825 | 1.25% | |
| 🤔 | 331 | 0.503% | |
| 👎 | 206 | 0.313% | |
| 🥰 | 158 | 0.24% | |
| 🥴 | 110 | 0.167% |
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 535 of the 536 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 65,786 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 536 most recent posts we hold, published 6 August 2026 to 3 September 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
Measured over the 536 most recent posts we hold, published 6 August 2026 to 3 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
😔Пʼятеро поранених залишаються у лікарні після вчорашньої атаки росіян на Дніпро, – ОВА. Троє чоловіків у важкому стані. Ворожий удар по Дніпру забрав життя двох людей. Ще девʼятеро постраждали. ㅤ Ми з Дніпра 👋 Надіслати новину
🙏37😢8❤6
⚡️52.028 гривень – стільки ви могли заробити за минулий місяць, якби працювали на удальонці. Через війну в Україні сформувався дефіцит людей, які можуть працювати з дому, тому навіть студентам та особам без досвіду пропонують зарплати 20-50 тисяч гривень. Головне – знати де шукати роботу, а саме користуватись такими ресурсами, як канал Injobe. Там викладають вакансії від роботдавців, які платять від $700. Освіта?…
👍4❤1💩1
💥10 ворожих БпЛА збили упродовж ночі наші сили ППО у різних районах Дніпропетровщини. Дякуємо 🙏🏼 ㅤ Ми з Дніпра 👋 Надіслати новину
🙏144❤39👍8🤡1
🤯В Одесі мінімум 17 постраждалих, у т.ч. 3 дітей, через удари рф по місту. ➡️ Репортаж із центру подій: https://t.me/+QOk0SQCbaQ05NjYy
😢89🤬50🙏20❤4😁2
БпЛА на Магдалинівку. ㅤ Ми з Дніпра 👋 Надіслати новину
🙏40🤬18😁2❤1🤡1🤯1
2 реактива у бік міста. ㅤ Ми з Дніпра 👋 Надіслати новину
🙏85🤬29😢6❤5🤡1
3 реактивних на Юріївку та 2 на Магдалинівку. ㅤ Ми з Дніпра 👋 Надіслати новину
🙏62🤬35👍2❤1🤡1
😨Ще кадри наслідків ворожої атаки по Дніпру. Шрапнель ледь не вбила людину в авто. ㅤ Ми з Дніпра 👋 Надіслати новину
🙏89🤯39🤬22😢12❤11🤡1
Гучні звуки, які чули мешканці Дніпра, – робота наших сил ППО, – ОВА. До відбою повітряної тривоги залишайтеся у безпечних місцях. ㅤ Ми з Дніпра 👋 Надіслати новину
🙏112❤27🔥3🤡2
Твій 100% бонус +50 фріспінів #реклама
❤7🤡4💩2
😨4 людей загинули внаслідок обстрілу області вдень, – ОВА. ㅤ Ми з Дніпра 👋 Надіслати новину
😢144🤬46🙏5❤2
Ветерани звинуватили очільника Федерації дзюдо України у рейдерстві На круглому столі «Ветеранський спорт без розривів» у Києві учасники підняли питання репутації президента Федерації дзюдо України Михайла Кошляка. Кілька ветеранів публічно заявили про колабораціонізм, рейдерство та зв’язки з кримінальним середовищем і зажадали реакції від Мінмолодьспорту. Один з присутніх розповів, що вже чотирнадцять років судит…
❤33👍18🥴7😁3
Showing the 12 most recent of 536 posts we hold for @we_from_dnipro. 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.
@we_from_dnipro edited 2 posts 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.
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.
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.
@we_from_dnipro named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was 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.
Read from Telegram’s recommendation API, most recently 18 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 25 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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“Доброго вечора, ми з Дніпра👋🏻” (@we_from_dnipro), 86,681 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/we_from_dnipro.
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.