Сегодня перед зданием администрации Касторенского района состоялся митинг посвященный годовщине вторжения ВСУ на территорию нашего региона. Два года назад, 6 августа 2024 года, Курская область столкнулась с тяжелейшим испытанием. Мы вспоминаем жителей приграничных районов, вынужденно оставивших родные дома, и отдаем дань памяти нашим воинам и мирным гражданам, которые до последнего вздоха защищали свою землю. Минут…

Channel
Касторенский район
@kastorenskij_rajon
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
678subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001572769139 |
|---|---|
| Type | Channel |
| Username | @kastorenskij_rajon |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 4 times, most recently 12 September 2026 |
| On Telegram | t.me/kastorenskij_rajon |
Topic
Local community — 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 20 September 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 16:58 | 678 | -3 |
| 14 Aug 2026, 15:54 | 681 | -1 |
| 7 Aug 2026, 10:01 | 682 | no change |
| 7 Aug 2026, 03:48 | 682 | first reading |
Engagement
6 posts held, back to 3 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 6 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Сегодня в нашем районе состоялись праздничные мероприятия приуроченные к Дню физкультурника. Торжественная часть началась со слов поздравлений от заместителя главы района по социальной политике Юлии Тимербековны Цыбановой. Особое внимание уделили тем, кто добился высоких результатов. Награды от Министерства спорта Курской области вручила главный консультант ведомства Алина Владимировна Пантелеева. Также приятным мо…
Photo, posted without a caption
Вам пришло подозрительное сообщение в соцсетях? Осторожно, это могут быть мошенники! Злоумышленники продолжают придумывать новые легенды, чтобы убедить свою жертву нарушить закон. Для этого они пишут в соцсетях, на сайтах знакомств и в игровых чатах. Одна из главных целей мошенников — получить доступ к чужим данным, паролям, банковским счетам и управлению устройством. Злоумышленники могут не только похитить деньги,…
В Новокасторном отметили День железнодорожника🎉 🚂1 августа поселок Новокасторное отпраздновал День железнодорожника — день, который здесь по праву считают главным профессиональным праздником. Для местных жителей железная дорога — это не просто транспортная артерия, а основа истории и жизни поселка. Центром торжеств стал парк отдыха, обновленный по нацпроекту «Формирование комфортной городской среды». С приветственн…
Photo, posted without a caption
Showing the 6 most recent of 6 posts we hold for @kastorenskij_rajon. 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
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“Касторенский район” (@kastorenskij_rajon), 678 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/kastorenskij_rajon.
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.