Telegram RegisterThe public register of Telegram
Telegram profile photo for Кому жмет руку Хоценко

Channel

Кому жмет руку Хоценко

@omskpolit

On this record: Topic · Previous handles · Also posting the same content · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry

206subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001352501249
TypeChannel
Username@omskpolit
Created4 December 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live12 September 2026
Measurements held5
Confirmed unchanged2 times, most recently 12 September 2026
On Telegramt.me/omskpolit

Topic

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 24 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.

Previous handles

Recorded in 2019 as “ОМСКПОЛИТ” — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 5 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

2042062056 August 2026 — 206 subscribers7 August 2026 — 206 subscribers12 August 2026 — 204 subscribers26 August 2026 — 205 subscribers3 September 2026 — 206 subscribers6 August 20263 September 2026
5 measurements spanning 28 days. 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 204–206 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 11:57206+1
26 Aug 2026, 06:04205+1
12 Aug 2026, 20:03204-2
7 Aug 2026, 03:48206no change
6 Aug 2026, 07:02206first reading

Engagement

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

Recent posts

5 Aug 2026, 05:48 UTC36 viewsread 7 August 2026
Forwarded from @arhvlasti

📊 Рейтинг губернаторов СФО за июль 2026 года Июль стал для регионов Сибири одним из самых напряженных месяцев: топливный кризис, атаки БПЛА, лесные пожары, ливни, засуха, туристическая нагрузка и коммунальные аварии одновременно проверяли устойчивость губернаторских команд. Оценивали глав 10 регионов по 5 маркерам: федеральные позиции, управленческий результат, реакция на кризисы, публичная активность и общая устой…

4 Aug 2026, 03:17 UTC45 viewsread 7 August 2026
Forwarded from @arhvlastiPhoto

🚦 Система раннего предупреждения. СФО. 27 июля – 2 августа 2026 года 🔴 Красная зона Омская область Главный кризис недели - повторная беспилотная опасность и работа ПВО. В аэропорту Омска вводились ограничения, рейсы из Москвы и Санкт-Петербурга перенаправлялись в Новосибирск. Из-за обломков сбитого БПЛА возник пожар в поле, пострадавших нет. Отменен праздничный концерт ко Дню города. На этом фоне власти сняли лимит…

29 Jul 2026, 16:30 UTC153 viewsread 7 August 2026
Forwarded from @arhvlastiPhoto

О столичности, метро и Высших силах Наблюдаем за дискуссией с чувством глубокого умиротворения. Сначала за звание «третьей столицы» бился Красноярск - коллеги-политологи объясняли, что столичность измеряется амбициями, Универсиадой, количеством фонтанов и уровнем еды в ресторанах. Теперь эстафету приняли омские коллеги. Оказывается, столичность - это уровень стратегических задач от федерального центра, количество …

29 Jul 2026, 01:06 UTC133 viewsread 7 August 2026
Forwarded from @arhvlastiPhoto

Технопром-2026: Новосибирск подтверждает статус столицы сибирской науки и технологий В августе 2026 года Новосибирская область вновь станет эпицентром технологической повестки страны. Анонс XIII Международного форума «Технопром» - не просто новость о событии. Это прямое подтверждение ключевой роли Новосибирска как бесспорной столицы Сибири в сфере науки, инноваций и технологического суверенитета. Почему это важно? …

27 Jul 2026, 06:00 UTC98 viewsread 7 August 2026
Forwarded from @arhvlastiPhoto

🚦 Система раннего предупреждения. СФО. 20–27 июля 2026 года 🔴 Красная зона Алтайский край Ураганный ветер до 40 м/с стал главным кризисом недели: в Краснощековском районе повреждены 152 кровли, нарушалось электроснабжение более 6 тыс. домовладений в 44 населенных пунктах, разворачивались ПВР. Электроснабжение восстановлено, но масштаб ущерба требует контроля. Дополнительный фон — сохраняющиеся риски с топливом и ус…

23 Jul 2026, 20:03 UTC119 viewsread 7 August 2026
Forwarded from @arhvlastiPhoto

Новый рейтинг депутатов: КПД или КВН? Вышел очередной интегральный рейтинг «полезности» депутатов Госдумы — КПДГД от проекта «Депутат Клуб». Четыре параметра по 25%: народ, эксперты, законы, медиа. Звучит солидно. Разбираем. 📌 «Экспертный рейтинг» без экспертов 25% итоговой оценки формирует «профессиональное сообщество политологов, журналистов и региональных экспертов». Фамилий — ноль. Ни панели, ни методики опроса…

21 Jul 2026, 06:32 UTC109 viewsread 7 August 2026
Forwarded from @arhvlastiPhoto

🚦 Система раннего предупреждения. СФО. 13–19 июля 2026 года 🔴 Красная зона Алтайский край Топливный кризис приобретает муниципальное измерение. В Бурлинском районе власти заявили об угрозе остановки ЖКХ и сельхозработ из-за нехватки ГСМ и предложили ввести режим ЧС. В Рубцовске запущен график заправки по номерам автомобилей, аналогичную меру рассматривают в Барнауле. Фактически регион первым в СФО тестирует жестко…

14 Jul 2026, 05:00 UTC121 viewsread 7 August 2026
Forwarded from @arhvlastiPhoto

Photo, posted without a caption

13 Jul 2026, 04:12 UTC111 viewsread 7 August 2026
Forwarded from @arhvlasti

🚦 Система раннего предупреждения. СФО. 6–12 июля 2026 года 🔴 Красная зона Новосибирская область Топливный кризис перешел в режим ЧС-управления: введен режим повышенной готовности, лимиты снижены до 30 л бензина и 60 л дизеля на транзакцию. Власти признают закрытые АЗС, очереди, дефицит отдельных видов топлива, мошеннические схемы с «местами в очереди». На заправки вывели народных дружинников. Для экстренных, комму…

7 Jul 2026, 20:47 UTC151 viewsread 7 August 2026
Forwarded from @arhvlastiFile

«Дитя. Ты приносишь мне открытие смертных и называешь его новым? (Колесников.Русский репортер) Я правил, когда галактика была молода. Я видел восход и падение бесчисленных видов, форм, разумов. И то, что эти двое - Швицгебель и Побер открыли ныне, я знал ещё до того, как их миры остыли от звёздного огня. Они лепечут о «гибкости сосуда сознания», будто младенцы, впервые узревшие пламя. Разум, не скованный плотью... …

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

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.

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.

Сибирский панк
@omsknotdead · 32,176
Telegram ranks this channel #15 of 93 here — alongside 92 others — read 5 September 2026
Омск | Омская область | Новости
@omsk_dvor · 25,425
Telegram ranks this channel #38 of 87 here — alongside 86 others — read 18 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 3 September 2026 — this entry's latest reading, not the date you are reading this.

“Кому жмет руку Хоценко” (@omskpolit), 206 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/omskpolit.

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.