Telegram RegisterThe public register of Telegram
Telegram profile photo for Оперштаб Курской области 🇷🇺

Channel

Оперштаб Курской области 🇷🇺

@gubernator_46

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry

182,796subscribers

-1,368 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001762307105
TypeChannel
Username@gubernator_46
DescriptionОфициальный информационный ресурс Оперативного штаба Курской области в Telegram 📝 Регистрация в РКН: https://clck.ru/3FTanv
Created21 October 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live1 November 2026
Measurements held58
Confirmed unchanged1 time, most recently 1 November 2026
On Telegramt.me/gubernator_46

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 8 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 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 word for word on 1 other registered channel. 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 (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@gubernator_46/19040 · this entry5 Aug 2026, 12:42 UTC@kurskadm/1088235 Aug 2026, 12:44 UTC1.002 minutes
@gubernator_46/19044 · this entry5 Aug 2026, 21:00 UTC@kurskadm/1088325 Aug 2026, 21:03 UTC1.004 minutes
@gubernator_46/19062 · this entry7 Aug 2026, 14:03 UTC@kurskadm/1089187 Aug 2026, 14:04 UTC1.0072 seconds
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@kurskadm5 (5/5 hand-verifiable sample passed)1.002 minutesthis entry (3–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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 29 comparable posts for this entry, running 4 August 2026 to 8 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 2, the earliest publisher we hold is @gubernator_46 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 8 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 1 other registered channel, 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

182,796184,164183,4805 August 2026 — 184,164 subscribers6 August 2026 — 184,164 subscribers6 August 2026 — 184,159 subscribers7 August 2026 — 184,122 subscribers8 August 2026 — 184,142 subscribers9 August 2026 — 184,116 subscribers10 August 2026 — 184,081 subscribers11 August 2026 — 184,047 subscribers12 August 2026 — 183,987 subscribers13 August 2026 — 183,936 subscribers15 August 2026 — 183,910 subscribers16 August 2026 — 183,878 subscribers17 August 2026 — 183,853 subscribers18 August 2026 — 183,814 subscribers19 August 2026 — 183,781 subscribers20 August 2026 — 183,752 subscribers22 August 2026 — 183,730 subscribers23 August 2026 — 183,682 subscribers25 August 2026 — 183,636 subscribers26 August 2026 — 183,607 subscribers27 August 2026 — 183,579 subscribers28 August 2026 — 183,546 subscribers29 August 2026 — 183,519 subscribers30 August 2026 — 183,487 subscribers31 August 2026 — 183,467 subscribers1 September 2026 — 183,434 subscribers2 September 2026 — 183,399 subscribers3 September 2026 — 183,379 subscribers4 September 2026 — 183,562 subscribers8 September 2026 — 183,476 subscribers11 September 2026 — 183,628 subscribers13 September 2026 — 183,564 subscribers14 September 2026 — 183,544 subscribers16 September 2026 — 183,538 subscribers18 September 2026 — 183,486 subscribers24 September 2026 — 183,431 subscribers3 October 2026 — 183,333 subscribers8 October 2026 — 183,237 subscribers12 October 2026 — 183,274 subscribers14 October 2026 — 183,213 subscribers15 October 2026 — 183,187 subscribers16 October 2026 — 183,144 subscribers17 October 2026 — 183,126 subscribers18 October 2026 — 183,095 subscribers19 October 2026 — 183,082 subscribers20 October 2026 — 183,074 subscribers21 October 2026 — 183,022 subscribers22 October 2026 — 183,031 subscribers23 October 2026 — 183,006 subscribers24 October 2026 — 182,984 subscribers25 October 2026 — 182,947 subscribers26 October 2026 — 182,971 subscribers27 October 2026 — 182,953 subscribers28 October 2026 — 182,923 subscribers29 October 2026 — 182,903 subscribers30 October 2026 — 182,885 subscribers31 October 2026 — 182,841 subscribers1 November 2026 — 182,796 subscribers5 August 20261 November 2026
58 measurements spanning 88 days, net -1,368. 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 182,591–184,369 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 58
Measured (UTC)SubscribersChange
1 Nov 2026, 17:48182,796-45
31 Oct 2026, 20:10182,841-44
30 Oct 2026, 18:17182,885-18
29 Oct 2026, 14:39182,903-20
28 Oct 2026, 14:55182,923-30
27 Oct 2026, 14:46182,953-18
26 Oct 2026, 16:04182,971+24
25 Oct 2026, 15:06182,947-37
24 Oct 2026, 18:27182,984-22
23 Oct 2026, 19:37183,006-25
22 Oct 2026, 22:56183,031+9
21 Oct 2026, 19:47183,022-52
20 Oct 2026, 13:30183,074-8
19 Oct 2026, 11:21183,082-13
18 Oct 2026, 09:06183,095-31
17 Oct 2026, 08:10183,126-18
16 Oct 2026, 11:00183,144-43
15 Oct 2026, 09:56183,187-26
14 Oct 2026, 08:10183,213-61
12 Oct 2026, 18:20183,274first reading

Engagement

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

ERR · 30 days
6.59%
avg views ÷ 182,796 subscribers
Avg views / post
12,100
252 posts measured
Reaction rate
0.334%
reactions ÷ views · ER floor
Posts in window
252
of 639 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 250 of 252 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 2 November 2026
Posts held639 (4 August 2026 – 2 November 2026)
Views total3,037,240
Reactions total10,138
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Nov 2026, 03:29 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
≈9,610
Videos
≈490
Links
≈2,420

Lifetime counters from Telegram’s own channel header, read 2 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
12m 50s
Average length
1m 50s

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

32,315 reactions across 622 posts, in 18 distinct kinds. The most used accounts for 76.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏24,66076.3%
🤬1,7625.45%
❤1,5944.93%
😢1,2833.97%
🎉7562.34%
🔥6431.99%
🕊5521.71%
👏3451.07%
🤗2230.69%
😱1890.585%
💔1290.399%
👌450.139%
🤔420.13%
🥰350.108%
🫡260.08%
🤝190.059%
🏆100.031%
💯20.006%

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

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

2 Nov 2026, 02:41 UTC593 viewsread 2 November 2026

✅ Курская область: внимание! Отбой опасности атаки БПЛА.

2 Nov 2026, 02:40 UTC597 viewsread 2 November 2026

✅ Курская область: внимание! Отбой авиационной опасности.

1 Nov 2026, 15:03 UTC≈5,260 views39 reactionsread 2 November 2026

⚡️ Курская область: авиационная опасность. Будьте бдительны! Силы и средства приведены в готовность для отражения возможной атаки.

🙏39

1 Nov 2026, 14:07 UTC≈5,810 views27 reactionsread 2 November 2026

✅ Курская область: внимание! Отбой авиационной опасности.

🙏27

1 Nov 2026, 07:12 UTC≈7,420 views38 reactionsread 2 November 2026

⚡️ Курская область: авиационная опасность. Будьте бдительны! Силы и средства приведены в готовность для отражения возможной атаки.

🙏38

1 Nov 2026, 06:16 UTC≈7,820 views25 reactionsread 2 November 2026
Photo

⚡️ Александр Хинштейн опубликовал сводку об оперативной обстановке в Курской области за прошедшие сутки: «Всего в период с 09:00 31 октября до 09:00 1 ноября сбито 73 вражеских беспилотника различного типа. 34 раза враг применил артиллерию по отселённым районам. 4 раза беспилотники атаковали нашу территорию с помощью взрывных устройств. В результате атак в деревне Никипеловка Кореневского района уничтожен дом. В д…

🙏25

1 Nov 2026, 05:02 UTC≈7,370 views26 reactionsread 2 November 2026

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

🙏26

1 Nov 2026, 04:18 UTC≈7,370 views22 reactionsread 2 November 2026

✅ Курская область: внимание! Отбой опасности атаки БПЛА.

🙏22

31 Oct 2026, 16:28 UTC≈39,700 views44 reactionsread 2 November 2026

✅ Курская область: внимание! Отбой авиационной опасности.

🙏44

31 Oct 2026, 10:41 UTC≈9,640 views48 reactionsread 2 November 2026

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

🙏48

31 Oct 2026, 08:22 UTC≈9,370 views38 reactionsread 2 November 2026

⚡️ Курская область: авиационная опасность. Будьте бдительны! Силы и средства приведены в готовность для отражения возможной атаки.

🙏38

31 Oct 2026, 06:22 UTC≈9,670 views35 reactionsread 2 November 2026
Photo

❗️ Александр Хинштейн опубликовал сводку об оперативной обстановке в Курской области за прошедшие сутки: «Всего в период с 09:00 30 октября до 09:00 31 октября сбито 143 вражеских беспилотника различного типа. 27 раз враг применил артиллерию по отселённым районам. 12 раз беспилотники атаковали нашу территорию с помощью взрывных устройств. Пострадали два человека: 64-летний мужчина в селе Черницыно Октябрьского райо…

🙏35

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

@gubernator_46 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
14 August 2026
Most recent edit
30 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 33 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

КУРСКИЙ БОМОНДЪ
@kurskbomond · 225,010
#1
Типичный Курск
@tipich_kursk · 150,578
#2
Курская область
@kurskadm · 78,706
#3
ТЕРРИТОРИЯ ВОЙНЫ
@war_territory · 23,726
#4
Курск №1
@kursk_russia · 44,068
#5
grohot_pgr
@grohot_pgr · 30
#6
Жесть Курск
@zhest_kursk_146 · 91,406
#7
Громко, курское приграничье!
@gromkokursk · 36,988
#8
СУДЖА РОДНАЯ 🇷🇺
@rodnaya_sudzha · 71,325
#9
Настоящий Гладков
@vvgladkov · 400,295
#10
Курское приграничье 2.0
@granica046 · 41,487
#11
🇷🇺 Актуальный Курск
@kursk_ak46 · 41,664
#12
Минобороны России
@mod_russia · 651,087
#13
Регион 46 Курск
@r46kursk · 50,117
#14
Тревожный Курск | Суджа
@tre_kyrsk · 32,330
#15
Приграничный Радар
@prigranichie_radar1 · 32,202
#16
Жесть Белгород
@zhest_belgorod · 589,426
#17
РСЧС Приграни́чье
@Rschs_prigranichie1 · 34,165
#18
Нетипичный Курск
@typical_kursk · 19,139
#19
ТАСС
@tass_agency · 569,342
#20
Секундочку
@sekundamedia · 9,813
#21
Управление Z 🇷🇺
@control_sigma · 31,471
#22
Сейм: новости Курской области🇷🇺
@seymkursk · 16,169
#23
ЧП Курск
@kursk46chp · 28,577
#24
Город Курск
@kurskpressa · 6,661
#25
Суджа в Telegram
@sudzha_tme · 28,794
#26
Наш Железногорск
@Nash_Zheleznogorsk · 14,491
#27
Теткино / Курск / Глушково / Коренево / Рыльск / Льгов /Суджа / Курчатов / Железногорск
@tetkino · 36,395
#28
Курская аномалия
@KurskAnomalia · 8,524
#29
МИГ России
@mig41 · 478,139
#30
Курск на связи ©
@kursk_nasv · 41,334
#31
Курская Telega
@KurskayaTelega · 10,567
#32
Апти Алаудинов «АХМАТ»
@AptiAlaudinovAKHMAT · 200,200
#33
МЧС Курской области
@mchs_46 · 11,040
#34
Приграничный Доzор
@prigran_dozor · 11,323
#35
КУРСКСИТИ|Новости города и области
@kurskcityru · 7,459
#36
Подслушано Курчатов
@podslushano_kurchatov1 · 23,519
#37
Вести Курск
@vesti_kursk · 11,171
#38
Новости Курска и Области
@kursk_smi · 60,024
#39
Железногорск
@zhelek46rus · 5,905
#40
Твой Курский край | Новости Курского приграничья
@kursk_info46 · 39,557
#41
WarGonzo
@wargonzo · 739,544
#42
Курские известия|Новости Курска
@kursk_time · 7,285
#43
МЧС России
@mchs_official · 77,833
#44
🚨ЧП КУРСК | ПРИГРАНИЧЬЕ
@kursk_chp46 · 9,310
#45
Инцидент Курск
@incident46 · 22,058
#46
🚨 ЧП, Курское приграничье
@incidentkursk · 37,556
#47
Типичный Рыльск
@typical_rilsk46 · 31,645
#48
Белгород №1
@belgorod01 · 189,869
#49
Курские новости
@kursk_novost · 17,280
#50
Глушковский Бомондъ/ Курское приграничье
@BomondGlushkovsk · 13,944
#51
ПАТРИОТ КУРСК
@patriot046 · 4,592
#52
Мир сегодня с "Юрий Подоляка"
@yurasumy · 2,668,319
#53
Readovka
@readovkanews · 2,001,042
#54
Прямой Эфир • Новости
@novosti_efir · 3,898,432
#55
Раньше всех. Ну почти.
@bbbreaking · 1,976,562
#56
Baza
@bazabazon · 1,559,012
#57
SHOT
@shot_shot · 1,267,854
#58
Роман Старовойт
@roman_starovoyt · 4,848
#59
АВТОКАДР_46
@Avtokadr46 · 55,789
#60
ЕЖ
@ejdailyru · 667,143
#61
Роман Алехин
@Alekhin_Telega · 116,369
#62
Kotsnews
@sashakots · 470,005
#63
СОЛОВЬЁВ
@solovievlive · 1,115,688
#64
Поддубный |Z|О|V| edition
@epoddubny · 569,302
#65
NewStream * Курск - мы вместе!
@news_strm · 4,537
#66
Кремль. Новости
@news_kremlin · 280,446
#67
Военкор Котенок
@voenkorKotenok · 309,497
#68
ZАПИСКИ VЕТЕРАНА 🇷🇺
@notes_veterans · 274,397
#69
Ловец Человеков | Елена Залесская
@iamhumancatcher · 119,724
#70
город Железногорск
@zheleznogorsk_gorod46 · 4,543
#71
ПОГРАНИЧНИК ИЗ АДА
@pograni4nik_iz_ada · 104,137
#72
Край | Курск | Курская область
@kraypress · 1,778
#73
Коммерсантъ
@kommersant · 294,905
#74
Плохая куряночка
@plohayaQ · 7,000
#75
Mash
@mash · 3,145,932
#76
Проспект Дериглазова|Курск
@DeriglazovaProspekt · 13,281
#77
Пул N3
@dimsmirnov175 · 331,121
#78

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

Нетипичный Курск
@typical_kursk · 19,139
Telegram ranks this channel #1 of 19 here — alongside 18 others — read 3 October 2026
Инцидент Курск
@incident46 · 22,058
Telegram ranks this channel #1 of 58 here — alongside 57 others — read 21 September 2026
ТЕРРИТОРИЯ ВОЙНЫ
@war_territory · 23,726
Telegram ranks this channel #1 of 55 here — alongside 54 others — read 16 September 2026
Подслушано Курчатов
@podslushano_kurchatov1 · 23,519
Telegram ranks this channel #1 of 40 here — alongside 39 others — read 16 September 2026
ЧП Курск
@kursk46chp · 28,577
Telegram ranks this channel #1 of 57 here — alongside 56 others — read 9 September 2026
РСЧС Приграни́чье
@Rschs_prigranichie1 · 34,165
Telegram ranks this channel #1 of 74 here — alongside 73 others — read 3 September 2026
Громко, курское приграничье!
@gromkokursk · 36,988
Telegram ranks this channel #1 of 63 here — alongside 62 others — read 1 September 2026
Курск на связи ©
@kursk_nasv · 41,334
Telegram ranks this channel #1 of 79 here — alongside 78 others — read 29 August 2026
Курское приграничье 2.0
@granica046 · 41,487
Telegram ranks this channel #1 of 59 here — alongside 58 others — read 29 August 2026
🇷🇺 Актуальный Курск
@kursk_ak46 · 41,664
Telegram ranks this channel #1 of 73 here — alongside 72 others — read 29 August 2026
Курская область
@kurskadm · 78,706
Telegram ranks this channel #1 of 82 here — alongside 81 others — read 18 August 2026
КУРСКИЙ БОМОНДЪ
@kurskbomond · 225,010
Telegram ranks this channel #1 of 65 here — alongside 64 others — read 11 August 2026
⚡️Курск сейчас
@kursk_now · 27,255
Telegram ranks this channel #2 of 82 here — alongside 81 others — read 10 September 2026
Управление Z 🇷🇺
@control_sigma · 31,471
Telegram ranks this channel #2 of 81 here — alongside 80 others — read 5 September 2026
Приграничный Радар
@prigranichie_radar1 · 32,202
Telegram ranks this channel #2 of 68 here — alongside 67 others — read 5 September 2026
Тревожный Курск | Суджа
@tre_kyrsk · 32,330
Telegram ranks this channel #2 of 69 here — alongside 68 others — read 5 September 2026
🚨 ЧП, Курское приграничье
@incidentkursk · 37,556
Telegram ranks this channel #2 of 22 here — alongside 21 others — read 31 August 2026
Твой Курский край | Новости Курского приграничья
@kursk_info46 · 39,557
Telegram ranks this channel #2 of 78 here — alongside 77 others — read 30 August 2026
Курск №1
@kursk_russia · 44,068
Telegram ranks this channel #2 of 62 here — alongside 61 others — read 28 August 2026
Регион 46 Курск
@r46kursk · 50,117
Telegram ranks this channel #2 of 72 here — alongside 71 others — read 25 August 2026
Новости Курска и Области
@kursk_smi · 60,024
Telegram ranks this channel #2 of 57 here — alongside 56 others — read 22 August 2026
grohot_pgr
@grohot_pgr · 30
Telegram ranks this channel #2 of 77 here — alongside 76 others — read 14 August 2026
Типичный Курск
@tipich_kursk · 150,578
Telegram ranks this channel #2 of 69 here — alongside 68 others — read 12 August 2026
Курск | События | Подслушано
@Kursk_podslushal · 36,196
Telegram ranks this channel #3 of 77 here — alongside 76 others — read 29 September 2026

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

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

2 Wikipedia articles name 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.

Старовойт, Роман Владимирович (ru.wikipedia.org)
“…Российской Федерации}} {{Губернаторы Курской области}} {{ВС|P3789=https://t.me/gubernator_46}} [[Категория:Выпускники БГТУ «Военмех»]] [[Категория:Выпускники…”
read 1 November 2026
Курськ (аеропорт) (uk.wikipedia.org)
“…anguage=uk}}{{Cite web|title=🇷🇺 Роман Старовойт|url=https://t.me/gubernator_46/2139|website=Telegram|accessdate=2022-12-06}}, внаслідок…”
read 1 November 2026

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

“Оперштаб Курской области 🇷🇺” (@gubernator_46), 182,796 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/gubernator_46.

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.