Telegram RegisterThe public register of Telegram
Telegram profile photo for ЧС Приграни́чье

Channel

ЧС Приграни́чье

@rschs_prigranichie

Not marked by Telegram, checked 10 August 2026

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

27,839subscribers

-533 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002091347864
TypeChannel
Username@rschs_prigranichie
DescriptionГлавные новости приграничья. Оповещаем народ и пишем обычные новости из зоны боевых действий. Купить рекламу 👉 @ktoktoktoktooo
Created17 December 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live18 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/rschs_prigranichie

Topic

National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 6 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
@atypicalday/13260623 Oct 2026, 06:16 UTC@rschs_prigranichie/32093 · this entry23 Oct 2026, 06:20 UTC0.974 minutes
@atypicalday/13481315 Nov 2026, 09:49 UTC@rschs_prigranichie/34124 · this entry15 Nov 2026, 09:50 UTC0.95under a minute
@atypicalday/13454911 Nov 2026, 07:51 UTC@rschs_prigranichie/33869 · this entry11 Nov 2026, 07:52 UTC0.9472 seconds
@atypicalday/12963723 Sept 2026, 12:52 UTC@rschs_prigranichie/29334 · this entry23 Sept 2026, 12:55 UTC0.942 minutes
@atypicalday/13252621 Oct 2026, 23:04 UTC@rschs_prigranichie/32014 · this entry21 Oct 2026, 23:05 UTC0.9172 seconds
@atypicalday/12987726 Sept 2026, 09:15 UTC@rschs_prigranichie/29553 · this entry26 Sept 2026, 09:15 UTC0.88under 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
@atypicalday27 (8/8 hand-verifiable sample passed)0.9172 seconds@atypicalday (27–0)
@gromkokursk20 (8/8 hand-verifiable sample passed)0.9172 seconds@gromkokursk (20–0)
@incidentkursk17 (8/8 hand-verifiable sample passed)0.9372 seconds@incidentkursk (17–0)
@trevoga_prigran_bpla11 (8/8 hand-verifiable sample passed)0.95under a minute@trevoga_prigran_bpla (11–0)
@Rschs_prigranichie18 (8/8 hand-verifiable sample passed)0.94under a minutethis entry (5–3)
@rschsprigranichie_ro6 (6/6 hand-verifiable sample passed)0.94under a minute@rschsprigranichie_ro (6–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. 84 of the 84 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 800 comparable posts for this entry, running 7 August 2026 to 19 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 20 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

27,83928,41228,125.57 August 202618 November 2026
65 measurements spanning 103 days, net -533. 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 27,753–28,498 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
18 Nov 2026, 07:3927,839-15
15 Nov 2026, 03:0827,854-27
12 Nov 2026, 01:1927,881-9
10 Nov 2026, 04:0627,890-2
8 Nov 2026, 16:5627,892-15
7 Nov 2026, 06:5627,907-6
6 Nov 2026, 03:3727,913-6
5 Nov 2026, 00:3927,919-3
3 Nov 2026, 02:5627,922+3
2 Nov 2026, 02:3727,919-3
1 Nov 2026, 00:1727,922-3
31 Oct 2026, 01:5027,925-8
30 Oct 2026, 00:1727,933-9
28 Oct 2026, 21:0727,942-1
27 Oct 2026, 21:1027,943-10
26 Oct 2026, 22:3627,953-4
25 Oct 2026, 21:2527,957-2
24 Oct 2026, 19:2727,959-7
23 Oct 2026, 22:1627,966-3
22 Oct 2026, 21:0927,969first reading

Engagement

3,000 posts held, back to 6 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 172 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.07%
avg views ÷ 27,839 subscribers
Avg views / post
298
959 posts measured
Reaction rate
0.315%
reactions ÷ views · ER floor
Posts in window
959
of 3,000 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 193 of 959 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 20 November 2026
Posts held3,000 (6 August 2026 – 20 November 2026)
Views total285,666
Reactions total212
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Nov 2026, 15:05 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,200
Videos
≈4,220
Links
≈19,300

Lifetime counters from Telegram’s own channel header, read 20 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
1m 38s
Average length
14s

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

229 reactions across 186 posts, in 18 distinct kinds. The most used accounts for 42.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏9842.8%
🤬4117.9%
❤2812.2%
😢2410.5%
🔥73.06%
💩52.18%
🖕52.18%
😁52.18%
👎31.31%
👍20.873%
🕊20.873%
😱20.873%
🤮20.873%
🍾10.437%
👏10.437%
🤗10.437%
🤡10.437%
🤩10.437%

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 207 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 229 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 20 October 2026 to 20 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.

Recent posts

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

20 Nov 2026, 13:38 UTC135 viewsread 20 November 2026

Севастополь Воздушная тревога ЧС Приграни́чье | Подписаться

20 Nov 2026, 13:18 UTC257 views4 reactionsread 20 November 2026

Путин по ошибке запустил беспилотники и ракеты по Польше — Трамп. ЧС Приграни́чье | Подписаться

😁3🤮1

20 Nov 2026, 08:34 UTC404 viewsread 20 November 2026

УГРОЗА ПОВТОРНОЙ АТАКИ БПЛА в Белгородском МО 11:32. Оставайтесь дома, не подходите к окнам или пройдите в укрытие. ЧС Приграни́чье | Подписаться

20 Nov 2026, 08:12 UTC431 viewsread 20 November 2026

Курск Опасность по БПЛА Курская область ЧС Приграни́чье | Подписаться

20 Nov 2026, 07:32 UTC480 views3 reactionsread 20 November 2026

За минувшие сутки боевики киевского режима ВСУ 77 раз атаковали территорию Белгородской области Нанесены удары по Белгороду, Белгородскому, Борисовскому, Валуйскому, Волоконовскому, Грайворонскому, Корочанскому, Краснояружскому, Прохоровскому, Ракитянскому и Шебекинскому округам. Противник произвёл 10 обстрелов с использованием артиллерии. Кроме того, 4 раза сбрасывал взрывные устройства с БПЛА. Благодаря професси…

🙏2🤬1

19 Nov 2026, 22:46 UTC594 views1 reactionsread 20 November 2026

Новороссийск меры предосторожности ЧС Приграни́чье | Подписаться

🙏1

19 Nov 2026, 21:44 UTC666 views1 reactionsread 20 November 2026

Старый Оскол про звуки знаем, тревог не получали. ЧС Приграни́чье | Подписаться

🙏1

19 Nov 2026, 21:06 UTC726 views1 reactionsread 20 November 2026

Железногорск Фатеж Тревога по БПЛА Курская область ЧС Приграни́чье | Подписаться

🙏1

19 Nov 2026, 21:06 UTC698 views1 reactionsread 20 November 2026

Курск Опасность по БПЛА Повторно ЧС Приграни́чье | Подписаться

🙏1

19 Nov 2026, 20:34 UTC696 views1 reactionsread 20 November 2026

Рыльск и Рыльский район Ограничить передвижение! ЧС Приграни́чье | Подписаться

🙏1

19 Nov 2026, 20:30 UTC671 views1 reactionsread 20 November 2026

Экстренная информация РСЧС: БЕСПИЛОТНАЯ ОПАСНОСТЬ на территории муниципальных образований: Приморско-Ахтарский муниципальный округ, Брюховецкий, Ейский, Каневской, Щербиновский, Абинский, Калининский, Красноармейский, Крымский, Северский, Славянский, Темрюкский, Тимашевский районы. 19.11.2026 ЧС Приграни́чье | Подписаться

🙏1

19 Nov 2026, 20:08 UTC607 views1 reactionsread 20 November 2026

Краснодарский край ракетная опасность ЧС Приграни́чье | Подписаться

🙏1

Showing the 12 most recent of 3,000 posts we hold for @rschs_prigranichie. 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.

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.

РСЧС Приграни́чье
@Rschs_prigranichie1 · 34,060
#1
Тревожный Старый Оскол
@sta_oskol · 83,952
#2
Жесть Белгород
@zhest_belgorod · 587,346
#3
Настоящий Гладков
@vvgladkov · 393,482
#4
ОК! Старый Оскол
@okoskol · 69,717
#5
Тревожный Курск | Суджа
@tre_kyrsk · 32,207
#6
Типичный Курск
@tipich_kursk · 150,229
#7
Оперштаб Курской области 🇷🇺
@gubernator_46 · 182,610
#8
Радар Белгород
@radarb31 · 137,077
#9
ЧП Оскол
@chp_st_oskol · 28,514
#10
Белгород С-400🚀🇷🇺
@belgorodc400 · 48,963
#11
Приграничный Радар
@prigranichie_radar1 · 32,061
#12
Белгород №1
@belgorod01 · 189,045
#13
Громко, курское приграничье!
@gromkokursk · 36,819
#14
Жесть Курск
@zhest_kursk_146 · 91,861
#15
Инцидент Белгород
@incbgd · 9,330
#16
ПОГРАНИЧНИК ИЗ АДА
@pograni4nik_iz_ada · 103,778
#17
Тревожный Губкин
@gubkih · 17,957
#18
ВОРОНЕЖСКОЕ НЕБО
@nebovrn36 · 153,737
#19
🇷🇺 Актуальный Курск
@kursk_ak46 · 41,554
#20
ЧП Белгород
@chp_bel · 62,963
#21
Курское приграничье 2.0
@granica046 · 41,334
#22
🚨Белгород | Live
@belgorod_live1 · 13,517
#23
🇷🇺ОперСводки 31🇷🇺
@opersvodki_belgorod · 18,533
#24
Блэтгород
@bletgorod · 106,189
#25
Взрывы Белгород🇷🇺
@vzrivi_belgorod1 · 34,128
#26
СУДЖА РОДНАЯ 🇷🇺
@rodnaya_sudzha · 71,039
#27
9 Канал | Старый Оскол
@StaryOskol_9kanal · 8,970
#28
Сводки и Аналитика СВО (Резерв)
@rezervsvo · 203,231
#29
БелПлюс
@belplus_bg · 70,200
#30
БЕЛГОРОДЕЦ
@belgorodecRU · 91,707
#31
Приграничье
@atypicalday · 63,296
#32
war_territory
@war_territory · 1
#33
Курская область
@kurskadm · 78,345
#34
Белгородский Андеграунд
@undeground_belgorod_31 · 33,706
#35
СТОГ Старый Оскол
@stog_oskol · 17,248
#36
Гусев
@gusev_36 · 130,502
#37
Жесть Шебекино
@zhest_shebekino_channel · 60,642
#38
ZАПИСКИ VЕТЕРАНА 🇷🇺
@notes_veterans · 273,406
#39
СВО 2024
@zalpom31_2 · 67,599
#40
Белгородчина31🇷🇺
@belgorodchina31 · 6,722
#41
Авто Белгород
@avto_belgorod31 · 25,581
#42
Белгородская область оповещения, тревоги
@lpr1_Belgorod_alarm · 56,829
#43
Правдивый Белгород
@pravda_belgorod · 7,405
#44
ОК! Губкин
@okgubkin · 16,069
#45
Zона приграничья🇷🇺
@glaZ_graniZa · 20,556
#46
Мониторинг Белгород | 31 Регион
@rschs31 · 16,443
#47
Чё в Белгороде?
@belgorod_granica · 198,892
#48
Регион-36 (Воронеж с огоньком)
@voronezh_r36 · 73,201
#49
Белгород — Молния
@bbbelgorod · 48,732
#50
Управление Z 🇷🇺
@control_sigma · 31,349
#51
Казачья Лопань Z
@kozacha23 · 39,483
#52
🚀Приграничный Наблюдатель🇷🇺
@ZOV_granicy · 10,859
#53
Белгород Правда
@belpravda31 · 15,636
#54
Приграничный Доzор
@prigran_dozor · 11,268
#55
ЧП Курск
@kursk46chp · 28,507
#56
Валуйки Телега
@tgvaluyki · 30,470
#57
31 Онлайн
@bel31online · 46,152 (as read 9 September 2026)
#58
Тревожное Горшечное
@ggorshechnoe · 3,555
#59
Тринадцатый.
@Z13_Separ · 208,065
#60
Тревожный Воронеж
@tre_voronezh · 51,739
#61
Прямой Эфир • Новости
@novosti_efir · 3,863,185
#62
Т-Воронеж | Типичный | Новости Воронежа
@typicalvoronezh · 372,611
#63
Мой и твой Воронеж
@mtv36 · 190,000
#64
Oskol Stelit | Старый Оскол
@oskol_stelit_31 · 28,702
#65
Жесть Воронеж
@zhest_voronezh_136 · 61,840
#66
Официальный Старый Оскол
@oskol_official · 15,794
#67
Воронеж №1
@vrn01 · 72,749
#68
Воронеж VRN ️
@vrn36v · 70,006
#69
Большой воронежский
@voronezh_news_36 · 83,437
#70
СКИМ
@skimst · 1,300
#71
vorzhest
@vrinc · 432
#72
в Старом Осколе любят
@ctary_oskol · 2,518
#73

Read from Telegram’s recommendation API, most recently 9 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

РСЧС Приграни́чье
@Rschs_prigranichie1 · 34,060
Telegram ranks this channel #5 of 74 here — alongside 73 others — read 3 September 2026
Тревожный Старый Оскол
@sta_oskol · 83,952
Telegram ranks this channel #6 of 28 here — alongside 27 others — read 18 August 2026
ЧП Оскол
@chp_st_oskol · 28,514
Telegram ranks this channel #7 of 32 here — alongside 31 others — read 9 September 2026
ОК! Старый Оскол
@okoskol · 69,717
Telegram ranks this channel #8 of 37 here — alongside 36 others — read 20 August 2026
Тревожный Курск | Суджа
@tre_kyrsk · 32,207
Telegram ranks this channel #12 of 69 here — alongside 68 others — read 5 September 2026
Приграничье
@atypicalday · 63,296
Telegram ranks this channel #14 of 64 here — alongside 63 others — read 21 August 2026
Регион 31 Белгород
@r31belgorod · 31,192
Telegram ranks this channel #19 of 81 here — alongside 80 others — read 10 September 2026
Oskol Stelit | Старый Оскол
@oskol_stelit_31 · 28,702
Telegram ranks this channel #20 of 30 here — alongside 29 others — read 9 September 2026
Чё в Белгороде?
@belgorod_granica · 198,892
Telegram ranks this channel #22 of 70 here — alongside 69 others — read 14 August 2026
Валуйки Телега
@tgvaluyki · 30,470
Telegram ranks this channel #24 of 52 here — alongside 51 others — read 6 September 2026
ВОРОНЕЖСКОЕ НЕБО
@nebovrn36 · 153,737
Telegram ranks this channel #25 of 39 here — alongside 38 others — read 13 August 2026
ВОЙНА НА УКРАИНЕ СВО УКРАИНА
@novostydhd · 53,853
Telegram ranks this channel #27 of 57 here — alongside 56 others — read 23 August 2026
ЧП Белгород
@chp_bel · 62,963
Telegram ranks this channel #28 of 85 here — alongside 84 others — read 21 August 2026
Небо приграничья
@neboprigran · 19,480
Telegram ranks this channel #29 of 54 here — alongside 53 others — read 30 September 2026
Громко, курское приграничье!
@gromkokursk · 36,819
Telegram ranks this channel #30 of 63 here — alongside 62 others — read 1 September 2026
🇷🇺 Актуальный Курск
@kursk_ak46 · 41,554
Telegram ranks this channel #30 of 73 here — alongside 72 others — read 29 August 2026
Гусев
@gusev_36 · 130,502
Telegram ranks this channel #30 of 83 here — alongside 82 others — read 13 August 2026
ЧП Курск
@kursk46chp · 28,507
Telegram ranks this channel #31 of 57 here — alongside 56 others — read 9 September 2026
grohot_pgr
@grohot_pgr · 28
Telegram ranks this channel #31 of 77 here — alongside 76 others — read 14 August 2026
Белгород С-400🚀🇷🇺
@belgorodc400 · 48,963
Telegram ranks this channel #34 of 83 here — alongside 82 others — read 25 August 2026
Тревожный Воронеж
@tre_voronezh · 51,739
Telegram ranks this channel #36 of 48 here — alongside 47 others — read 25 August 2026
Регион-36 (Воронеж с огоньком)
@voronezh_r36 · 73,201
Telegram ranks this channel #36 of 80 here — alongside 79 others — read 19 August 2026
Приграничный Радар
@prigranichie_radar1 · 32,061
Telegram ranks this channel #39 of 68 here — alongside 67 others — read 5 September 2026
Инцидент Курск
@incident46 · 21,979
Telegram ranks this channel #40 of 58 here — alongside 57 others — read 21 September 2026

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

“ЧС Приграни́чье” (@rschs_prigranichie), 27,839 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/rschs_prigranichie.

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.