Telegram RegisterThe public register of Telegram
Telegram profile photo for ЧП Белгород

Channel

ЧП Белгород

@chp_bel

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

63,036subscribers

-795 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001351170357
TypeChannel
Username@chp_bel
DescriptionПредложить новость: @Chp31bot Новостной портал Белгорода и области Реклама: @Engage_suBot, @Olha605 Мы в ВК - https://vk.com/bel_obl_chp
Created26 February 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held62
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/chp_bel

Topic

Local community — 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 98% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 3 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@chp_bel/29886 · this entry9 Aug 2026, 20:46 UTC@myregion48/172939 Aug 2026, 20:46 UTC1.00under a minute
@chp_bel/29991 · this entry15 Aug 2026, 20:59 UTC@myregion48/1732515 Aug 2026, 20:59 UTC1.00under a minute
@chp_bel/30023 · this entry18 Aug 2026, 09:15 UTC@myregion48/1733118 Aug 2026, 09:16 UTC1.00under a minute
@myregion48/174426 Sept 2026, 18:12 UTC@chp_bel/30256 · this entry6 Sept 2026, 18:13 UTC1.00under a minute
@chp_bel/30572 · this entry28 Sept 2026, 20:38 UTC@myregion48/1768728 Sept 2026, 20:40 UTC1.0072 seconds
@myregion48/1777411 Oct 2026, 20:23 UTC@chp_bel/30680 · this entry11 Oct 2026, 20:23 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@myregion4849 (8/8 hand-verifiable sample passed)1.00under a minute@myregion48 (26–23)
@chp_st_oskol33 (8/8 hand-verifiable sample passed)0.97under a minute@chp_st_oskol (18–15)
@eto_yaroslavl6 (6/6 hand-verifiable sample passed)1.005.8 hours@eto_yaroslavl (5–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 49 of the 49 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 702 comparable posts for this entry, running 5 August 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the keys clone_copy · clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

63,03663,83163,433.56 August 202610 November 2026
62 measurements spanning 95 days, net -795. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 62,917–63,950 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)SubscribersChange
10 Nov 2026, 00:5163,036-8
8 Nov 2026, 14:1563,044-15
7 Nov 2026, 11:1763,059-13
6 Nov 2026, 09:1963,072-14
5 Nov 2026, 09:5663,086-10
4 Nov 2026, 08:4863,096-9
3 Nov 2026, 07:0663,105-1
2 Nov 2026, 06:2863,106-21
1 Nov 2026, 08:5663,127-19
31 Oct 2026, 07:5063,146-27
30 Oct 2026, 04:3863,173-24
29 Oct 2026, 06:5963,197-19
28 Oct 2026, 06:1163,216-29
27 Oct 2026, 05:3663,245-18
26 Oct 2026, 05:2063,263-31
25 Oct 2026, 01:4563,294-17
24 Oct 2026, 03:1663,311-7
23 Oct 2026, 02:2863,318-21
22 Oct 2026, 03:3663,339-13
20 Oct 2026, 19:2863,352first reading

Engagement

739 posts held, back to 5 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 199 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.99%
avg views ÷ 63,036 subscribers
Avg views / post
1,880
251 posts measured
Reaction rate
0.318%
reactions ÷ views · ER floor
Posts in window
251
of 739 held

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 249 of 251 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 November 2026
Posts held739 (5 August 2026 – 10 November 2026)
Views total472,334
Reactions total1,495
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 03:44 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.

What this channel posts

Photos
≈15,300
Videos
≈6,470
Links
≈12,500

Lifetime counters from Telegram’s own channel header, read 11 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.

Video runtime
17m 57s
Average length
12s

Measured directly from 91 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.

Reaction mix

4,185 reactions across 732 posts, in 8 distinct kinds. The most used accounts for 35.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,47535.2%
👍91721.9%
🤬91321.8%
🙏2626.26%
😢2445.83%
🤯2315.52%
😱1303.11%
🕊130.311%

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 732 of the 739 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,185 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 739 most recent posts we hold, published 5 August 2026 to 10 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.

Advertising

Ad load
11.8%
87 of 739 posts carry an ad marker
Regulatory tokens
87
posts carrying an erid · 75 distinct tokens
Median views · ads
2,010
over 87 measured posts
Median views · rest
1,860
over 652 measured posts

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.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzqwPNH23418 August 202621 August 2026
2VtzqxXeoFy39 August 20269 November 2026
2VtzqufxpHq23 September 20264 September 2026
2Vtzqv74Dvz25 August 20265 November 2026
2VtzqvHSosG26 August 20266 November 2026
2VtzqvwcEEg215 September 202616 September 2026
2Vtzqw2AEkU220 September 202621 September 2026
2VtzqwfFDgF27 August 20267 November 2026
2Vtzqx9Qz2o28 August 20268 November 2026
2SDnjeU9W52110 November 202610 November 2026
2VfnxvZxgt519 November 20269 November 2026
2VtzquZkiDr124 September 202624 September 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. 63 further tokens are held for this entry and not listed here.

Measured over the 739 most recent posts we hold, published 5 August 2026 to 10 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 251 posts held from the last 30 days (0.398%) 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).

10 Nov 2026, 18:25 UTC854 views4 reactionsread 11 November 2026
Advertisementerid 2VtzqwRqNvrPhoto

Реклама. Erid: 2VtzqwRqNvr Квартира, ремонт, машина — везде одна история: увидел, понравилось, купил. А потом выясняется, что то же самое можно было взять заметно дешевле. Телефон неделю выбираем, холодильник сравниваем, три тысячи ищем где дешевле. А на миллионах логика почему-то отключается. Пример с автомобилями. MAZDA CX-5: в РФ — 3 900 000 ₽, через AUTOPARK — 3 000 000 ₽, разница 900 000 ₽. NISSAN QASHQAI: 3 2…

❤4

10 Nov 2026, 16:49 UTC≈1,090 views3 reactionsread 11 November 2026

Белгородских главврачей отправят на трёхдневный курс по ИИ-агентам — учить будет Сбер Программу «ИИ-агенты в здравоохранении: внутренние драйверы изменений» разработали «Школа 21», СберМедИИ и ЦНИИОИЗ Минздрава. Ориентирована она на руководителей клиник, главврачей и специалистов по цифровому развитию. Формат такой: один день онлайн, два — очно на площадке «Школы 21». За это время участники разберут устройство ИИ-а…

❤3

10 Nov 2026, 15:13 UTC≈1,200 views5 reactionsread 11 November 2026

Смайлик-волейболист в Белгороде снова пострадал от хулиганов — на этот раз его не только испинали, но и погнули. Совсем недавно у скульптуры оторвали волейбольный мяч, виновных тогда поймали. Теперь камеры зафиксировали новых вандалов. Полиция установила участников повторного повреждения — оно случилось на следующий день после первого инцидента. По предварительным данным, к порче элемента фигуры причастны двое несо…

🤬5

10 Nov 2026, 13:37 UTC≈1,190 views4 reactionsread 11 November 2026
Advertisementerid 2SDnjeU9W52Photo

В 1989 году швейцарский сыровар Петер Глаузер из городка Белп под Берном случайно оставил в погребе партию свежих сырных шариков с чесноком и перцем. Они высохли до состояния камня — но вместо того чтобы выбросить, сыровары попробовали натереть их стружкой на горячее блюдо. Так появился Белпер Кнолле, который сегодня называют швейцарским сырным трюфелем. В ТМ «Сельские традиции» этот сыр варят в двух вариантах: с чё…

👍3❤1

10 Nov 2026, 12:57 UTC≈1,050 views1 reactionsread 11 November 2026
Advertisementerid 2VtzqurKbSKPhoto

Отчёты воруют твои вечера? 😩 Есть два типа помощников. Первые дадут инструкцию, как сделать. Вторые — сделают за тебя. Пятница, 17:00. Руководитель ждёт отчёт. Ты час копаешься в CRM, копируешь, вставляешь, строишь графики. Вечер насмарку. А можно просто написать «Мой агент»: «Собери недельный отчёт». Дальше он сам подключится к твоей amoCRM или Битрикс24, выгрузит данные, сделает графики, сводную таблицу и пришл…

👍1

10 Nov 2026, 12:01 UTC≈1,100 views5 reactionsread 11 November 2026
Photo

Белгородка Мария Осетрова взяла серебро чемпионата России по плаванию. Соревнования прошли в Санкт-Петербурге. На дистанции 50 метров на спине Мария показала 26,19 секунды — второе место. Этим результатом спортсменка выполнила отборочный норматив на чемпионат мира и повторила рекорд Белгородской области. Тренирует её Феликс Сидельник. Подписаться | Написать нам

👍5

10 Nov 2026, 10:25 UTC≈1,270 views6 reactionsread 11 November 2026
Photo

В Белгороде почти половина опрошенных назвала главной радостью месяца семью — а покупке нового автомобиля не порадовался никто. «Фонарь» провёл анонимный опрос среди читателей и попросил белгородцев назвать главный повод для улыбки за последний месяц. Участвовали 213 человек. 45 процентов выбрали семью. По 15 процентов набрали зарплата и отпуск, восемь — работа, семь — сделка Путина с Трампом по дизелю. Успехи на С…

❤5🤯1

10 Nov 2026, 08:49 UTC≈1,360 views1 reactionsread 11 November 2026
Photo

Андрей Бубело покинул пост министра ЖКХ Белгородской области. Об этом стало известно редакции «Фонаря». Ведомство он возглавил 9 сентября 2026 года. Министром Бубело проработал около двух месяцев. Подписаться | Написать нам

👍1

10 Nov 2026, 07:13 UTC≈1,490 views2 reactionsread 11 November 2026

Гороскоп на 10 ноября: Рыбам советуют прогулку, Овнам — не ждать мгновенного результата Звёзды сегодня напоминают: необязательно каждый день совершать подвиги, чтобы двигаться вперёд. Кому-то улыбнётся удача, а кому-то пора поверить в себя. Овнам сил больше, чем кажется, — главное не требовать от себя мгновенного результата. Тельцам стоит перестать сравнивать свои успехи с чужими, а вечером порадовать себя чем-нибу…

❤2

10 Nov 2026, 05:37 UTC≈1,550 views8 reactionsread 11 November 2026
Photo

50-летний боец из Старого Оскола Фёдор Емельяненко предложил провести показательный бой с Хабибом Нурмагомедовым. Емельяненко готов выйти на ковёр с бывшим чемпионом UFC, если Нурмагомедов поддержит идею. Одной из возможных площадок может стать следующий чемпионат мира по самбо. Пока Хабиб не подтвердил, что готов принять участие в поединке. Подписаться | Написать нам

❤7🤯1

Showing the 12 most recent of 739 posts we hold for @chp_bel. 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.

Posts edited after publishing

@chp_bel 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.

First edit seen
26 August 2026
Most recent edit
18 September 2026

Posts recorded as deleted after publishing

We recorded 6 posts on @chp_bel 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.

First seen missing
8 October 2026
Most recent seen missing
26 October 2026
Median time before seen missing
25 hours
Seen missing in the last 30 days
5

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

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.

Channels Telegram recommends alongside this 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.

Жесть Белгород
@zhest_belgorod · 588,269
#1
Настоящий Гладков
@vvgladkov · 398,604
#2
Радар Белгород
@radarb31 · 137,296
#3
Белгород №1
@belgorod01 · 189,419
#4
Блэтгород
@bletgorod · 106,297
#5
БелПлюс
@belplus_bg · 70,366
#6
Белгород С-400🚀🇷🇺
@belgorodc400 · 49,068
#7
БЕЛГОРОДЕЦ
@belgorodecRU · 91,989
#8
grohot_pgr
@grohot_pgr · 30
#9
Белгород — Молния
@bbbelgorod · 48,790
#10
Белгородский Андеграунд
@undeground_belgorod_31 · 33,767
#11
Жесть Шебекино
@zhest_shebekino_channel · 60,718
#12
Взрывы Белгород🇷🇺
@vzrivi_belgorod1 · 34,186
#13
bel31online
@bel31online · 7
#14
Просто Михаил Шебекино 📸
@mfoto31 · 46,347
#15
Авто Белгород
@avto_belgorod31 · 25,598
#16
СВО 2024
@zalpom31_2 · 67,828
#17
ОК! Старый Оскол
@okoskol · 69,808
#18
Казачья Лопань Z
@kozacha23 · 39,532
#19
Белгород | ФОНАРЬ🔦
@fonartv · 26,899
#20
ШÖ ❓ Шебекино
@Sho_Shebekino · 30,893
#21
Шёпот Шебекино
@club_shebekino · 48,685
#22
ЧП Оскол
@chp_st_oskol · 28,543
#23
Бел.Ру | Новости Белгорода
@IABelRu · 34,341
#24
🇷🇺ОперСводки 31🇷🇺
@opersvodki_belgorod · 18,567
#25
Белгородчина31🇷🇺
@belgorodchina31 · 6,734
#26
Приграничный Радар
@prigranichie_radar1 · 32,154
#27
ЧС Приграни́чье
@rschs_prigranichie · 27,890
#28
Красная Яруга🇷🇺
@krasnaya_yaruga31 · 29,600
#29
Go31 | Новости Белгорода
@belgorod_go31 · 35,112
#30
РСЧС|БПЛА|Белгородская область
@rchs_belgorod · 9,868
#31
Пепел ➜ Белгород
@belpepel · 169,162
#32
БелГородские подробности
@bel_podrobnosti · 7,132
#33
Тревожный Старый Оскол
@sta_oskol · 84,069
#34
Белгородский канал
@channelbel · 7,227
#35
Zона приграничья🇷🇺
@glaZ_graniZa · 20,609
#36
📬Открытый Белгород
@openbelgorod · 5,751
#37
Жесть Курск
@zhest_kursk_146 · 91,276
#38
Оперштаб Белгородской области
@operativno31 · 15,389
#39
Элитный Белгород
@elite_belgorod_31 · 32,052
#40
Белгород Правда
@belpravda31 · 15,674
#41
МАЛИКОВЪ
@steelmalikov · 14,046
#42
Белгород Сирена🚨🇷🇺
@belgorod_sirena31 · 12,995
#43
Белгород NEWS
@belnews_belgorod · 16,736
#44
Группировка «СЕВЕР»|Приграничье
@grp_sever · 33,759
#45
🚨Белгород | Live
@belgorod_live1 · 13,548
#46
Валуйки Телега
@tgvaluyki · 30,466
#47
Тринадцатый.
@Z13_Separ · 208,541
#48
belgorod_vkurse24
@belgorod_vkurse24 · 27
#49
Мэрия Белгорода
@beladm31 · 6,741
#50
Валуйки
@valuyki31 · 6,492
#51
Старый Оскол !NEWS
@belgorod_best31 · 7,601
#52
РСЧС Приграни́чье
@Rschs_prigranichie1 · 34,128
#53
🚀Приграничный Наблюдатель🇷🇺
@ZOV_granicy · 11,598
#54
Поддубный |Z|О|V| edition
@epoddubny · 568,057
#55
Инцидент Белгород
@incbgd · 9,340
#56
МЧС Белгородской области
@mchs31 · 18,407
#57
Мониторинг Белгород | 31 Регион
@rschs31 · 16,490
#58
Мир Белогорья
@mirbelogorya · 12,263
#59
БелПресса | Новости Белгорода и Белгородской области
@belpressa · 2,878
#60
Белгород-медиа
@belgorodmedia24 · 4,253
#61
Красная Яруга🇷🇺Ракитное Приграничье
@yaruga31 · 35,630
#62
Правительство Белгородской области
@belregion_ru · 4,565
#63
Грайворонский муниципальный округ
@graivoron_okrug · 5,305
#64
ВАЛУЙКИ ПОДСЛУШАНО
@valuykitg · 9,818
#65
Геннадий Бондарев
@bondarev_gennadi · 1,752
#66
онлайн 31🇷🇺
@onlain31 · 5,454
#67
Грайворон 💛
@pulsegrayvorona · 10,965
#68
Белгородский Осведомитель
@belgorod_informant · 22,233
#69
ЧП Белгородская область
@chpbelgorod · 35,749
#70
Oskol Stelit | Старый Оскол
@oskol_stelit_31 · 28,722
#71
БелТру • Новости Белгорода и области
@beltrue · 2,747
#72
Лимон | Белгород
@bel_lemon · 2,769
#73
ZАПИСКИ VЕТЕРАНА 🇷🇺
@notes_veterans · 273,805
#74
Мир сегодня с "Юрий Подоляка"
@yurasumy · 2,662,248
#75
Readovka
@readovkanews · 2,012,342
#76
Белгород №1. Жизнь
@belgorod01people · 38,048
#77
Прямой Эфир • Новости
@novosti_efir · 3,880,315
#78
SHOT
@shot_shot · 1,265,878
#79
Операция Z: Военкоры Русской Весны
@rvvoenkor · 1,452,307
#80
Старше Эдды
@vysokygovorit · 485,001
#81
Хуйовий Харків 🇺🇦 Хуевый Харьков
@huyovy_kharkiv · 464,400
#82
ТРУДНЫЙ ТОКОВ
@tokov · 3,214
#83
УРАЗОВО говорит 🇷🇺
@urazovo · 9,568
#84
Короча Наизнанку 🌎
@korocha_iz · 9,093
#85

Read from Telegram’s recommendation API, most recently 21 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.

Appears in Telegram’s recommendations for other channels

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.

Регион 31 Белгород
@r31belgorod · 31,234
Telegram ranks this channel #8 of 81 here — alongside 80 others — read 10 September 2026
Белгород | Интересное | Новости
@belgorod_life · 27,799
Telegram ranks this channel #9 of 70 here — alongside 69 others — read 10 September 2026
ЧП Оскол
@chp_st_oskol · 28,543
Telegram ranks this channel #12 of 32 here — alongside 31 others — read 9 September 2026
Белгородский Осведомитель
@belgorod_informant · 22,233
Telegram ranks this channel #13 of 82 here — alongside 81 others — read 20 September 2026
Oskol Stelit | Старый Оскол
@oskol_stelit_31 · 28,722
Telegram ranks this channel #13 of 30 here — alongside 29 others — read 9 September 2026
Валуйки Телега
@tgvaluyki · 30,466
Telegram ranks this channel #14 of 52 here — alongside 51 others — read 6 September 2026
Белгородский Андеграунд
@undeground_belgorod_31 · 33,767
Telegram ranks this channel #15 of 82 here — alongside 81 others — read 4 September 2026
bel31online
@bel31online · 7
Telegram ranks this channel #15 of 82 here — alongside 81 others — read 27 August 2026
ВАЛУЙКИ "Z" O" V"🇷🇺🫡
@valyikizoov · 19,629
Telegram ranks this channel #16 of 51 here — alongside 50 others — read 30 September 2026
Авто Белгород
@avto_belgorod31 · 25,598
Telegram ranks this channel #16 of 83 here — alongside 82 others — read 14 September 2026
ОК! Старый Оскол
@okoskol · 69,808
Telegram ranks this channel #16 of 37 here — alongside 36 others — read 20 August 2026
Белгород
@belgorod_tg · 38,663
Telegram ranks this channel #18 of 81 here — alongside 80 others — read 30 August 2026
Пепел ➜ Белгород
@belpepel · 169,162
Telegram ranks this channel #19 of 89 here — alongside 88 others — read 12 August 2026
Элитный Белгород
@elite_belgorod_31 · 32,052
Telegram ranks this channel #20 of 74 here — alongside 73 others — read 4 September 2026
Белгород — Молния
@bbbelgorod · 48,790
Telegram ranks this channel #20 of 88 here — alongside 87 others — read 26 August 2026
БелПлюс
@belplus_bg · 70,366
Telegram ranks this channel #20 of 80 here — alongside 79 others — read 20 August 2026
Блэтгород
@bletgorod · 106,297
Telegram ranks this channel #20 of 81 here — alongside 80 others — read 15 August 2026
ЧС Приграни́чье
@rschs_prigranichie · 27,890
Telegram ranks this channel #21 of 73 here — alongside 72 others — read 9 September 2026
Взрывы Белгород🇷🇺
@vzrivi_belgorod1 · 34,186
Telegram ranks this channel #21 of 82 here — alongside 81 others — read 3 September 2026
Радар Белгород
@radarb31 · 137,296
Telegram ranks this channel #21 of 79 here — alongside 78 others — read 13 August 2026
Белгород №1
@belgorod01 · 189,419
Telegram ranks this channel #21 of 84 here — alongside 83 others — read 11 August 2026
ШÖ ❓ Шебекино
@Sho_Shebekino · 30,893
Telegram ranks this channel #22 of 57 here — alongside 56 others — read 6 September 2026
Новости Белгорода и Области
@belgorod_smi · 63,356
Telegram ranks this channel #22 of 68 here — alongside 67 others — read 21 August 2026
Белгородчина
@belgorpost · 63,016
Telegram ranks this channel #23 of 89 here — alongside 88 others — read 22 August 2026

This channel appears in 45 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.

Cite this entry

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.

“ЧП Белгород” (@chp_bel), 63,036 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/chp_bel.

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.