Telegram RegisterThe public register of Telegram
Telegram profile photo for Приграничье Брянск 🇷🇺

Channel

Приграничье Брянск 🇷🇺

@prigrani4ie

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

48,652subscribers

-10,117 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-1001761913600
TypeChannel
Username@prigrani4ie
Created14 May 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live14 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/prigrani4ie

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 20 August 2026 and assigned it the closest of 31 fixed categories, at 96% 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 8 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
@olegtsarov/461219 Aug 2026, 17:00 UTC@prigrani4ie/27396 · this entry10 Aug 2026, 04:00 UTC0.9911 hours
@olegtsarov/4617711 Aug 2026, 16:06 UTC@prigrani4ie/27433 · this entry12 Aug 2026, 04:03 UTC0.9912 hours
@olegtsarov/4634717 Aug 2026, 16:35 UTC@prigrani4ie/27519 · this entry18 Aug 2026, 04:02 UTC0.9911 hours
@olegtsarov/4668626 Aug 2026, 16:34 UTC@prigrani4ie/27588 · this entry27 Aug 2026, 04:01 UTC0.9911 hours
@olegtsarov/4629215 Aug 2026, 16:08 UTC@prigrani4ie/27504 · this entry16 Aug 2026, 04:02 UTC0.9912 hours
@olegtsarov/4647220 Aug 2026, 16:02 UTC@prigrani4ie/27544 · this entry21 Aug 2026, 04:00 UTC0.9912 hours
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
@olegtsarov27 (8/8 hand-verifiable sample passed)0.9912 hours@olegtsarov (27–0)
@barakholka3225 (8/8 hand-verifiable sample passed)1.0028 minutesthis entry (14–11)
@tipical3213 (8/8 hand-verifiable sample passed)0.9423 minutesthis entry (7–6)
@klintsyregion_3212 (8/8 hand-verifiable sample passed)0.9423 minutesthis entry (8–4)
@pb_0326 (6/6 hand-verifiable sample passed)0.9414 minutesthis entry (4–2)
@Fox_News_Novozybkov6 (6/6 hand-verifiable sample passed)1.0011 minuteseven
@granica0465 (5/5 hand-verifiable sample passed)0.9814 hoursthis entry (4–1)
@dnrdonetsk5 (5/5 hand-verifiable sample passed)0.9811 hours@dnrdonetsk (5–0)

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. 58 of the 58 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 331 comparable posts for this entry, running 5 August 2026 to 28 September 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 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

48,65258,93853,7956 August 202614 November 2026
65 measurements spanning 100 days, net -10,117. 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 47,109–60,481 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
14 Nov 2026, 18:2148,652-149
11 Nov 2026, 21:4648,801-83
10 Nov 2026, 03:4748,884-27
8 Nov 2026, 16:5148,911-84
7 Nov 2026, 13:4948,995-43
6 Nov 2026, 14:0549,038-6
5 Nov 2026, 17:2649,044-43
4 Nov 2026, 14:1549,087-53
3 Nov 2026, 10:3649,140-44
2 Nov 2026, 07:3849,184-29
1 Nov 2026, 06:3649,213-41
31 Oct 2026, 03:0049,254-51
30 Oct 2026, 00:1649,305-43
29 Oct 2026, 03:1949,348-53
28 Oct 2026, 03:5849,401-53
27 Oct 2026, 01:5549,454-53
26 Oct 2026, 04:0749,507-46
25 Oct 2026, 03:4649,553-29
24 Oct 2026, 02:5449,582-61
23 Oct 2026, 06:0149,643first reading

Engagement

500 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 111 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 500 posts for this entry, the most recent from 28 September 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4h 38m
Average length
2m 01s

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

7,293 reactions across 484 posts, in 13 distinct kinds. The most used accounts for 43.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏3,18243.6%
❤1,73123.7%
👍1,39419.1%
😡5918.10%
⚡3104.25%
🤬420.576%
custom 5199426892448439368130.178%
😢110.151%
😱80.11%
🤯50.069%
💯20.027%
🤔20.027%
🤨20.027%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.

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

Measured over the 500 most recent posts we hold, published 5 August 2026 to 28 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
3
across the posts below
Posts paid on
1
of 500 we hold a reading for · 0.2%
Most on one post
3
single highest reading

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

28 Sept 2026, 07:49 UTC≈2,730 views25 reactionsread 28 September 2026

‼️Егор Ковальчук: Враг наносит целенаправленные удары по железнодорожной инфраструктуре В результате атаки БпЛА на перегоне Дятьково-Людиново обрушилась часть моста, 10 вагонов сошли с железнодорожных путей. Пострадавших нет. В Унечском районе в результате атаки сошли с рельсов 18 пустых полувагонов. Никто не пострадал. После осмотра места происшествия сотрудниками Росгвардии начнутся восстановительные работы. Ещ…

🙏20❤3👍2

28 Sept 2026, 07:24 UTC≈2,540 views12 reactionsread 28 September 2026

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

🙏9❤3

27 Sept 2026, 13:36 UTC≈3,670 views12 reactionsread 28 September 2026

‼️Брянская область беспилотная опасность

🙏10⚡1👍1

27 Sept 2026, 11:10 UTC≈3,900 views10 reactionsread 28 September 2026

‼️Брянск и район внимание по реактивным БПЛА

🙏9❤1

27 Sept 2026, 08:42 UTC≈4,210 views16 reactionsread 28 September 2026

‼️Стародуб внимание! Со стороны Климовского направления идут ударные БПЛА

🙏14👍1💯1

27 Sept 2026, 08:25 UTC≈4,220 views11 reactionsread 28 September 2026

‼️Брянская область беспилотная опасность

🙏10⚡1

27 Sept 2026, 07:16 UTC≈4,360 views20 reactionsread 28 September 2026

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

🙏16❤3⚡1

26 Sept 2026, 14:03 UTC≈4,450 views19 reactionsread 28 September 2026

‼️Егор Ковальчук: Противник атаковал АЗС в посёлке Климово. Пострадал местный житель. Он находился на территории заправочной станции. Ещё один удар ВСУ нанесли по магазину в поселке Белая Березка Трубчевского района. Ранение получила местная жительница.

🙏11👍4🤬3❤1

26 Sept 2026, 14:01 UTC≈4,380 views16 reactionsread 28 September 2026

‼ Егор Ковальчук: Сегодня ночью враг совершил массированную атаку по инфраструктурным объектам и жилым домам в Брянской области. В Унечском районе повреждено железнодорожное полотно. Было приостановлено движение двух грузовых поездов Брянск-Унеча и Злынка-Брянск, отменен пригородный поезд сообщением Унеча-Почеп. Задержка в движении двух пассажирских поездов №85 Москва-Новозыбков и №489 Анапа-Минск. Поезд Москва-Нов…

❤6🙏6👍2💯1😢1

26 Sept 2026, 08:31 UTC≈4,110 views24 reactionsread 28 September 2026
Photo

🇷🇺Марьино наше! ➖️Штурмовые подразделения 80 омсбр группировки "Север" в результате ожесточенных боев выбили подразделения 47 омбр ВСУ из поселка Марьино Сумской области. ➖️Освобождение Марьино важный шаг в подготовке к осенней зачистке лесного массива южнее поселковой агломерации Иволжанское — Кияница — Мариьно. С выпадением осенней листвы боевикам ВСУ будет тяжело удержать позиции и устоять перед нашей авиацией, …

❤18🤬5🤔1

26 Sept 2026, 07:45 UTC≈4,130 views12 reactionsread 28 September 2026

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

🙏9❤2😢1

25 Sept 2026, 15:13 UTC≈4,770 views26 reactionsread 28 September 2026

‼️Егор Ковальчук: В Стародубе БпЛА атаковал гражданский грузовой автомобиль. Осколочные ранения получил водитель, он госпитализирован.

🙏19❤3😢2⚡1🤯1

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

@prigrani4ie 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
11 September 2026
Most recent edit
11 September 2026

Posts recorded as deleted after publishing

We recorded 3 posts on @prigrani4ie 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
10 August 2026
Most recent seen missing
15 September 2026
Median time before seen missing
13 hours
Seen missing in the last 30 days
0

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

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 · 297,765
#1
Город Брянск
@br_gorod · 92,794
#2
ТИПИЧНЫЙ БРЯНСК | НОВОСТИ
@tipicl32 · 158,866
#3
grohot_pgr
@grohot_pgr · 28
#4
Подслушано Климово
@klimovo32 · 21,668
#5
Новозыбков FOX
@Fox_News_Novozybkov · 23,151
#6
НОВОСТИ БРЯНСКА
@bra_32 · 41,023
#7
AV БогомаZ
@avbogomaz · 46,135
#8
ЧП и ДТП Брянск
@bryansk_off32 · 59,247
#9
Климово_32
@Klimovo_3232 · 5,578
#10
Новости Брянска
@barakholka32 · 63,701
#11
Настоящий Типичный Брянск
@tipical32 · 46,408
#12
Подслушано Клинцы (region_32)
@klintsyregion_32 · 52,656
#13
Жесть Брянск
@zhestbryansk_32 · 30,809
#14
Операция Z: Военкоры Русской Весны
@rvvoenkor · 1,451,025
#15
Белорусский силовик
@belarusian_silovik · 449,733
#16
Жесть приграничья 🇷🇺
@zgest_granica · 7,190
#17
Мой Брянск
@mybryansk32 · 3,139
#18
Типичные Клинцы
@tipical_klintsy · 8,937
#19
ГориZонт Брянск 🇷🇺
@GoriZont_bryansk · 11,017
#20
Тревожный Брянск
@nabat32 · 28,193
#21
Жесть | Брянск
@br_zhest · 17,443
#22
ZАПИСКИ VЕТЕРАНА 🇷🇺
@notes_veterans · 273,485
#23
БЕЛАЯ БЕРЕЗКА ᅠ
@belayaberezka · 7,763
#24
Старший Пограннаряда 🇷🇺
@starshii_pogrannaryada · 34,583
#25
Readovka
@readovkanews · 2,011,824
#26
Тринадцатый.
@Z13_Separ · 208,366
#27
Young Pa4kkkka
@botva777 · 457 (as read 22 August 2026)
#28
ПОГРАНИЧНИК ИЗ АДА
@pograni4nik_iz_ada · 103,908
#29

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

Подслушано Климово
@klimovo32 · 21,668
Telegram ranks this channel #3 of 40 here — alongside 39 others — read 22 September 2026
AV БогомаZ
@avbogomaz · 46,135
Telegram ranks this channel #3 of 89 here — alongside 88 others — read 26 August 2026
Город Брянск
@br_gorod · 92,794
Telegram ranks this channel #3 of 43 here — alongside 42 others — read 16 August 2026
Тревожный Брянск
@nabat32 · 28,193
Telegram ranks this channel #6 of 52 here — alongside 51 others — read 9 September 2026
ПОДСЛУШАНО БРЯНСК
@pb_032 · 297,765
Telegram ranks this channel #6 of 40 here — alongside 39 others — read 14 August 2026
Жесть Брянск
@zhestbryansk_32 · 30,809
Telegram ranks this channel #7 of 58 here — alongside 57 others — read 6 September 2026
НОВОСТИ БРЯНСКА
@bra_32 · 41,023
Telegram ranks this channel #7 of 47 here — alongside 46 others — read 29 August 2026
Подслушано Клинцы (region_32)
@klintsyregion_32 · 52,656
Telegram ranks this channel #7 of 15 here — alongside 14 others — read 24 August 2026
ЧП и ДТП Брянск
@bryansk_off32 · 59,247
Telegram ranks this channel #7 of 67 here — alongside 66 others — read 22 August 2026
Новости Брянска
@barakholka32 · 63,701
Telegram ranks this channel #7 of 60 here — alongside 59 others — read 21 August 2026
Новости Брянска и Области
@bryansk_smi · 73,042
Telegram ranks this channel #7 of 43 here — alongside 42 others — read 19 August 2026
ТИПИЧНЫЙ БРЯНСК | НОВОСТИ
@tipicl32 · 158,866
Telegram ranks this channel #7 of 44 here — alongside 43 others — read 14 August 2026
Настоящий Типичный Брянск
@tipical32 · 46,408
Telegram ranks this channel #10 of 62 here — alongside 61 others — read 27 August 2026
Брянский навигатор
@navigator_32 · 23,863
Telegram ranks this channel #22 of 92 here — alongside 91 others — read 17 September 2026
Курск | События | Подслушано
@Kursk_podslushal · 36,187
Telegram ranks this channel #30 of 77 here — alongside 76 others — read 29 September 2026
Белгород | События | Новости
@Belgorod_narod · 20,064
Telegram ranks this channel #48 of 68 here — alongside 67 others — read 29 September 2026
МЧС Брянской области
@mchs_bryansk · 18,617
Telegram ranks this channel #56 of 89 here — alongside 88 others — read 5 October 2026
grohot_pgr
@grohot_pgr · 28
Telegram ranks this channel #56 of 77 here — alongside 76 others — read 14 August 2026

This channel appears in 18 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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“Приграничье Брянск 🇷🇺” (@prigrani4ie), 48,652 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/prigrani4ie.

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.