Telegram RegisterThe public register of Telegram
Telegram profile photo for Типичный Курск

Channel

Типичный Курск

@tipich_kursk

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

150,300subscribers

-1,403 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001343310930
TypeChannel
Username@tipich_kursk
Description🔥Актуальные новости Курской области Прислать новость: @tipich_kursk_bot Реклама/сотрудничество: @tipich_kursk46 Биржа: https://telega.in/c/kursk_tipich Регистрация в РКН: clck.ru/3QcUaH
Created6 October 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/tipich_kursk

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 9 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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 5 other registered channels. This entry also forms a group of 2 channels linked by matching posts. 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
@kursk_chp46/954622 Aug 2026, 09:59 UTC@tipich_kursk/27343 · this entry22 Aug 2026, 09:59 UTC1.00under a minute
@tipich_kursk/27908 · this entry31 Oct 2026, 11:13 UTC@barakholka46/1181131 Oct 2026, 15:09 UTC0.953.9 hours
@tipich_kursk/27399 · this entry28 Aug 2026, 07:46 UTC@barakholka46/1159728 Aug 2026, 08:18 UTC0.9432 minutes
@tipich_kursk/27239 · this entry4 Aug 2026, 15:28 UTC@barakholka46/115445 Aug 2026, 07:57 UTC0.9316 hours
@tipich_kursk/27986 · this entry11 Nov 2026, 16:02 UTC@barakholka46/1184511 Nov 2026, 16:33 UTC0.9331 minutes
@tipich_kursk/27337 · this entry21 Aug 2026, 12:33 UTC@barakholka46/1157921 Aug 2026, 14:26 UTC0.921.9 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
@kursk_chp4648 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (47–1)
@barakholka466 (6/6 hand-verifiable sample passed)0.922.5 hoursthis entry (6–0)
@okkursk5 (5/5 hand-verifiable sample passed)0.912.5 hoursthis entry (5–0)
@typical_kursk5 (5/5 hand-verifiable sample passed)0.9164 minutesthis entry (3–2)
@tetkino5 (5/5 hand-verifiable sample passed)0.895.0 hoursthis entry (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. 2 of the 2 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 403 comparable posts for this entry, running 2 August 2026 to 12 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @tipich_kursk — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · clone_source, last confirmed 13 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

150,300151,703151,001.56 August 202611 November 2026
66 measurements spanning 98 days, net -1,403. 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 150,090–151,913 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
11 Nov 2026, 17:58150,300-22
9 Nov 2026, 21:41150,322-24
8 Nov 2026, 13:46150,346-52
7 Nov 2026, 09:39150,398-23
6 Nov 2026, 12:49150,421-40
5 Nov 2026, 12:10150,461-16
4 Nov 2026, 13:19150,477-16
3 Nov 2026, 12:54150,493-38
2 Nov 2026, 13:10150,531-47
1 Nov 2026, 14:28150,578-57
31 Oct 2026, 11:49150,635-68
30 Oct 2026, 10:16150,703-53
29 Oct 2026, 07:10150,756-17
28 Oct 2026, 06:07150,773-45
27 Oct 2026, 02:39150,818-15
26 Oct 2026, 03:45150,833-12
25 Oct 2026, 02:27150,845-41
24 Oct 2026, 02:36150,886+3
23 Oct 2026, 03:57150,883-41
22 Oct 2026, 02:57150,924first reading

Engagement

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

ERR · 30 days
8.13%
avg views ÷ 150,300 subscribers
Avg views / post
12,200
178 posts measured
Reaction rate
0.621%
reactions ÷ views · ER floor
Posts in window
178
of 610 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 12 November 2026
Posts held610 (2 August 2026 – 12 November 2026)
Views total2,173,740
Reactions total13,497
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 05:47 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
≈10,800
Videos
≈5,620
Links
≈16,400

Lifetime counters from Telegram’s own channel header, read 13 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
1h 08m
Average length
35s

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

57,239 reactions across 593 posts, in 46 distinct kinds. The most used accounts for 14.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏8,13714.2%
🤣7,14912.5%
🔥5,5069.62%
🤬5,4499.52%
👍5,1979.08%
🤡4,9498.65%
❤4,5017.86%
😱4,3627.62%
🤯2,4234.23%
😁2,3234.06%
👎1,6902.95%
😢1,0121.77%
😭6451.13%
🍾4940.863%
👏4920.86%
😡4820.842%
☃3400.594%
🥱2270.397%
🙉1710.299%
🗿1610.281%
26 further kinds1,5292.67%

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

Measured over the 610 most recent posts we hold, published 2 August 2026 to 12 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
29
across the posts below
Posts paid on
21
of 610 we hold a reading for · 3%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @tipich_kursk. 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 610 most recent posts we hold for this entry, published 2 August 2026 to 12 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
0.328%
2 of 610 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
11,500
over 2 measured posts
Median views · rest
12,900
over 608 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzqfnYuE128 October 202628 October 2026
2Vtzqx1vjBL17 November 20267 November 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 610 most recent posts we hold, published 2 August 2026 to 12 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

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

12 Nov 2026, 22:51 UTC≈3,980 views37 reactionsread 13 November 2026

💥Громко над Курском! Подробности тут: 👉 max.ru/kursk_tipich

🙏20🔥8👍3🤬2😱2❤1😁1

12 Nov 2026, 17:43 UTC≈10,100 views160 reactions2 Starsread 13 November 2026
Photo

❗️ Сообщают, что в Курске БПЛА упал на жилой дом Подробности тут: 👉 max.ru/kursk_tipich

🤯43🤡35🔥24🙏22😱13🤣11❤5👌5

12 Nov 2026, 16:31 UTC≈10,400 views54 reactionsread 13 November 2026

💥Громко над Курском! Следим за ситуацией тут 👇 https://max.ru/kursk_tipich

🙏17🔥14🤬8👍7😁7❤1

12 Nov 2026, 10:49 UTC≈10,800 views51 reactionsread 13 November 2026

❗️❗️❗️❗️❗️❗️ Ракетная опасность на всей территории Курской области Следим за ситуацией тут 👇 https://max.ru/kursk_tipich

🔥17🙏11🤬9👍5😁4🤣2❤1🤯1

12 Nov 2026, 10:05 UTC≈10,500 views62 reactionsread 13 November 2026
Photo

Водителя, насмерть сбившего подростка на Энгельса, отправили в колонию на 7,5 года 22-летний автомобилист в состоянии опьянения ехал со скоростью почти 100 км/ч, проехал на красный и сбил двух подростков, переходивших дорогу на зелёный. Один погиб на месте, второй получил травмы. После ДТП водитель отказался от медосвидетельствования. Суд назначил ему 7,5 года колонии общего режима и запретил садиться за руль на 2,…

👍25🤯13🤣9😱8❤5🤬1😢1

12 Nov 2026, 07:24 UTC≈10,100 views172 reactionsread 13 November 2026
Photo

⚡️У прошедшего первым в России вакцинацию от рака курянина исчезли метастазы В течение четырех месяцев не выявлено новообразований, рассказал "Газете. Ru" научный руководитель Центра имени Гамалеи Александр Гинцбург. По его словам, пациент будет находиться под наблюдением врачей в течение трех лет. 📲 Висит телега? Читайте наши новости в МАХ

🙏118👍24❤9😁6🤡5🔥4🤣3👎2

12 Nov 2026, 04:49 UTC≈9,590 views48 reactionsread 13 November 2026

❗️❗️❗️❗️❗️❗️ Ракетная опасность на всей территории Курской области UPD: Отбой 08:01 Следим за ситуацией тут 👇 https://max.ru/kursk_tipich

🙏19❤9🤬7👍6🤣4😍2🤯1

11 Nov 2026, 16:02 UTC≈11,000 views133 reactionsread 13 November 2026
Photo

❗️Курянин отсудил у комитета ЖКХ Курска около 270 тысяч за яму на Дериглазова ⠀ Мопед Алексея ночью 7 мая на проспекте Дериглазова у дома №31 попал в выбоину глубиной около 15 см. Участок не был огорожен и без предупреждающих знаков. Мужчина получил перелом лучевой кости и до 3 июля был на больничном, а мопед восстановлению не подлежал. ⠀ Суд взыскал с комитета ЖКХ 100 тысяч компенсации и расходы на юридические услуг…

👍107🔥11❤4🤡4🤣4😁3

11 Nov 2026, 14:59 UTC≈9,760 views29 reactionsread 13 November 2026
Video

❗️С Возможностью приобретения БЕЗ ПВ Этого дня ждут целый год. И нет, это не Новый год 🎄 Это Чёрная пятница — 11.11! А в жилом комплексе АРТ она приносит скидку до 1 400 000 рублей на квартиру 🤩 🔥Клубный дом в центре города, вся необходимая инфраструктура рядом и всего 40 минут до Москвы. ❗️С Возможностью приобретения БЕЗ ПВ 👶Детский сад и школа — в пяти минутах, а дорога к ним проходит без машин. Удобно для род…

🤡17🤣6❤2👍2🔥1🗿1

11 Nov 2026, 14:10 UTC≈9,970 views41 reactionsread 13 November 2026
Video

❗️ДТП на Энгельса в сторону Парковой, напротив СКК. Движение может быть затруднено. 📲 Висит телега? Читайте наши новости в МАХ

😁13😱7👍5🤬5❤4🤣3😢3😡1

11 Nov 2026, 09:12 UTC≈10,200 views89 reactionsread 13 November 2026

😱59-летний житель Курской области стал жертвой мошенников, отдав им в общей сложности более 18 млн рублей. Сначала под предлогом защиты аккаунта на «Госуслугах» и «проверки» купюр он передал курьерам 4 млн рублей сбережений. Спустя несколько месяцев он продал дом и по требованию лжесотрудников банка и правоохранительных органов отдал еще 14 млн рублей. После этого «куратор» перестал выходить на связь. Возбуждено уго…

🤣47🤯23🤡10❤3👏3😢2🤔1

11 Nov 2026, 07:13 UTC≈10,700 views51 reactionsread 13 November 2026

💥Громко над Курском! Следим за ситуацией тут 👇 https://max.ru/kursk_tipich

🙏15🔥13👀7🤣7🤯3❤2👌1🤬1

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@tipich_kursk edited 4 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
22 August 2026
Most recent edit
7 November 2026

Posts recorded as deleted after publishing

We recorded 2 posts on @tipich_kursk 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
22 September 2026
Most recent seen missing
12 October 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
0

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 1 registered channel — 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.

КУРСКИЙ БОМОНДЪ
@kurskbomond · 224,546
#1
Оперштаб Курской области 🇷🇺
@gubernator_46 · 182,482
#2
Зеленка
@war_territory · 14,835
#3
СУДЖА РОДНАЯ 🇷🇺
@rodnaya_sudzha · 71,120
#4
Жесть Курск
@zhest_kursk_146 · 91,251
#5
Курск №1
@kursk_russia · 43,948
#6
Курская область
@kurskadm · 78,398
#7
NewStream * Курск - мы вместе!
@news_strm · 4,518
#8
grohot_pgr
@grohot_pgr · 30
#9
Громко, курское приграничье!
@gromkokursk · 36,895
#10
Курское приграничье 2.0
@granica046 · 41,376
#11
Тревожный Курск | Суджа
@tre_kyrsk · 32,208
#12
🇷🇺 Актуальный Курск
@kursk_ak46 · 41,578
#13
Регион 46 Курск
@r46kursk · 50,036
#14
🚨ЧП КУРСК | ПРИГРАНИЧЬЕ
@kursk_chp46 · 9,287
#15
Жесть Белгород
@zhest_belgorod · 588,064
#16
Приграничный Радар
@prigranichie_radar1 · 32,130
#17
РСЧС Приграни́чье
@Rschs_prigranichie1 · 34,119
#18
Нетипичный Курск
@typical_kursk · 19,089
#19
Суджа в Telegram
@sudzha_tme · 28,715
#20
ЧП Курск
@kursk46chp · 28,540
#21
Теткино / Курск / Глушково / Коренево / Рыльск / Льгов /Суджа / Курчатов / Железногорск
@tetkino · 36,282
#22
Управление Z 🇷🇺
@control_sigma · 31,369
#23
Типичный Рыльск
@typical_rilsk46 · 31,575
#24
Секундочку
@sekundamedia · 9,758
#25
Курск на связи ©
@kursk_nasv · 41,261
#26
Курская аномалия
@KurskAnomalia · 8,473
#27
Сейм: новости Курской области🇷🇺
@seymkursk · 16,151
#28
Глушковский Бомондъ/ Курское приграничье
@BomondGlushkovsk · 13,905
#29
Приграничный Доzор
@prigran_dozor · 11,291
#30
Новости Курска и Области
@kursk_smi · 59,889
#31
⚡️Курск сейчас
@kursk_now · 27,140
#32
Город Курск
@kurskpressa · 6,661
#33
Настоящий Гладков
@vvgladkov · 398,330
#34
КУРСКСИТИ|Новости города и области
@kurskcityru · 7,453
#35
ПОГРАНИЧНИК ИЗ АДА
@pograni4nik_iz_ada · 103,983
#36
Курская Telega
@KurskayaTelega · 10,480
#37
Вести Курск
@vesti_kursk · 11,123
#38
МОЙ КУРСК | НОВОСТИ 🇷🇺
@my_kursk_46 · 11,587
#39
Курские известия|Новости Курска
@kursk_time · 7,241
#40
Подслушано Курчатов
@podslushano_kurchatov1 · 23,461
#41
Твой Курский край | Новости Курского приграничья
@kursk_info46 · 39,415
#42
Глушково /Курская область
@gluchkovo · 9,478
#43
Инцидент Курск
@incident46 · 22,020
#44
МЧС Курской области
@mchs_46 · 10,999
#45
ЧС Приграни́чье
@rschs_prigranichie · 27,881
#46
Курские новости
@kursk_novost · 17,261
#47
Наш Железногорск
@Nash_Zheleznogorsk · 14,463
#48
Приграничье
@atypicalday · 63,461
#49
Железногорск
@zhelek46rus · 5,894
#50
Новости Курска
@barakholka46 · 11,882
#51
🚨 ЧП, Курское приграничье
@incidentkursk · 37,454
#52
Соловьиный край
@Solovej46 · 8,192
#53
ГОРОД КУРСК
@gorod_kursk · 5,879
#54
Прямой Эфир • Новости
@novosti_efir · 3,875,626
#55
Мир сегодня с "Юрий Подоляка"
@yurasumy · 2,661,091
#56
Readovka
@readovkanews · 2,015,419
#57
АВТОКАДР_46
@Avtokadr46 · 55,817
#58
Проспект Дериглазова|Курск
@DeriglazovaProspekt · 13,237
#59
Тринадцатый.
@Z13_Separ · 208,541
#60
Минобороны России
@mod_russia · 649,746
#61
ZАПИСКИ VЕТЕРАНА 🇷🇺
@notes_veterans · 273,644
#62
Роман Алехин
@Alekhin_Telega · 115,907
#63
Белгород №1
@belgorod01 · 189,419
#64
Радар Белгород
@radarb31 · 137,294
#65
машера (mashera)
@massheraa · 105,771
#66
ДНЕВНИК МРАКОБОРЦЕВ: Территория Героев
@iamhumancatcher · 407
#67
Роман Старовойт
@roman_starovoyt · 4,839
#68
ЮЗГУ 💙
@swsu_kursk · 5,646
#69

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

Молниеносные новости 🗞️
@Rostov_Krasnodar1 · 23,940
Telegram ranks this channel #1 of 39 here — alongside 38 others — read 22 September 2026
⚡️Курск сейчас
@kursk_now · 27,140
Telegram ranks this channel #1 of 82 here — alongside 81 others — read 10 September 2026
Тревожный Курск | Суджа
@tre_kyrsk · 32,208
Telegram ranks this channel #1 of 69 here — alongside 68 others — read 5 September 2026
Нетипичный Курск
@typical_kursk · 19,089
Telegram ranks this channel #2 of 19 here — alongside 18 others — read 3 October 2026
Инцидент Курск
@incident46 · 22,020
Telegram ranks this channel #2 of 58 here — alongside 57 others — read 21 September 2026
Ополчение/Рыльск/Медведь
@rylskopolchenie · 22,470
Telegram ranks this channel #2 of 59 here — alongside 58 others — read 20 September 2026
Зеленка
@war_territory · 14,835
Telegram ranks this channel #2 of 55 here — alongside 54 others — read 16 September 2026
ЧП Курск
@kursk46chp · 28,540
Telegram ranks this channel #2 of 57 here — alongside 56 others — read 9 September 2026
Суджа в Telegram
@sudzha_tme · 28,715
Telegram ranks this channel #2 of 63 here — alongside 62 others — read 9 September 2026
Типичный Рыльск
@typical_rilsk46 · 31,575
Telegram ranks this channel #2 of 49 here — alongside 48 others — read 5 September 2026
РСЧС Приграни́чье
@Rschs_prigranichie1 · 34,119
Telegram ranks this channel #2 of 74 here — alongside 73 others — read 3 September 2026
Громко, курское приграничье!
@gromkokursk · 36,895
Telegram ranks this channel #2 of 63 here — alongside 62 others — read 1 September 2026
Курск на связи ©
@kursk_nasv · 41,261
Telegram ranks this channel #2 of 79 here — alongside 78 others — read 29 August 2026
Курское приграничье 2.0
@granica046 · 41,376
Telegram ranks this channel #2 of 59 here — alongside 58 others — read 29 August 2026
🇷🇺 Актуальный Курск
@kursk_ak46 · 41,578
Telegram ranks this channel #2 of 73 here — alongside 72 others — read 29 August 2026
Приграничье
@atypicalday · 63,461
Telegram ranks this channel #2 of 64 here — alongside 63 others — read 21 August 2026
СУДЖА РОДНАЯ 🇷🇺
@rodnaya_sudzha · 71,120
Telegram ranks this channel #2 of 81 here — alongside 80 others — read 20 August 2026
Оперштаб Курской области 🇷🇺
@gubernator_46 · 182,482
Telegram ranks this channel #2 of 78 here — alongside 77 others — read 11 August 2026
КУРСКИЙ БОМОНДЪ
@kurskbomond · 224,546
Telegram ranks this channel #2 of 65 here — alongside 64 others — read 11 August 2026
Подслушано Курчатов
@podslushano_kurchatov1 · 23,461
Telegram ranks this channel #3 of 40 here — alongside 39 others — read 16 September 2026
Приграничный Радар
@prigranichie_radar1 · 32,130
Telegram ranks this channel #3 of 68 here — alongside 67 others — read 5 September 2026
🚨 ЧП, Курское приграничье
@incidentkursk · 37,454
Telegram ranks this channel #3 of 22 here — alongside 21 others — read 31 August 2026
Твой Курский край | Новости Курского приграничья
@kursk_info46 · 39,415
Telegram ranks this channel #3 of 78 here — alongside 77 others — read 30 August 2026
Курск №1
@kursk_russia · 43,948
Telegram ranks this channel #3 of 62 here — alongside 61 others — read 28 August 2026

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

“Типичный Курск” (@tipich_kursk), 150,300 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/tipich_kursk.

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.