Telegram RegisterThe public register of Telegram
Telegram profile photo for Жесть Белгород

Channel

Жесть Белгород

@zhest_belgorod

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Domains linked from posts · Referenced elsewhere · Cite this entry

587,700subscribers

-5,827 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 316,228–1,000,000.

Register entry

Telegram ID-1001283524369
TypeChannel
Username@zhest_belgorod
DescriptionГлавный канал Белгородской области! 💼 По вопросам рекламы: @reklama_bg1 📸 Прислать новость, фото или видео: @Predlozhka_zhest_bg 🏆Наша сетка каналов: @Solovey_Media РКН: https://clck.ru/3Gyz6z Биржа: https://telega.in/c/zhest_belgorod
Created10 March 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held67
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/zhest_belgorod

Topic

International news — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 61% 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 7 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
@elite_belgorod_31/4450019 Aug 2026, 06:30 UTC@zhest_belgorod/72934 · this entry19 Aug 2026, 06:30 UTC1.00under a minute
@elite_belgorod_31/4559729 Sept 2026, 15:00 UTC@zhest_belgorod/74212 · this entry29 Sept 2026, 15:00 UTC1.00under a minute
@elite_belgorod_31/4561830 Sept 2026, 06:30 UTC@zhest_belgorod/74221 · this entry30 Sept 2026, 06:30 UTC1.00under a minute
@elite_belgorod_31/4630127 Oct 2026, 06:50 UTC@zhest_belgorod/75060 · this entry27 Oct 2026, 07:40 UTC1.0050 minutes
@elite_belgorod_31/464672 Nov 2026, 18:17 UTC@zhest_belgorod/75260 · this entry2 Nov 2026, 18:18 UTC1.00under a minute
@zhest_belgorod/72803 · this entry14 Aug 2026, 09:00 UTC@stroitel_online_31/3506014 Aug 2026, 10:00 UTC1.0060 minutes
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
@elite_belgorod_3114 (8/8 hand-verifiable sample passed)1.00under a minute@elite_belgorod_31 (9–5)
@stroitel_online_3111 (8/8 hand-verifiable sample passed)1.0060 minutesthis entry (10–1)
@bel31online11 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (9–2)
@belplus_bg12 (8/8 hand-verifiable sample passed)1.0048 minutesthis entry (9–3)
@rachsbelgorod8 (8/8 hand-verifiable sample passed)0.922 minutesthis entry (8–0)
@belgorod_vkurse248 (8/8 hand-verifiable sample passed)0.9314 minutesthis entry (8–0)
@belgorod_afisha_3110 (8/8 hand-verifiable sample passed)1.00under a minute@belgorod_afisha_31 (8–2)

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. 15 of the 15 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 1,909 comparable posts for this entry, running 5 August 2026 to 14 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 · clone_source, last confirmed 15 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

587,700595,047591,373.56 August 202615 November 2026
67 measurements spanning 101 days, net -5,827. 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 586,598–596,149 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 67
Measured (UTC)SubscribersChange
15 Nov 2026, 06:11587,700-364
11 Nov 2026, 21:40588,064-205
10 Nov 2026, 00:06588,269-204
8 Nov 2026, 12:10588,473-119
7 Nov 2026, 07:09588,592-135
6 Nov 2026, 03:47588,727-155
5 Nov 2026, 06:46588,882-90
4 Nov 2026, 08:36588,972-173
3 Nov 2026, 11:54589,145-104
2 Nov 2026, 12:49589,249-177
1 Nov 2026, 11:58589,426-120
31 Oct 2026, 10:49589,546-108
30 Oct 2026, 11:17589,654-72
29 Oct 2026, 13:56589,726-77
27 Oct 2026, 13:11589,803+11
26 Oct 2026, 13:01589,792+609
25 Oct 2026, 10:41589,183+1,451
24 Oct 2026, 12:15587,732-103
23 Oct 2026, 13:21587,835-142
22 Oct 2026, 12:26587,977first reading

Engagement

2,023 posts held, back to 5 August 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 205 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.43%
avg views ÷ 587,700 subscribers
Avg views / post
26,100
599 posts measured
Reaction rate
0.598%
reactions ÷ views · ER floor
Posts in window
599
of 2,023 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 November 2026
Posts held2,023 (5 August 2026 – 15 November 2026)
Views total15,606,032
Reactions total93,297
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 13:57 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
≈30,100
Videos
≈14,400
Links
≈34,700

Lifetime counters from Telegram’s own channel header, read 15 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
2h 01m
Average length
29s

Measured directly from 256 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

154,888 reactions across 999 posts, in 10 distinct kinds. The most used accounts for 38.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬60,04138.8%
🔥29,16218.8%
❤20,56813.3%
🙏18,71312.1%
😱9,2926.00%
🙉7,5604.88%
🤯3,1232.02%
🤨2,6921.74%
🤔2,2071.42%
😐1,5300.988%

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 999 of the 1,000 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 154,888 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 25 September 2026 to 15 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 Stars

Stars received
78
across the posts below
Posts paid on
46
of 1,000 we hold a reading for · 5%
Most on one post
10
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @zhest_belgorod. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 25 September 2026 to 15 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
2.40%
24 of 1,000 posts carry an ad marker
Regulatory tokens
24
posts carrying an erid · 18 distinct tokens
Median views · ads
22,300
over 24 measured posts
Median views · rest
25,400
over 976 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
2VtzqxKd9ja425 September 202616 October 2026
2Vtzqvdj342211 November 202613 November 2026
2VtzqwYHGoo230 October 20266 November 2026
2VtzqxkvnKe227 September 202629 September 2026
2Vtzquir53j123 October 202623 October 2026
2Vtzquj1VXA130 September 202630 September 2026
2Vtzqupsxbw16 October 20266 October 2026
2VtzqvLViGD19 October 20269 October 2026
2VtzqvxD8Ln12 November 20262 November 2026
2VtzqvzkyRo116 October 202616 October 2026
2Vtzqw75S3p110 November 202610 November 2026
2VtzqwFzN2r110 November 202610 November 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. 6 further tokens are held for this entry and not listed here.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 25 September 2026 to 15 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: 52 of 599 posts held from the last 30 days (8.68%) 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).

15 Nov 2026, 12:43 UTC≈6,580 views16 reactionsread 15 November 2026

Posted without readable text

🙉11❤2🤬2🤨1

15 Nov 2026, 10:49 UTC≈12,700 views108 reactionsread 15 November 2026

❗️Четверо мирных жителей пострадали при атаках ВСУ. В Волчьей Александровке Волоконовского округа дрон атаковал грузовик, ранен мужчина. В Шебекино беспилотник ударил по легковому автомобилю — пострадала женщина. Оба после оказания помощи продолжат лечение амбулаторно. Ещё двое пострадали в Дубовом Белгородского округа: мужчина получил ранение лица, женщина — голени. Их доставляют в городскую больницу №2 Белгорода.…

🤬55🔥31❤10🙏10🤨1😐1

15 Nov 2026, 09:15 UTC≈15,500 views71 reactionsread 15 November 2026

❗️Опасность атаки БПЛА в Белгороде Больше информации о происшествиях на территории области публикуем в нашем MAX 🇷🇺 👇👇👇 https://max.ru/zhest_belgorod

🔥28🤬26🙏7😱4❤2🤨2😐2

15 Nov 2026, 08:36 UTC≈17,500 views109 reactionsread 15 November 2026
Photo

🔊Белгородскую область за сутки атаковали 131 раз. Сбиты и подавлены 166 беспилотников. Под ударами оказались 12 округов. Зафиксировано семь артобстрелов и пять сбросов взрывных устройств с БПЛА. В Белгородском и Валуйском округах ранены два мирных жителя. Оба госпитализированы, им оказывают необходимую медицинскую помощь. Больше информации о происшествиях на территории области публикуем в нашем MAX 🇷🇺 👇👇👇 https:/…

🤬44🔥32❤16🙏12😱3😐2

15 Nov 2026, 05:59 UTC≈22,800 views273 reactionsread 15 November 2026
Photo

🪵 Решил запастись дровами, но вместо этого может получить срок. 52-летнему жителю Старого Оскола грозит до двух лет лишения свободы за незаконную вырубку шести ясеней. О спиле деревьев в урочище возле села Монаково сообщил лесничий. Ущерб оценили примерно в 20 тысяч рублей. Полицейские установили, что мужчина приехал на тракторе, спилил деревья и вывез их к себе на участок. Там похищенную древесину и обнаружили со…

🙉165🤯48🤬28❤14🤨9🔥6🤔2😐1

14 Nov 2026, 18:18 UTC≈31,200 views277 reactionsread 15 November 2026
Photo

🤦 Уличные вандалы снова портят городское имущество. На этот раз пострадала входная дверь дома на Садовой, 29А. Надписи оставили прямо рядом с табличкой о видеонаблюдении, но даже это не остановило «художников». Больше информации о происшествиях на территории области публикуем в нашем MAX 🇷🇺 👇👇👇 https://max.ru/zhest_belgorod

🤬185❤37🔥32🤯6😱6😐5🤨2🙏2

14 Nov 2026, 17:33 UTC≈31,600 views172 reactionsread 15 November 2026

❗️В Валуйках мирный житель пострадал при атаке FPV-дрона. Беспилотник ударил по объекту инфраструктуры. Мужчина получил осколочное ранение живота, его госпитализировали. Больше информации о происшествиях на территории области публикуем в нашем MAX 🇷🇺 👇👇👇 https://max.ru/zhest_belgorod

🤬81🔥46🙏23❤9🤯7🤨4😐2

14 Nov 2026, 16:37 UTC≈32,200 views266 reactionsread 15 November 2026
Video

🎄 По улицам Белгорода вновь запустят праздничный новогодний автобус. Транспорт украсят гирляндами и ёлкой, используя декорации прошлых лет. Автобус будет курсировать две недели до Нового года и ещё две — после. Номер маршрута назовут ближе к запуску. В прошлом году праздничный автобус работал на маршруте № 8. Больше информации о происшествиях на территории области публикуем в нашем MAX 🇷🇺 👇👇👇 https://max.ru/zhest…

❤142🤬61🤨23🙉15🔥9🙏6🤔5😱5

14 Nov 2026, 15:34 UTC≈29,400 views201 reactionsread 15 November 2026

❗️В результате атак ВСУ пострадал мирный житель Белгородской области. В селе Отрадное Белгородского округа FPV-дрон атаковал мужчину. Он получил осколочные ранения спины и ног. Пострадавшего доставили в Октябрьскую районную больницу, затем переведут в белгородскую горбольницу №2. В Шебекино дроны повредили две ГАЗели и балкон многоквартирного дома. В селе Нежеголь взрыв FPV-дрона выбил окна частного дома и повредил…

🤬97🔥57🙏21❤19😐3🤨2🙉2

14 Nov 2026, 14:35 UTC≈30,100 views473 reactionsread 15 November 2026
Video

🔊Показываем кадры с места трагедии в селе Пролетарском Ракитянского округа. Напомним, ночью беспилотник атаковал частный дом. В результате погибли три человека: мужчина, его жена и их 24-летняя дочь. Больше информации о происшествиях на территории области публикуем в нашем MAX 🇷🇺 👇👇👇 https://max.ru/zhest_belgorod

🤬265🙏83🔥65❤25😱21🤯8🤨5😐1

14 Nov 2026, 13:40 UTC≈29,700 views97 reactionsread 15 November 2026
Photo

В июле на ул. Елаговка в селе Короткое Корочанского района сделали ямочный ремонт, но сейчас на месте бывших ям снова стоят огромные лужи. Жители просят обратить внимание на состояние дороги. Больше информации о происшествиях на территории области публикуем в нашем MAX 🇷🇺 👇👇👇 https://max.ru/zhest_belgorod

😱41🤬31🔥15❤6😐3🤨1

14 Nov 2026, 12:49 UTC≈29,600 views187 reactionsread 15 November 2026

⚡️ В Белгородской области 17-летнего подростка обвиняют в государственной измене. По данным следствия, с августа по сентябрь 2025 года житель Губкинского округа контактировал с представителями украинских спецслужб. По их заданию он собирал и передавал сведения, которые могли быть использованы против безопасности России. Противоправную деятельность пресекли силовики. Прокуратура утвердила обвинительное заключение, у…

🤯76🤬55❤23🔥14🤔7🙉7🤨2😱2

Showing the 12 most recent of 2,023 posts we hold for @zhest_belgorod. 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

@zhest_belgorod 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
10 October 2026
Most recent edit
16 October 2026

Forward network

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

Named by 21 registered channels — 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.

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.

Настоящий Гладков
@vvgladkov · 398,330
#1
Белгород №1
@belgorod01 · 189,295
#2
Блэтгород
@bletgorod · 106,261
#3
Радар Белгород
@radarb31 · 137,248
#4
БелПлюс
@belplus_bg · 70,331
#5
Жесть Курск
@zhest_kursk_146 · 91,204
#6
БЕЛГОРОДЕЦ
@belgorodecRU · 91,918
#7
СВО 2024
@zalpom31_2 · 67,760
#8
Белгород — Молния
@bbbelgorod · 48,774
#9
grohot_pgr
@grohot_pgr · 28
#10
Жесть Шебекино
@zhest_shebekino_channel · 60,703
#11
Белгород С-400🚀🇷🇺
@belgorodc400 · 49,050
#12
Белгородский Андеграунд
@undeground_belgorod_31 · 33,758
#13
Белгородская область оповещения, тревоги
@lpr1_Belgorod_alarm · 56,957
#14
Элитный Белгород
@elite_belgorod_31 · 32,025
#15
Приграничный Радар
@prigranichie_radar1 · 32,130
#16
Взрывы Белгород🇷🇺
@vzrivi_belgorod1 · 34,182
#17
КУРСКИЙ БОМОНДЪ
@kurskbomond · 224,546
#18
bel31online
@bel31online · 7
#19
Вышка
@vyshka_newss · 63,562
#20
Оперштаб Курской области 🇷🇺
@gubernator_46 · 182,482
#21
Типичный Курск
@tipich_kursk · 150,205
#22
ЧП Белгород
@chp_bel · 62,996
#23
Шёпот Шебекино
@club_shebekino · 48,665
#24
Строитель Онлайн
@stroitel_online_31 · 26,639
#25
Go31 | Новости Белгорода
@belgorod_go31 · 35,097
#26
Авто Белгород
@avto_belgorod31 · 25,598
#27
СУДЖА РОДНАЯ 🇷🇺
@rodnaya_sudzha · 71,120
#28
Казачья Лопань Z
@kozacha23 · 39,515
#29
Белгород | ФОНАРЬ🔦
@fonartv · 26,893
#30
Красная Яруга🇷🇺Ракитное Приграничье
@yaruga31 · 35,610
#31
🚨Белгород | Live
@belgorod_live1 · 13,533
#32
ШÖ ❓ Шебекино
@Sho_Shebekino · 30,889
#33
РСЧС Приграни́чье
@Rschs_prigranichie1 · 34,119
#34
Просто Михаил Шебекино 📸
@mfoto31 · 46,349
#35
Красная Яруга🇷🇺
@krasnaya_yaruga31 · 29,560
#36
Белгород №1. Жизнь
@belgorod01people · 38,026
#37
Бел.Ру | Новости Белгорода
@IABelRu · 34,326
#38
Белгород Сирена🚨🇷🇺
@belgorod_sirena31 · 12,995
#39
Жесть Воронеж
@zhest_voronezh_136 · 61,926
#40
Группировка «СЕВЕР»|Приграничье
@grp_sever · 33,746
#41
Пепел ➜ Белгород
@belpepel · 168,893
#42
Белорусский силовик
@belarusian_silovik · 449,733
#43
Белгородский канал
@channelbel · 7,218
#44
МИГ России
@mig41 · 475,372
#45
Белгород Правда
@belpravda31 · 15,660
#46
Инцидент Белгород
@incbgd · 9,337
#47
МАЛИКОВЪ
@steelmalikov · 14,058
#48
Белгородчина31🇷🇺
@belgorodchina31 · 6,729
#49
Старый Оскол !NEWS
@belgorod_best31 · 7,599
#50
ЧС Приграни́чье
@rschs_prigranichie · 27,854
#51
Zона приграничья🇷🇺
@glaZ_graniZa · 20,601
#52
Тревожный Старый Оскол
@sta_oskol · 83,990
#53
Мир сегодня с "Юрий Подоляка"
@yurasumy · 2,661,091
#54
ZАПИСКИ VЕТЕРАНА 🇷🇺
@notes_veterans · 273,485
#55
Прямой Эфир • Новости
@novosti_efir · 3,875,626
#56
Readovka
@readovkanews · 2,011,824
#57
Раньше всех. Ну почти.
@bbbreaking · 1,975,202
#58
Baza
@bazabazon · 1,556,528
#59
Операция Z: Военкоры Русской Весны
@rvvoenkor · 1,451,986
#60
SHOT
@shot_shot · 1,265,323
#61
Хуйовий Харків 🇺🇦 Хуевый Харьков
@huyovy_kharkiv · 463,751
#62
Тринадцатый.
@Z13_Separ · 208,366
#63
Поддубный |Z|О|V| edition
@epoddubny · 567,310
#64
Старше Эдды
@vysokygovorit · 484,806
#65
Т-Воронеж | Типичный | Новости Воронежа
@typicalvoronezh · 373,120
#66
Пегасий БелГУ
@bsuedu · 7,756
#67
Повёрнутые на войне 🇷🇺
@voenacher · 657,808
#68
Kotsnews
@sashakots · 469,228
#69
Минобороны России
@mod_russia · 649,285
#70
Украина.ру
@ukr_2025_ru · 493,820
#71
Харків 1654 | Місто-герой 🇺🇦
@kharkiv_1654 · 243,176
#72
Военкор Котенок
@voenkorKotenok · 308,376
#73
Mash
@mash · 3,138,471
#74
Хроники Вальдемара🇩🇪 <3
@chronicsofwaldemar · 1,005
#75

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

Белгород Подслушано
@Belgorod5 · 50,267
Telegram ranks this channel #1 of 78 here — alongside 77 others — read 29 September 2026
Белгородский Осведомитель
@belgorod_informant · 22,220
Telegram ranks this channel #1 of 82 here — alongside 81 others — read 20 September 2026
Авто Белгород
@avto_belgorod31 · 25,598
Telegram ranks this channel #1 of 83 here — alongside 82 others — read 14 September 2026
Белгород * Новости * Важное
@Belgorod_vajnoe · 26,739
Telegram ranks this channel #1 of 41 here — alongside 40 others — read 12 September 2026
Строитель Онлайн
@stroitel_online_31 · 26,639
Telegram ranks this channel #1 of 33 here — alongside 32 others — read 11 September 2026
Регион 31 Белгород
@r31belgorod · 31,223
Telegram ranks this channel #1 of 81 here — alongside 80 others — read 10 September 2026
Белгород | Интересное | Новости
@belgorod_life · 27,798
Telegram ranks this channel #1 of 70 here — alongside 69 others — read 10 September 2026
Приграничный Радар
@prigranichie_radar1 · 32,130
Telegram ranks this channel #1 of 68 here — alongside 67 others — read 5 September 2026
Элитный Белгород
@elite_belgorod_31 · 32,025
Telegram ranks this channel #1 of 74 here — alongside 73 others — read 4 September 2026
Белгородский Андеграунд
@undeground_belgorod_31 · 33,758
Telegram ranks this channel #1 of 82 here — alongside 81 others — read 4 September 2026
Взрывы Белгород🇷🇺
@vzrivi_belgorod1 · 34,182
Telegram ranks this channel #1 of 82 here — alongside 81 others — read 3 September 2026
Бел.Ру | Новости Белгорода
@IABelRu · 34,326
Telegram ranks this channel #1 of 86 here — alongside 85 others — read 3 September 2026
Go31 | Новости Белгорода
@belgorod_go31 · 35,097
Telegram ranks this channel #1 of 83 here — alongside 82 others — read 2 September 2026
Казачья Лопань Z
@kozacha23 · 39,515
Telegram ranks this channel #1 of 84 here — alongside 83 others — read 30 August 2026
Белгород
@belgorod_tg · 38,637
Telegram ranks this channel #1 of 81 here — alongside 80 others — read 30 August 2026
bel31online
@bel31online · 7
Telegram ranks this channel #1 of 82 here — alongside 81 others — read 27 August 2026
ВОЙНА НА УКРАИНЕ СВО УКРАИНА
@novostydhd · 54,107
Telegram ranks this channel #1 of 57 here — alongside 56 others — read 23 August 2026
Жесть Шебекино
@zhest_shebekino_channel · 60,703
Telegram ranks this channel #1 of 59 here — alongside 58 others — read 22 August 2026
ЧП Белгород
@chp_bel · 62,996
Telegram ranks this channel #1 of 85 here — alongside 84 others — read 21 August 2026
Новости Белгорода и Области
@belgorod_smi · 63,253
Telegram ranks this channel #1 of 68 here — alongside 67 others — read 21 August 2026
Вышка
@vyshka_newss · 63,562
Telegram ranks this channel #1 of 80 here — alongside 79 others — read 21 August 2026
СВО 2024
@zalpom31_2 · 67,760
Telegram ranks this channel #1 of 69 here — alongside 68 others — read 20 August 2026
БелПлюс
@belplus_bg · 70,331
Telegram ranks this channel #1 of 80 here — alongside 79 others — read 20 August 2026
Жесть Курск
@zhest_kursk_146 · 91,204
Telegram ranks this channel #1 of 82 here — alongside 81 others — read 17 August 2026

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

Domains linked from posts

One domain this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

max.ru34 posts · 5 August 2026 – 7 August 2026 · example post

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Attacks in Russia during the Russo-Ukrainian war (2022–present) (en.wikipedia.org)
“…Белгород |url=https://t.me/zhest_belgorod/36741 |url-status=live |archive-url=https://web.archive.org/web/20240102122830/https://t.me/zhest_belgorod/36741…”
read 1 November 2026

Hacker News

This handle was named 2 times in a Hacker News comment or story, via the public Algolia search API. HN comment and story text has no confirmed reuse licence, so nothing quoted from either is reproduced here — only that a mention exists, when, and by whom, with a link to read it at the source.

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 15 November 2026 — this entry's latest reading, not the date you are reading this.

“Жесть Белгород” (@zhest_belgorod), 587,700 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/zhest_belgorod.

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.