Telegram RegisterThe public register of Telegram
Telegram profile photo for Управление по работе с населением| Оперативно

Channel

Управление по работе с населением| Оперативно

@urnshakhty

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

810subscribers

-5 since we began measuring on 2 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002077570782
TypeChannel
Username@urnshakhty
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 September 2026
Last confirmed live19 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/urnshakhty

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 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 why it has no browse page of its own yet.

Growth

810815812.52 September 2026 — 815 subscribers2 September 2026 — 815 subscribers11 September 2026 — 814 subscribers19 September 2026 — 810 subscribers2 September 202619 September 2026
4 measurements spanning 17 days, net -5. 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 809–816 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 12:37810-4
11 Sept 2026, 04:01814-1
2 Sept 2026, 03:15815no change
2 Sept 2026, 03:00815first reading

Engagement

15 posts held, back to 13 February 2026the 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 15 posts for this entry, the most recent from 5 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
46s
Average length
23s

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

Recent posts

11 Mar 2026, 10:48 UTC502 viewsread 2 September 2026
Forwarded from @admshakhtyPhoto

Филиал «Шахтинский» сообщает, что с 11-30 час. 11.03.2026г в связи с проведением аварийных-восстановительных работ снижено давление следующих районов улиц: 🔹ул. Советская, 🔹ул. Шевченко, 🔹пер. Мечникова, 🔹пр-т. Чернокозова, 🔹пер. Луговой, 🔹ул. Ленина, 🔹ул. Пролетарская, 🔹пр. Победа Революции, 🔹ул. Разина, 🔹пер. Сквозной, 🔹пер. 1-й Милиционный, 🔹пер. 2-й Милиционный и прилегающие к ним улицы. 💧 Подвоз воды будет осу

9 Mar 2026, 08:08 UTC392 viewsread 2 September 2026
Forwarded from @admshakhtyPhoto

Информируем жителей города Шахты! Губернатором Ю.Б. Слюсарем принято решение: с 5 марта единовременная региональная выплата в Ростовской области при заключении контракта о прохождении военной службы увеличена до 3 млн рублей. Утверждено соответствующее постановление правительства области 📑 https://clck.ru/3SP7TN Кроме того, всем гражданам, заключившим контракт, положена федеральная выплата по линии МО РФ, которая

26 Feb 2026, 17:38 UTC495 viewsread 2 September 2026
Video

Сегодня посетили Артёмовский территориальный отдел, поселок Машзавод. Встретились с жителями, посмотрели проблемные вопросы по течи канализации.

21 Feb 2026, 13:26 UTC580 viewsread 2 September 2026

https://vk.ru/wall-224528048_2769 ШАХТЫ, ДЕРЖИМ СТРОЙ! 19.02.2026 проведен очередной общегородской сбор необходимых вещей в зону специальной военной операции. Управление по работе с населением Администрации города Шахты благодарит отдел по молодежной политики и туризму, лично Кочеткова Романа Владимировича за предоставленное помещение для проведения общегородского гуманитарного сбора! Но, самое главное, мы благодари

18 Feb 2026, 08:58 UTC538 viewsread 2 September 2026
Forwarded from @admshakhtyPhoto

Шахтинцев приглашают на военную службу по контракту. По вопросам службы можно обратиться в Военный комиссариат г. Шахты и Октябрьского района Ростовской области по адресу: г.Шахты, ул. Шевченко, 137. Телефон для справок: +78636224511. Стань Героем, приближающим Победу. 📲 Шахты | Подписывайтесь на нас в MAX #АдминистрацияШахты #Шахты #СВОихнебросаем #Службапоконтракту #поддержкаучастниковСВО #СВО

17 Feb 2026, 10:02 UTC453 viewsread 2 September 2026

Начальник управления по работе с населением Администрации города Шахты Александр Шевченко провел рабочую встречу с руководителем некоммерческой организации «Свободная жизнь» Дмитрием Ковалевым. Основной темой диалога стало взаимодействие территориальных отделов по работе с населением и общественников в рамках реализации социально значимого проекта «Мой город Шахты». В ходе беседы обсудили комплекс совместных мероприя

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

Forward network

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.

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.

Шахты | События | Новости
@Shahti_narod · 29,710
Telegram ranks this channel #25 of 43 here — alongside 42 others — read 19 September 2026
Шахты РУ новости
@rushahty · 27,361
Telegram ranks this channel #30 of 40 here — alongside 39 others — read 19 September 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. 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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“Управление по работе с населением| Оперативно” (@urnshakhty), 810 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/urnshakhty.

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.