Channel
@Volodarskoe_News
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Cite this entry
1,541subscribers
+32 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001625607362 |
|---|---|
| Type | Channel |
| Username | @Volodarskoe_News |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/Volodarskoe_News |
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 17 September 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 |
|---|---|---|
| 18 Sept 2026, 17:37 | 1,541 | +11 |
| 14 Sept 2026, 17:16 | 1,530 | -1 |
| 10 Sept 2026, 23:21 | 1,531 | +14 |
| 5 Sept 2026, 18:19 | 1,517 | +4 |
| 1 Sept 2026, 09:26 | 1,513 | +1 |
| 29 Aug 2026, 17:06 | 1,512 | +3 |
| 26 Aug 2026, 19:33 | 1,509 | no change |
| 26 Aug 2026, 01:00 | 1,509 | first reading |
10 posts held, back to 24 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 1 page 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 3 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 25 August 2026 |
|---|---|
| Posts held | 10 (24 August 2026 – 25 August 2026) |
| Views total | 2,810 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 26 Aug 2026, 01:00 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.
Measured directly from 1 video 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.
4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 50.0% | |
| 👍 | 2 | 50.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 3 of the 10 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 24 August 2026 to 25 August 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. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| MvGzQC98w3kvMJtraRy2Qepr | 1 | 25 August 2026 | 25 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 10 most recent posts we hold, published 24 August 2026 to 25 August 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.
В Володарском округе навели порядок на месте захоронения павших советских солдат в годы ВОВ 25 августа председатель ТОС «Тополек» и жители села Шевченко совместными усилиями навели порядок на месте захоронения павших советских солдат в годы ВОВ.
👍2
В Володарском округе прошло расширенное аппаратное совещание 25 августа глава Володарского округа Сергей Юзвинкевич провел расширенное аппаратное совещание с начальниками отделов и структурных подразделений администрации Володарского округа, руководителями предприятий, а также территориальных подразделений министерств и ведомств ДНР. Обсудили текущую ситуацию и определили приоритетные задачи на ближайший период. Та…
ШУМ продлил прием заявок на участие в одноименной премии до 28 августа Продлился приём заявок на Премию «ШУМ» — теперь зарегистрироваться можно до 28 августа 12:00 (по мск) на сайте: premiyashum.ru Это супер возможность для тех медиаспециалистов, кто хочет заявить о себе на всю страну, расширить аудиторию и даже получить финансовую поддержку.
BACK TO SCHOOL в modi! 🤍🖤 ✨ Школьная ярмарка! ✨ Ручки и тетради, стильные блокноты и стикеры на любой вайб — собери свой идеальный набор в modi! Сделай этот учебный год самым ярким! А так-же у нас представлено 12 товарных категорий: • товары для дома • канцелярия • подарки • декоративная и уходовая косметика • украшения и аксессуары • товары для праздника • игры и игрушки • товары для путешествий • зоотовары • то…
В Володарском округе проверили ход подготовки Зеленоярской школы к новому учебному году 25 августа глава Володарский округ Сергей Юзвинкевич проверил ход подготовки ГБОУ «Зеленоярская школа Володарского м.о.» к новому учебному году. В ходе выезда Сергей Вильевич осмотрел результаты проведенного ремонта, состояние классных кабинетов, пищеблока и санитарных узлов, а также проверил готовность систем водоснабжения и от…
В Володарском округе прошел турнир по мини-футболу среди юношей 22 августа в Володарском муниципальном округе состоялся турнир по мини-футболу среди мужских команд. По итогам турнира места распределились следующим образом: — 1 место — «Олимпик»; — 2 место — «Скиф»; — 3 место — «Володарск».
❗️❗️Народный фронт в ДНР предупреждает! 🔴ВНИМАНИЕ! ФЕЙК! Вновь зафиксированы случаи распространения поддельных писем от имени Народного фронта. На этот раз мошенники рассылают по организациям и учреждениям поддельные письма о передаче гуманитарной помощи — генераторов и антидроновых сетей. В письме — ссылка на архив с якобы "документами" и пароль для доступа. Переходить по ссылкам и скачивать файлы категорически н…
Глава избиркома ДНР объяснил, почему в регионе нет электронного голосования Дистанционное электронное голосование (ДЭГ) является хорошей формой волеизъявления граждан, но по ряду причин пока не проводится в ДНР. Об этом сообщил Донецкому агентству новостей председатель Избирательной комиссии Республики Владимир Высоцкий. «Дистанционное электронное голосование — это очень хорошая вещь. Наверно, это моя персональная м…
❤1
Как пишут прихожане, в Святогорской лавре укропы всушники зверски убили монаха, и ранили еще двоих. Нападение произошло около 11 утра возле Свято-Николаевского храма в верхней части монастыря. Ножом был зверски убит монах Варсонофий, его лицо изуродовали до неузнаваемости. Кроме того, были ранены инок Григорий (у него ножом пробито легкое) и послушник Андрей. Оба находятся в тяжелом состоянии в одной из больниц г…
❤1
Росгвардейцы ДНР стали призерами чемпионата по военно-спортивному многоборью в Южном округе Представители Главного управления Росгвардии по ДНР замкнули тройку лидеров чемпионата Южного округа войск национальной гвардии РФ по летнему офицерскому троеборью. Соревнования прошли в Краснодарском крае в год 10-летия ведомства. В состязаниях приняли участие 85 спортсменов — они представляли 16 сборных команд со всего юга…
Showing the 10 most recent of 10 posts we hold for @Volodarskoe_News. 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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“ВОЛОДАРСКИЕ ВЕСТИ” (@Volodarskoe_News), 1,541 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Volodarskoe_News.
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.