Channel
@sov_vrn
On this record: Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
520subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001724251271 |
|---|---|
| Type | Channel |
| Username | @sov_vrn |
| Description | Официальный канал управы Советского района |
| Created | 11 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/sov_vrn |
This channel’s posts match, word for word or near enough, posts on 3 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 07:02 | 520 | no change |
| 7 Aug 2026, 06:54 | 520 | first reading |
20 posts held, back to 13 March 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 1 pageof 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 28 July 2026 |
|---|---|
| Posts held | 20 (13 March 2026 – 28 July 2026) |
| Views total | 45 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 07: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.
Lifetime counters from Telegram’s own channel header, read 7 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.
4 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🙏 | 3 | 75.0% | |
| 👍 | 1 | 25.0% |
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 2 of the 20 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 13 March 2026 to 28 July 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.
Каждый регион нашей страны — это уникальная история, отраженная в лицах людей, красоте природы, традициях и культурном наследии. X Юбилейный Международный фотоконкурс «Русская цивилизация» вновь открывает возможность показать красоту родного края и поделиться своей историей со всей страной. В этом году введена новая специальная номинация ФГБУ «Дом народов России» — «Россия – семья семей». Фотографии, отражающие сем…
Отбой ракетной опасности в регионе!
Уважаемые воронежцы! Внимание, в регионе объявляется ракетная опасность! Работают системы оповещения. Если вы находитесь дома, необходимо укрыться в помещениях без окон со сплошными стенами. Это коридор, ванная, кладовая. Если вы находитесь на улице — зайдите в ближайшее здание или подходящее укрытие.
Отмена непосредственной угрозы атаки БПЛА в Воронеже, Нововоронеже, Борисоглебске, Бутурлиновском, Лискинском, Россошанском и Острогожском районах! Режим опасности атаки БПЛА действует на всей территории региона.
Внимание! Воронеж — тревога в связи с угрозой непосредственного удара БПЛА. Работают системы оповещения. Зайдите в помещение, отойдите от окон. Если увидели БПЛА — сразу уходите из зоны его видимости и позвоните по телефону 112.
Отмена непосредственной угрозы атаки БПЛА в Воронеже и Нововоронеже! Режим опасности атаки БПЛА действует на всей территории региона.
Внимание! Воронеж и Нововоронеж — тревога в связи с угрозой непосредственного удара БПЛА. Работают системы оповещения. Зайдите в помещение, отойдите от окон. Если увидели БПЛА — сразу уходите из зоны его видимости и позвоните по телефону 112.
Отмена непосредственной угрозы атаки БПЛА в Воронеже! Дежурными силами ПВО в небе над городом обнаружены и уничтожены два беспилотных летательных аппарата. По предварительной информации, пострадавших и разрушений нет. Режим опасности атаки БПЛА действует на всей территории региона.
Внимание! Воронеж — тревога в связи с угрозой непосредственного удара БПЛА. Работают системы оповещения. Зайдите в помещение, отойдите от окон. Если увидели БПЛА — сразу уходите из зоны его видимости и позвоните по телефону 112.
🙏3
Отмена непосредственной угрозы атаки БПЛА в Воронеже и Лискинском районе! Режим опасности атаки БПЛА действует на всей территории региона.
Внимание! Воронеж — тревога в связи с угрозой непосредственного удара БПЛА. Работают системы оповещения. Зайдите в помещение, отойдите от окон. Если увидели БПЛА — сразу уходите из зоны его видимости и позвоните по телефону 112.
Отмена непосредственной угрозы атаки БПЛА в Воронеже, Нововоронеже и Острогожском районе! Режим опасности атаки БПЛА действует на всей территории региона.
Showing the 12 most recent of 20 posts we hold for @sov_vrn. 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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Управа Советского района” (@sov_vrn), 520 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/sov_vrn.
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.