Channel
@r31belgorod
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
31,474subscribers
-159 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001523696308 |
|---|---|
| Type | Channel |
| Username | @r31belgorod |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/r31belgorod |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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 |
|---|---|---|
| 16 Sept 2026, 20:00 | 31,474 | -7 |
| 15 Sept 2026, 01:18 | 31,481 | -8 |
| 13 Sept 2026, 07:16 | 31,489 | -10 |
| 11 Sept 2026, 09:01 | 31,499 | -2 |
| 8 Sept 2026, 17:57 | 31,501 | -12 |
| 5 Sept 2026, 14:38 | 31,513 | -8 |
| 3 Sept 2026, 16:58 | 31,521 | -1 |
| 2 Sept 2026, 07:07 | 31,522 | -4 |
| 1 Sept 2026, 03:36 | 31,526 | -7 |
| 31 Aug 2026, 06:14 | 31,533 | -7 |
| 30 Aug 2026, 03:38 | 31,540 | -3 |
| 29 Aug 2026, 01:47 | 31,543 | -1 |
| 28 Aug 2026, 00:59 | 31,544 | -5 |
| 26 Aug 2026, 21:29 | 31,549 | -6 |
| 25 Aug 2026, 23:52 | 31,555 | -4 |
| 25 Aug 2026, 00:54 | 31,559 | -6 |
| 23 Aug 2026, 16:04 | 31,565 | -8 |
| 22 Aug 2026, 00:05 | 31,573 | -4 |
| 20 Aug 2026, 18:15 | 31,577 | -6 |
| 19 Aug 2026, 20:17 | 31,583 | first reading |
22 posts held, back to 2 July 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 63 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 3 of 4 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 September 2026 |
|---|---|
| Posts held | 22 (2 July 2026 – 6 September 2026) |
| Views total | 5,269 |
| Reactions total | 14 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Sept 2026, 13:24 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 6 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.
90 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 54 | 60.0% | |
| 👍 | 27 | 30.0% | |
| 👎 | 6 | 6.67% | |
| 🔥 | 1 | 1.11% | |
| 😱 | 1 | 1.11% | |
| 🥰 | 1 | 1.11% |
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 19 of the 22 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 90 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 2 July 2026 to 6 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.
🕷 Клещи покусали более 1,5 тысячи белгородцев с начала весны С 1 марта по 3 сентября за медпомощью после укусов клещей обратились 1530 жителей региона. Среди них — 426 детей. Это на 3,6% меньше, чем за аналогичный период прошлого года. Всего зарегистрировали 74 случая клещевого боррелиоза. Данные приводит региональное управление Роспотребнадзора.
👍2😱1
В управлении Экоохотнадзора Белгородской области рассказали, что сейчас на полях региона можно наблюдать необычное явление — аисты собираются в многочисленные стаи. Всё просто: после уборки урожая и покоса травы на полях остаются грызуны, насекомые и лягушки — лёгкая добыча для птиц. Аисты прилетают целыми группами, чтобы накопить силы перед дальней дорогой — осенней миграцией на юг. Птицы общаются, наедаются и гот…
❤2👍2
Вид на улицы Щорса и Конева, 2006 год.
❤7
Вчера на ул. Губкина 60-летний водитель эвакуатора «Исудзу» при перестроении врезался в «ПАЗ» под управлением 41-летнего водителя, затем наехал на стоящую «Ладу XRAY» с женщиной-водителем внутри. Пострадали 5 пассажирок «ПАЗа» (57, 65, 46 и 35 лет).
Доброе утро. ☀️
❤6
☀️ Доброе утро, Белгород! Сегодня в городе тёплая погода. Днём температура поднимется до +21…+24 °C, к вечеру столбик термометра опустится до +17 °C. В течение дня переменная облачность, осадков не ожидается. Ветер северо‑западный, 8–13 м/с.
❤1👍1
В Белгороде на улице Архиерейской 6 августа произошло ДТП с участием внедорожника и мотоцикла. По предварительным данным, водитель джипа решил развернуться с крайней правой полосы, не убедившись в безопасности маневра. В этот момент по левой полосе двигался мотоциклист и совершил столкновение. К счастью, в результате аварии все участники остались живы.
❤1
🌲
🔥1🥰1
🌳Новооскольский дуб победил во всероссийском конкурсе «Российское дерево года — 2026» 📷: Администрация Новооскольского округа
👍16
🚔 За минувшие выходные дни сотрудники Госавтоинспекции выявили 33 нетрезвых водителя
📰 Орловская область заняла 51-е место в рейтинге качества дорог. Нормативам соответствует лишь 50,7% региональных трасс. Лидируют Москва, Челябинская область и Ингушетия. Замыкают список Кировская, Волгоградская и Архангельская области.
В четверг в Нижнем Ольшанце Белгородского округа обнаружили боеприпасы времён Великой Отечественной войны. На берегу водохранилища в микрорайоне Изумрудный нашли 81-мм мину и гранату РГ-42. Взрывотехники вывезли опасные находки на полигон и уничтожили.
👍1
Showing the 12 most recent of 22 posts we hold for @r31belgorod. 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.
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 10 September 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 1 seed channel's Telegram-generated recommendation list 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Регион 31 Белгород” (@r31belgorod), 31,474 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/r31belgorod.
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.