Telegram RegisterThe public register of Telegram
Telegram profile photo for Новости Брянска

Channel

Новости Брянска

@barakholka32

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

64,100subscribers

-566 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-1001526637248
TypeChannel
Username@barakholka32
DescriptionЛента всех событий: Новости, Происшествия, ЧП, ДТП Брянск и Брянская область. По всем вопросам: @BROKER6
Created27 August 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live19 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/barakholka32

Topic

National 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 10 August 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.

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 word for word on 2 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
@E_V_Kovalchuk/16715 Aug 2026, 06:07 UTC@barakholka32/18399 · this entry5 Aug 2026, 06:46 UTC1.0040 minutes
@E_V_Kovalchuk/16836 Aug 2026, 06:13 UTC@barakholka32/18403 · this entry6 Aug 2026, 06:13 UTC1.00under a minute
@E_V_Kovalchuk/16916 Aug 2026, 06:41 UTC@barakholka32/18407 · this entry6 Aug 2026, 06:44 UTC1.004 minutes
@E_V_Kovalchuk/16926 Aug 2026, 07:07 UTC@barakholka32/18410 · this entry6 Aug 2026, 07:11 UTC1.004 minutes
@E_V_Kovalchuk/16987 Aug 2026, 06:13 UTC@barakholka32/18418 · this entry7 Aug 2026, 06:13 UTC1.00under a minute
@E_V_Kovalchuk/16997 Aug 2026, 12:32 UTC@barakholka32/18421 · this entry7 Aug 2026, 12:32 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@E_V_Kovalchuk8 (8/8 hand-verifiable sample passed)1.004 minutes@E_V_Kovalchuk (80)
@koronavirus327 (7/7 hand-verifiable sample passed)1.004 minutes@koronavirus32 (52)

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. 11 of the 13 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 15 comparable posts for this entry, running 4 August 2026 to 7 August 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).

Across the whole group of 3, the earliest publisher we hold is @E_V_Kovalchuk. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

64,10064,66664,3836 August 2026 — 64,666 subscribers6 August 2026 — 64,652 subscribers7 August 2026 — 64,653 subscribers8 August 2026 — 64,645 subscribers9 August 2026 — 64,632 subscribers10 August 2026 — 64,622 subscribers11 August 2026 — 64,606 subscribers12 August 2026 — 64,572 subscribers14 August 2026 — 64,556 subscribers15 August 2026 — 64,588 subscribers16 August 2026 — 64,569 subscribers17 August 2026 — 64,541 subscribers19 August 2026 — 64,515 subscribers20 August 2026 — 64,499 subscribers21 August 2026 — 64,468 subscribers22 August 2026 — 64,452 subscribers24 August 2026 — 64,429 subscribers25 August 2026 — 64,404 subscribers26 August 2026 — 64,391 subscribers27 August 2026 — 64,366 subscribers28 August 2026 — 64,353 subscribers29 August 2026 — 64,347 subscribers30 August 2026 — 64,338 subscribers31 August 2026 — 64,327 subscribers1 September 2026 — 64,317 subscribers2 September 2026 — 64,290 subscribers3 September 2026 — 64,262 subscribers6 September 2026 — 64,229 subscribers9 September 2026 — 64,221 subscribers11 September 2026 — 64,188 subscribers13 September 2026 — 64,168 subscribers15 September 2026 — 64,147 subscribers17 September 2026 — 64,116 subscribers19 September 2026 — 64,100 subscribers6 August 202619 September 2026
34 measurements spanning 44 days, net -566. 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 64,015–64,751 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
19 Sept 2026, 09:1964,100-16
17 Sept 2026, 01:1864,116-31
15 Sept 2026, 03:1964,147-21
13 Sept 2026, 15:3864,168-20
11 Sept 2026, 19:4164,188-33
9 Sept 2026, 07:5964,221-8
6 Sept 2026, 00:4064,229-33
3 Sept 2026, 19:4064,262-28
2 Sept 2026, 09:4764,290-27
1 Sept 2026, 06:2864,317-10
31 Aug 2026, 09:0464,327-11
30 Aug 2026, 11:3564,338-9
29 Aug 2026, 12:2564,347-6
28 Aug 2026, 12:1464,353-13
27 Aug 2026, 14:0464,366-25
26 Aug 2026, 11:4364,391-13
25 Aug 2026, 12:2364,404-25
24 Aug 2026, 09:4264,429-23
22 Aug 2026, 15:2764,452-16
21 Aug 2026, 07:3864,468first reading

Engagement

271 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 100 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
9.23%
avg views ÷ 64,100 subscribers
Avg views / post
5,910
159 posts measured
Reaction rate
0.741%
reactions ÷ views · ER floor
Posts in window
159
of 271 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 22 September 2026
Posts held271 (4 August 202622 September 2026)
Views total940,240
Reactions total6,967
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Sept 2026, 14:12 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
7,050
Videos
3,030
Links
831

Lifetime counters from Telegram’s own channel header, read 22 September 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
46m 40s
Average length
1m 00s

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

11,217 reactions across 271 posts, in 21 distinct kinds. The most used accounts for 19.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2,20819.7%
🙏1,65514.8%
🤣1,30311.6%
👍1,29511.5%
🤬9978.89%
😢9478.44%
🔥6455.75%
👎5264.69%
😱4263.80%
😁4043.60%
👀1571.40%
🥴1451.29%
🏆1351.20%
😭1211.08%
🤯870.776%
🤷‍♂580.517%
💯450.401%
🥰210.187%
🐳170.152%
🫡160.143%
1 further kind90.08%

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

Measured over the 271 most recent posts we hold, published 4 August 2026 to 22 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.

Telegram Stars

Stars received
14
across the posts below
Posts paid on
6
of 271 we hold a reading for · 2%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @barakholka32. 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 271 most recent posts we hold for this entry, published 4 August 2026 to 22 September 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.

Recent posts

22 Sept 2026, 12:03 UTC≈1,340 views3 reactionsread 22 September 2026

Экстренная информация РСЧС: Сильные дожди, грозы, порывы ветра 15-17 м/с ожидаются местами на территории Брянской области 23 сентября 2026 года (данные Брянского ЦГМС). В результате погодных условий возрастает вероятность перебоев с электроснабжением, повреждения имущества упавшими конструкциями и деревьями. Гражданам рекомендуется выбирать безопасные пути, не приближаться к оборванным проводам, автомобилистам выбира

3

22 Sept 2026, 08:12 UTC≈2,640 views29 reactionsread 22 September 2026

На Брянщине в двух приграничных районах запретили ночные поездки на мототранспорте В Климовском районе и Сельцовском городском округе Брянской области введён ночной запрет на передвижение на мототехнике. Соответствующий указ подписал и.о. губернатора Юрий Филипенко. Ограничения касаются всех категорий мототранспорта с L1 по L7: с 22:00 до 06:00 запрещено ездить на мопедах, мотоциклах, мотороллерах, трициклах и квад

👍21😁6🤣2

22 Sept 2026, 06:58 UTC≈2,810 views32 reactionsread 22 September 2026
Photo

Брянчанка завоевала золотую медаль на Кубке Мира по самбо Соревнования проходили в минувшие выходные в Душанбе, рассказали в региональном департаменте ФК и спорта. Блестящий результат показала брянская участница Ольга Брягиня. Она взяла золото в дисциплине «боевое самбо» в весовой категории до 50 килограммов. 📍Бронзовым призёром соревнований также стал брянец Александр Горохов. Он выступал в категории до 88 кило.

27🏆3👎2

21 Sept 2026, 16:43 UTC≈4,280 views103 reactionsread 22 September 2026
Photo

Краски осени.

62🔥23👍13👎5

21 Sept 2026, 15:43 UTC≈4,550 views20 reactionsread 22 September 2026
Video

❗️ВНИМАНИЕ ВСЕМ❗️ Продолжаются массивные атаки по всем регионам России. Наши ПВО за сутки сбивают ТЮСЯЧИ дронов. Во многих областях введен режим ЧРЕЗВЫЧАЙНОГО ПОЛОЖЕНИЯ. Всем настоятельно рекомендуем следить за ситуацией в специальных каналах вашего города! КАНАЛЫ БУДУТ РАБОТАТЬ ДАЖЕ БЕЗ МОБИЛЬНОЙ СВЯЗИ. Убедительная просьба, найти свой город и подписаться: Москва: @msklive Питер: @petrlive Абакан: @abknlive Арха

👎125🤣3

21 Sept 2026, 15:21 UTC≈4,140 views22 reactionsread 22 September 2026

Егор Ковальчук: Дрон-камикадзе атаковал движущийся гражданский автомобиль на автодороге «Стародуб — Клинцы». Осколочные ранения получил водитель, он госпитализирован. Еще один дрон ударил по грузовой автомашине возле села Мишковка Стародубского округа. Водитель ранен, ему назначено амбулаторное лечение. Желаю скорейшего выздоровления.

🤬14🔥3🤣31🙏1

21 Sept 2026, 08:32 UTC≈4,850 views50 reactionsread 22 September 2026
Video

Дрон атаковал машину с членом УИК в Стародубском районе Об этом сообщила Элла Памфилова. Женщина получила тяжелое осколочное ранение и на данный момент находится в больнице.

😁17🤬12🤯7😭7🤣32🔥2

21 Sept 2026, 06:25 UTC≈5,050 views29 reactionsread 22 September 2026

Егор Ковальчук: Трагедия в приграничье. Дрон-камикадзе атаковал жилой дом в селе Андрейковичи Погарского района. К большому горю, погиб хозяин. Выражаю глубокие соболезнования родным и близким погибшего. Окажем всю необходимую помощь. В результате атак дронов-камикадзе по движущимся автомобилям на автодороге Стародуб-Клинцы, а также вблизи села Картушин Стародубского района ранения получили двое мужчин и женщина. П

🤬18😢7🔥31

20 Sept 2026, 18:42 UTC≈5,750 views43 reactionsread 22 September 2026

Украинский дрон ударил по двигавшемуся скутеру в деревне Карпиловка Злынковского района Осколочные ранения получила женщина, сообщает врио губернатора. Пострадавшей оказывают медпомощь.

🤯15🤬13🤣6🔥4😢32

20 Sept 2026, 17:41 UTC≈5,940 views32 reactionsread 22 September 2026

По уточненной информации, при ударе украинского дрона по маршрутному такси в пригороде Стародуба осколочные ранения получила 15-летняя девочка. Пострадавшую доставили в больницу, где ей оказана вся необходимая медицинская помощь. Желаю скорейшего выздоровления!

😱215🥴3👍1🤣1🙏1

20 Sept 2026, 17:40 UTC≈5,950 views30 reactionsread 22 September 2026

Егор Ковальчук: Четыре человека ранены при ударе украинского дрона по маршрутному такси в пригороде Стародуба. Осколочные ранения получили три женщины и мужчина. Сгорела маршрутка автопредприятия. Еще один удар был нанесен по легковому автомобилю в Стародубе. Осколочные ранения получили двое мужчин. Всех пострадавших доставили в больницу, им оказана вся необходимая медицинская помощь.

🤬19😢10👀1

20 Sept 2026, 07:08 UTC≈6,300 views39 reactionsread 22 September 2026

Егор Ковальчук: В результате подрыва на взрывном устройстве ранения получил житель Злынки. Ему оказана вся необходимая медицинская помощь.Желаю скорейшего выздоровления! За прошедшие сутки над территорией Брянской области подразделениями ПВО Министерства обороны РФ, мобильно-огневыми группами бригады «БАРС-Брянск», МОГ Брянского ЛО МВД России на транспорте, спецподразделениями Росгвардии по Брянской области уничтоже

🙏26🔥5🤣3🥴2😱21

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

@barakholka32 edited 1 post 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
2 September 2026
Most recent edit
2 September 2026

Forward network

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.

Mentions

Named by 2 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

ПОДСЛУШАНО БРЯНСК
@pb_032 · 298,250
#1
ТИПИЧНЫЙ БРЯНСК | НОВОСТИ
@tipicl32 · 158,747
#2
Город Брянск
@br_gorod · 93,486
#3
Настоящий Типичный Брянск
@tipical32 · 46,523
#4
НОВОСТИ БРЯНСКА
@bra_32 · 41,448
#5
ЧП и ДТП Брянск
@bryansk_off32 · 59,737
#6
Приграничье Брянск 🇷🇺
@prigrani4ie · 54,390
#7
Жесть Брянск
@zhestbryansk_32 · 30,801
#8
Новости Курска
@barakholka46 · 12,076
#9
БРЯ | Новости и события Брянска
@bryansk_media · 26,882
#10
AV БогомаZ
@avbogomaz · 47,555
#11
Подслушано Клинцы (region_32)
@klintsyregion_32 · 52,586
#12
Readovka
@readovkanews · 2,012,262
#13
Жесть Белгород
@zhest_belgorod · 591,426
#14
grohot_pgr
@grohot_pgr · 2
#15
Новости Брянска
@newsbryanskru · 7,432
#16
Новости Брянска и Области
@bryansk_smi · 73,327
#17
Город Брянск
@br_gorod32 · 5,809
#18
Типичный Курск
@tipich_kursk · 151,420
#19
Брянск и новости
@bryandnews · 5,386
#20
Регион 32
@region32live · 15,479
#21
Тревожный Брянск
@nabat32 · 28,334
#22
Типичные Клинцы
@tipical_klintsy · 9,016
#23
Брянский Ворчун
@br_vorchun · 6,732
#24
Подслушано Климово
@klimovo32 · 21,773
#25
Жесть Курск
@zhest_kursk_146 · 92,206
#26
🔞ПОДСЛУШАНО БРЯНСК
@pb_O32 · 10,885
#27
Жесть | Брянск
@br_zhest · 17,661
#28
БЕЛАЯ БЕРЕЗКА ᅠ
@belayaberezka · 8,087
#29
Брянская губерния
@guberniyatv · 5,718
#30
Климово_32
@Klimovo_3232 · 5,664
#31
Минобороны России
@mod_russia · 650,928
#32
Новозыбков FOX
@Fox_News_Novozybkov · 22,688
#33
Брянская городская администрация
@admbryansk · 3,350
#34
Брянск.Ньюс
@brnews01 · 1,464
#35
Брянская улица
@bryanskucom · 430
#36
Типичный Брянск
@bryansk_zhest · 11,955
#37
Мой Брянск
@mybryansk32 · 3,166
#38
Брянск и Бежица
@bib_32 · 5,251
#39
Подслушано Сураж
@surazh_town · 6,507
#40
МЧС Брянской области
@mchs_bryansk · 19,013
#41
Брянский Водитель
@br_auto32 · 11,831
#42
Типичный город Брянск
@bryansk_typical · 2,327
#43
Mash
@mash · 3,096,804
#44
Прямой Эфир • Новости
@novosti_efir · 3,956,254
#45
SHOT
@shot_shot · 1,264,301
#46
LEO CARS 32 🇷🇺 - Bryansk
@leocars32 · 1,566
#47
Куда сходить в Брянске
@skhodit_v_bryanske · 4,129
#48
Оперштаб Курской области 🇷🇺
@gubernator_46 · 183,486
#49
ГАСТРОКАРТА БРЯНСКА
@gastro_b · 3,677
#50
СУДЖА РОДНАЯ 🇷🇺
@rodnaya_sudzha · 72,151
#51
ДЕВЯНОСТО ПЕРВЫЙ 🥑🍀
@place91 · 2,653
#52
Заповедник "Брянский лес"
@brles · 881
#53
ЦЕНЗУРА | БРЯНСК
@censoredhall · 2,474
#54
В Брянске - и точка
@VBryanskeiTochka · 1,921
#55
Теткино / Курск / Глушково / Коренево / Рыльск / Льгов /Суджа / Курчатов / Железногорск
@tetkino · 36,711
#56
Alisadivine
@alisadivine · 730 (as read 21 August 2026)
#57
Maya Larme @Larme
@maya_life_0 · 1,198
#58
Лицей Express
@lyceum_express · 1,764
#59
kalinichevvva
@kalinichevvvaa · 2,687
#60

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.

БРЯНСК | СОБЫТИЯ | НОВОСТИ
@Bryansk_nov · 22,436
Telegram ranks this channel #1 of 68 here — alongside 67 others — read 20 September 2026
Брянск | События | Подслушано
@Bryansk_podslushal · 36,252
Telegram ranks this channel #2 of 52 here — alongside 51 others — read 20 September 2026
НОВОСТИ БРЯНСКА
@bra_32 · 41,448
Telegram ranks this channel #6 of 47 here — alongside 46 others — read 29 August 2026
Настоящий Типичный Брянск
@tipical32 · 46,523
Telegram ranks this channel #6 of 62 here — alongside 61 others — read 27 August 2026
ТИПИЧНЫЙ БРЯНСК | НОВОСТИ
@tipicl32 · 158,747
Telegram ranks this channel #6 of 44 here — alongside 43 others — read 14 August 2026
БРЯ | Новости и события Брянска
@bryansk_media · 26,882
Telegram ranks this channel #7 of 66 here — alongside 65 others — read 11 September 2026
ПОДСЛУШАНО БРЯНСК
@pb_032 · 298,250
Telegram ranks this channel #7 of 40 here — alongside 39 others — read 14 August 2026
ЧП и ДТП Брянск
@bryansk_off32 · 59,737
Telegram ranks this channel #8 of 67 here — alongside 66 others — read 22 August 2026
Тревожный Брянск
@nabat32 · 28,334
Telegram ranks this channel #9 of 52 here — alongside 51 others — read 9 September 2026
Новости Брянска и Области
@bryansk_smi · 73,327
Telegram ranks this channel #9 of 43 here — alongside 42 others — read 19 August 2026
Город Брянск
@br_gorod · 93,486
Telegram ranks this channel #9 of 43 here — alongside 42 others — read 16 August 2026
Жесть Брянск
@zhestbryansk_32 · 30,801
Telegram ranks this channel #10 of 58 here — alongside 57 others — read 6 September 2026
Приграничье Брянск 🇷🇺
@prigrani4ie · 54,390
Telegram ranks this channel #11 of 29 here — alongside 28 others — read 22 August 2026
AV БогомаZ
@avbogomaz · 47,555
Telegram ranks this channel #15 of 89 here — alongside 88 others — read 26 August 2026
Подслушано Климово
@klimovo32 · 21,773
Telegram ranks this channel #16 of 40 here — alongside 39 others — read 22 September 2026
Брянск * Новости * Важное
@Bryansk_vajnoe · 25,730
Telegram ranks this channel #23 of 73 here — alongside 72 others — read 20 September 2026
Брянский навигатор
@navigator_32 · 23,977
Telegram ranks this channel #27 of 92 here — alongside 91 others — read 17 September 2026

This channel appears in 17 seed channels' Telegram-generated recommendation lists in total. 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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“Новости Брянска” (@barakholka32), 64,100 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/barakholka32.

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.