Channel
@a_sapozhnikov_chita
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
891subscribers
-362 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001508079683 |
|---|---|
| Type | Channel |
| Username | @a_sapozhnikov_chita |
| Created | 12 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/a_sapozhnikov_chita |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 44% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 02:18 | 891 | -14 |
| 7 Sept 2026, 10:19 | 905 | -285 |
| 2 Sept 2026, 04:53 | 1,190 | -2 |
| 30 Aug 2026, 12:14 | 1,192 | -4 |
| 27 Aug 2026, 21:07 | 1,196 | -2 |
| 25 Aug 2026, 04:13 | 1,198 | -7 |
| 22 Aug 2026, 07:17 | 1,205 | -12 |
| 18 Aug 2026, 17:33 | 1,217 | -8 |
| 16 Aug 2026, 02:24 | 1,225 | -12 |
| 12 Aug 2026, 17:06 | 1,237 | -8 |
| 9 Aug 2026, 21:21 | 1,245 | -6 |
| 6 Aug 2026, 22:33 | 1,251 | -2 |
| 6 Aug 2026, 11:51 | 1,253 | no change |
| 6 Aug 2026, 09:58 | 1,253 | first reading |
6 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 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.
Продолжаю работать в муниципальных образованиях - сегодня в Забайкальске. Посетил строительную площадку реконструкции международного автомобильного пункта пропуска «Забайкальск» — одного из важнейших транспортно-логистических объектов не только Забайкальского края, но и всей страны. О ходе реализации проекта рассказал заместитель руководителя организации, ведущей реконструкцию, Роман Николаевич. Обсудили этапы стро…
Продолжаю работать в муниципальных образованиях - сегодня в Забайкальске. Посетил строительную площадку реконструкции международного автомобильного пункта пропуска «Забайкальск» — одного из важнейших транспортно-логистических объектов не только Забайкальского края, но и всей страны. О ходе реализации проекта рассказал заместитель руководителя организации, ведущей реконструкцию, Роман Николаевич. Обсудили этапы стро…
🗳 «Единая Россия» получила № 1 в избирательном бюллетене 🏛 В Центральной избирательной комиссии России состоялась жеребьёвка, определившая порядок расположения наименований политических партий в избирательном бюллетене на выборах депутатов Государственной Думы IX созыва. 1️⃣ По итогам процедуры «Единая Россия» будет расположена в бюллетене первой. В жеребьёвке приняли участие представители 11 политических партий, ф…
✅Краснокаменску - ровные дороги и уютные дворы ▶️Заместитель председателя Законодательного Собрания Забайкальского края, член Регионального политсовета партии "Единая Россия" Александр Сапожников вместе с однопартийцами оценил ход ремонта дорог и дворов во втором городе региона. 💬"Сейчас активно идёт ремонт дороги номер 45 (до полигона ТБО). Погодные условия и проливные дожди внесли некоторые коррективы в капитальн…
📍 Краснокаменску — внимание Единой России и краевых властей 🏛 На этой неделе в Краснокаменском муниципальном округе с рабочим визитом находится заместитель председателя Законодательного Собрания Забайкальского края Александр Сапожников. 🏫 «Поездка плановая и связана с мониторингом объектов народной программы Единой России и национальных проектов. В Краснокаменске близится к завершению капитальный ремонт двух средни…
📚 7 августа с 11:00 до 13:00 в Штабе общественной поддержки «Единой России» в Чите состоится Единый день приёмов участников специальной военной операции и членов их семей по вопросам образования. 🤝 Защитники Отечества и их близкие смогут оставить обращения, получить необходимые разъяснения и подробные консультации по интересующим их темам. 📞 Записаться на приём можно по телефону: 23-00-73. 📍 Адрес: г. Чита, ул. Бу…
Showing the 6 most recent of 6 posts we hold for @a_sapozhnikov_chita. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Александр Сапожников” (@a_sapozhnikov_chita), 891 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/a_sapozhnikov_chita.
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.