Channel
@kurskchp
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Cite this entry
119subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001655587762 |
|---|---|
| Type | Channel |
| Username | @kurskchp |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/kurskchp |
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 26 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
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.
Posts published here appear in near-verbatim form on 1 other registered channel. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @typical_kursk/312916 Aug 2026, 09:18 UTC | @kurskchp/8008 · this entry6 Aug 2026, 09:18 UTC | 1.00 | under a minute |
| @typical_kursk/312936 Aug 2026, 09:55 UTC | @kurskchp/8011 · this entry6 Aug 2026, 09:55 UTC | 1.00 | under a minute |
| @typical_kursk/312966 Aug 2026, 11:20 UTC | @kurskchp/8014 · this entry6 Aug 2026, 11:21 UTC | 1.00 | under a minute |
| @typical_kursk/312986 Aug 2026, 12:17 UTC | @kurskchp/8015 · this entry6 Aug 2026, 12:17 UTC | 1.00 | under a minute |
| @typical_kursk/312996 Aug 2026, 12:45 UTC | @kurskchp/8016 · this entry6 Aug 2026, 12:45 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @typical_kursk | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | @typical_kursk (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. 3 of the 3 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 12 comparable posts for this entry, running 5 August 2026 to 6 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @typical_kursk. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, 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.
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 12:54 | 119 | -1 |
| 20 Oct 2026, 04:28 | 120 | +1 |
| 10 Sept 2026, 00:42 | 119 | +1 |
| 23 Aug 2026, 15:34 | 118 | -1 |
| 16 Aug 2026, 03:14 | 119 | +2 |
| 9 Aug 2026, 05:01 | 117 | no change |
| 8 Aug 2026, 07:04 | 117 | -1 |
| 7 Aug 2026, 11:36 | 118 | first reading |
20 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 1 page 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
‼️Растёт количество жертв украинских преступлений В результате атаки вражеского дрона в селе Вишнево Беловского района пострадали два человека: у 41-летнего мужчины слепые осколочные ранения спины и левого плеча. У Дмитрия Сергеевича 1981 года рождения слепые осколочные ранения левого бедра и левой стопы. Им уже оказали первую помощь, везём в Курскую областную больницу. Наши врачи ждут раненых и сделают всё, чтобы …
Курянин, насмерть избивший прохожего в центре Курска, предстанет перед судом Трагедия произошла 18 мая в центре Курска. По версии следствия, ночью 25-летний местный житель, находясь в состоянии алкогольного опьянения, вступил в конфликт с 24-летним прохожим. Во время ссоры обвиняемый нанес оппоненту сильный удар в область челюсти. Потерпевший потерял равновесие, упал и ударился головой о землю. Полученные травмы ок…
Photo, posted without a caption
❗️Сеймским отделом полиции УМВД России по г. Курску разыскивается мужчина, подозреваемый в совершении хищения из магазина. Граждане, располагающие информацией о местонахождении разыскиваемого, могут сообщать об этом по номеру 8-919-175-05-05 или телефону дежурной части 36-00-62. 📢 Подписаться на Курск 💬 Прислать информацию
❗️Над Курском сбита вражеская воздушная цель 📢 Подписаться на Курск 💬 Прислать информацию
Photo, posted without a caption
Мурал, посвященный Толе Минашкину, начали наносить на торце дома рядом с кинотеатром «Юность». Ранее изображение планировали разместить по адресу Клыкова, 62, но там против выступили жильцы. Теперь портрет 5-летнего ребенка, погибшего на курском пляже в результате падения беспилотника, появится в центре города. Впрочем, мнение жильцов и здесь было неоднозначно. 📢 Подписаться на Курск 💬 Прислать информацию
❗️Очень громко было в Курске. 📢 Подписаться на Курск 💬 Прислать информацию
❗️При повторном ударе дрона в Рыльском районе пострадал 42-летний мужчина В Рыльском районе при ликвидации последствий атаки дрона пострадал 42-летний мужчина. После атаки дрона ВСУ начался пожар, и житель деревни Викторовка начал тушить возгорание. В этот момент произошёл повторный удар. Мужчина сорвался с крыши и получил травмы. - У него ушибы шейного и грудного отделов позвоночника и грудной клетки. Его отвезут …
❗️Повторно многочисленные фиксации БПЛА в небе над областью! Льгов - меры безопасности! Пролет БПЛА! 📢 Подписаться на Курск 💬 Прислать информацию
Предварительно, возгорание связано с прилетом обломка сбитого БПЛА. 📢 Подписаться на Курск 💬 Прислать информацию
❗️❗️Сводка об оперативной обстановке в Курской области за прошедшие сутки. Всего в период с 09:00 5 августа до 09:00 6 августа сбито 157 вражеских беспилотников различного типа. 20 раз враг применил артиллерию по отселённым районам. 15 раз беспилотники атаковали нашу территорию с помощью взрывных устройств. В результате атак пострадали 11 человек. К огромному горю ещё двое погибли: 72-летний пенсионер в деревне Тро…
Showing the 12 most recent of 20 posts we hold for @kurskchp. 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.
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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“ЧП Курск | РЕЗЕРВ” (@kurskchp), 119 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/kurskchp.
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.