Channel
@ohotnadzor55
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
3,034subscribers
+45 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001303352970 |
|---|---|
| Type | Channel |
| Username | @ohotnadzor55 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/ohotnadzor55 |
Other / unclassifiable — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 16 Sept 2026, 17:16 | 3,034 | +3 |
| 12 Sept 2026, 15:56 | 3,031 | +4 |
| 8 Sept 2026, 08:36 | 3,027 | +4 |
| 3 Sept 2026, 04:18 | 3,023 | +2 |
| 30 Aug 2026, 22:15 | 3,021 | +1 |
| 28 Aug 2026, 01:18 | 3,020 | +1 |
| 24 Aug 2026, 18:15 | 3,019 | +4 |
| 20 Aug 2026, 19:34 | 3,015 | +20 |
| 17 Aug 2026, 14:05 | 2,995 | +3 |
| 10 Aug 2026, 13:25 | 2,992 | +3 |
| 6 Aug 2026, 21:15 | 2,989 | no change |
| 6 Aug 2026, 21:04 | 2,989 | first reading |
16 posts held, back to 20 March 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 3 pages 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 16 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
45 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 46.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 21 | 46.7% | |
| 👍 | 14 | 31.1% | |
| 👎 | 8 | 17.8% | |
| 👏 | 1 | 2.22% | |
| 🔥 | 1 | 2.22% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 11 of the 16 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 45 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 20 March 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🎯 Определена дата жеребьевки на добычу самцов косули сибирской и лося во время гона! 📅 10 августа 2026 года в 11:00 в Министерстве природных ресурсов и экологии Омской области состоится жеребьевка по распределению разрешений на добычу: 🦌 самцов косули сибирской во время гона; 🫎 самцов лося во время гона. По итогам приема заявок: •на косулю сибирскую поступило 762 заявки, к участию допущено 760; •на лося поступило…
👍4
Photo, posted without a caption
👍2
🦫 С 7 августа начинается выдача разрешений на добычу соболя! Министерство природных ресурсов и экологии Омской области информирует о начале выдачи разрешений на добычу соболя на сезон охоты 2026–2027 годов. 📅 Прием заявлений стартует 7 августа 2026 года в 8:30. 📍 Где получить разрешение? При личном обращении — по адресу: г. Омск, ул. Куйбышева, 63. 💳 Перед подачей заявления необходимо оплатить: • государственную …
Photo, posted without a caption
🎯Министерство подвело итоги жеребьевки по распределению разрешений на добычу барсука и бурого медведя в общедоступных охотничьих угодьях региона. 📄 Проверить результаты жеребьевки уже можно на сайте Министерства природных ресурсов и экологии Омской области. 📌 Основные цифры: 🐻 Бурый медведь • Подано заявок — 2 132 • Допущено к жеребьевке — 2 132 • Лимит добычи — 417 особей 🦡 Барсук • Подано заявок — 1 641 • Допущ…
Photo, posted without a caption
🦆 С 13 июля в Омской области начинается выдача разрешений на добычу пернатой дичи Министерство природных ресурсов и экологии Омской области сообщает, что с 8:30 13 июля 2026 года начинается прием заявлений и выдача разрешений на добычу пернатой дичи на предстоящий сезон охоты. 📍 Получить разрешение можно: • лично в Министерстве (г. Омск, ул. Куйбышева, 63, каб. 103А); • в МФЦ; • в районных пунктах выдачи разрешений…
❤6
Photo, posted without a caption
❗️Уважаемые охотники! 📌Ежегодно с 15 мая Министерством осуществляется прием заявок на участие в распределении разрешений на добычу барсука между физическими лицами, осуществляющими охоту в общедоступных охотничьих угодьях Омской области. Указанные заявки будут приниматься до 25 мая 2026 года включительно. Заявки на участие в жеребьевке можно подать двумя способами: 🔸представить заявку в электронном виде на Региона…
❤7
Первые состязания гончих собак в Омской области: «Голоса Сибири»! Министерство природных ресурсов и экологии Омской области совместно с Омским областным обществом охотников и рыболовов при поддержке охотпользователей Омской области объявляет о проведении первых в регионе состязаний по зайцу-беляку среди гончих собак «Голоса Сибири». Мероприятие призвано: 🔸 способствовать развитию охотничьего собаководства на террит…
👍5❤4
Photo, posted without a caption
🐾Весенне-летний учет охотничьих ресурсов! Минприроды информирует о начале весенних учетов численности охотничьих ресурсов на территории Омской области в 2026 году: ➡ с 1 апреля по 31 мая – учёт численности и распространения бурого медведя; ➡ с 1 апреля по 1 июня – весенний пролет водоплавающей дичи; ➡с 15 апреля по 20 мая – учёт численности глухаря и тетерева на току. В соответствии с Порядком осуществления госуда…
❤1
Showing the 12 most recent of 16 posts we hold for @ohotnadzor55. 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.
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 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Охотнадзор55 Минприроды Омской области” (@ohotnadzor55), 3,034 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/ohotnadzor55.
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.