Channel
@RusBerNews
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Telegram's recommendations · Cite this entry
17,436subscribers
+897 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001379012273 |
|---|---|
| Type | Channel |
| Username | @RusBerNews |
| Description | Важливі та цікаві новини для мешканців Русанівки та Березняків. Зворотній зв'язок @RBNewsbot instagram.com/rusberlive fb.com/groups/rusberlive |
| 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 | 12 November 2026 |
| Measurements held | 61 |
| Confirmed unchanged | 2 times, most recently 12 November 2026 |
| On Telegram | t.me/RusBerNews |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 |
|---|---|---|
| 10 Nov 2026, 05:49 | 17,436 | -6 |
| 8 Nov 2026, 17:21 | 17,442 | -2 |
| 7 Nov 2026, 11:10 | 17,444 | +6 |
| 6 Nov 2026, 13:38 | 17,438 | +3 |
| 5 Nov 2026, 12:45 | 17,435 | +5 |
| 4 Nov 2026, 12:06 | 17,430 | +45 |
| 3 Nov 2026, 08:30 | 17,385 | +3 |
| 2 Nov 2026, 07:09 | 17,382 | +7 |
| 1 Nov 2026, 07:50 | 17,375 | -5 |
| 31 Oct 2026, 06:19 | 17,380 | +27 |
| 30 Oct 2026, 05:21 | 17,353 | +49 |
| 29 Oct 2026, 08:21 | 17,304 | -8 |
| 28 Oct 2026, 05:00 | 17,312 | +1 |
| 27 Oct 2026, 04:01 | 17,311 | +5 |
| 26 Oct 2026, 06:20 | 17,306 | -4 |
| 25 Oct 2026, 04:59 | 17,310 | -5 |
| 24 Oct 2026, 02:54 | 17,315 | -3 |
| 23 Oct 2026, 04:50 | 17,318 | +8 |
| 22 Oct 2026, 02:31 | 17,310 | +11 |
| 20 Oct 2026, 21:44 | 17,299 | first reading |
920 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 77 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 311 of 313 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 920 (6 August 2026 – 13 November 2026) |
| Views total | 1,182,307 |
| Reactions total | 13,304 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 18:22 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 13 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 117 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.
48,577 reactions across 917 posts, in 23 distinct kinds. The most used accounts for 20.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤬 | 10,026 | 20.6% | |
| ❤ | 8,616 | 17.7% | |
| 😁 | 7,922 | 16.3% | |
| 🙏 | 6,563 | 13.5% | |
| 👍 | 4,848 | 9.98% | |
| 😢 | 2,175 | 4.48% | |
| 👎 | 1,299 | 2.67% | |
| 🤯 | 1,019 | 2.10% | |
| custom 5402174001931901119 | 886 | 1.82% | |
| custom 5800747065784929649 | 856 | 1.76% | |
| 🔥 | 802 | 1.65% | |
| 🤔 | 706 | 1.45% | |
| 🤪 | 581 | 1.20% | |
| 😱 | 536 | 1.10% | |
| 🙈 | 513 | 1.06% | |
| custom 5242478184334658673 | 432 | 0.889% | |
| 👏 | 204 | 0.42% | |
| 🤗 | 141 | 0.29% | |
| custom 5242681838798933498 | 138 | 0.284% | |
| ✍ | 105 | 0.216% | |
| 3 further kinds | 209 | 0.43% |
Custom emoji. 4 of the rows above are 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 counts beside them are Telegram’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 917 of the 920 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 48,577 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 920 most recent posts we hold, published 6 August 2026 to 13 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: 203 of 313 posts held from the last 30 days (64.9%) 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).
😭 Мешканці будинку на вул. Ентузіастів, 5/1 шукають Скуратівську Надію, яка проживає на Березняках. Жінка має відношення до квартири в цьому будинку, з якої витікає вода та затоплює сусідів. Наразі водопостачання перекрито, а ремонтники не можуть розпочати роботи, доки не вдасться знайти відповідальну за квартиру особу. ❗️ Якщо ви знаєте Надію Скуратівську або маєте її контакти, будь ласка, допоможіть передати їй ц…
❤8😱5🙏2
🗺 У застосунку "Повітряна тривога" відновили функцію відстеження руху ворожих повітряних цілей. Тепер для доступу до неї користувачам необхідно пройти верифікацію через "Дію", — Мінцифри. 👊 Донат на ЗСУ ✈️Надіслати нам новину @RBNewsbot│👥Форум 💬Русанівка│💬Березняки
❤22😁14👎5🤯3
😵 У Києві опалення вже отримали 99% комунальних багатоквартирних будинків. Виняток — окремі випадки аварій на тепломережах, які наразі усувають, — Кличко 👊 Донат на ЗСУ ✈️Надіслати нам новину @RBNewsbot│👥Форум 💬Русанівка│💬Березняки
👍21🙏6❤1🤬1
🟩🟩м. Київ Відбій повітряної тривоги
🙏9👍4❤3
❗️ Якщо через руйнування інфраструктури послуги фактично не надаватимуться, розглядається можливість припинення нарахування комунальних платежів, — прем’єр Корецький 👊 Донат на ЗСУ ✈️Надіслати нам новину @RBNewsbot│👥Форум 💬Русанівка│💬Березняки
😁41👍21🤯4❤1👏1🤪1
🚀 загроза застосування малогабаритної реактивної крилатої ракети-дрона «Бандероль».
🤬21🙏7
🟩🟩м. Київ Відбій повітряної тривоги
🙏11❤2👍2
🟡📢📢📢м. Київ 🚀 Причина тривоги: Загроза реактивного БПЛА.
🤬13🙏10
🟩🟩м. Київ Відбій повітряної тривоги
🙏8❤3custom 52426818387989334981
🟡📢📢📢м. Київ 🚀 Причина тривоги: Загроза реактивного БПЛА.
🤬7🙏3custom 52424781843346586731
🟩🟩м. Київ Відбій повітряної тривоги
❤9🙏6custom 52426818387989334981
📢📢📢м. Київ ‼️Ракетна небезпека: загроза застосування балістичного озброєння.
🤬13🙏5❤1custom 52424781843346586731
Showing the 12 most recent of 920 posts we hold for @RusBerNews. 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.
@RusBerNews edited 7 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.
We recorded 2 posts on @RusBerNews 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.
The 5 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
😐 На Русанівці з опаленням якась температурна лотерея. В одних будинках батареї холодні, в інших — можна яєчню смажити. А що у вас?
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
🤔 Що зараз із водою у вас?
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
🤔 Що зараз із водою у вас? У частині будинків водопостачання вже відновили, в інших води поки немає.
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
⛽️ А що у вас із опаленням? Учора почали подавати тепло, але ситуація на R&B, як завжди, неоднорідна.
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
🤨 Що далі з МАФами?
The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 920 most recent posts we hold, published 6 August 2026 to 13 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 9 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“R&B News. Русанівка та Березняки.” (@RusBerNews), 17,436 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/RusBerNews.
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.