Job listings — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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
40 measurements spanning 70 days, net +7,537. 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 24,827–34,960 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 40
Measured (UTC)
Subscribers
Change
16 Oct 2026, 12:10
33,533
-39
15 Oct 2026, 13:06
33,572
+9
14 Oct 2026, 12:38
33,563
+34
13 Oct 2026, 02:30
33,529
-262
8 Oct 2026, 21:59
33,791
+245
4 Oct 2026, 10:57
33,546
+795
25 Sept 2026, 23:57
32,751
+1,208
19 Sept 2026, 06:40
31,543
+156
16 Sept 2026, 19:36
31,387
+43
14 Sept 2026, 20:36
31,344
+70
13 Sept 2026, 04:20
31,274
+90
11 Sept 2026, 08:58
31,184
+315
8 Sept 2026, 14:37
30,869
+370
5 Sept 2026, 10:36
30,499
+335
3 Sept 2026, 16:18
30,164
-491
2 Sept 2026, 12:23
30,655
+117
1 Sept 2026, 13:26
30,538
+82
31 Aug 2026, 15:35
30,456
+209
30 Aug 2026, 14:16
30,247
+206
29 Aug 2026, 14:55
30,041
first reading
Engagement
17 posts held, back to 4 May 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 118 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
66.5%
avg views ÷ 33,533 subscribers
Avg views / post
22,300
2 posts measured
Reaction rate
1.15%
reactions ÷ views · ER floor
Posts in window
2
of 17 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 15 October 2026
Posts held
17 (4 May 2025 – 15 October 2026)
Views total
44,600
Reactions total
514
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
17 Oct 2026, 02:01 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
35
Videos
3
Links
27
Lifetime counters from Telegram’s own channel header, read 17 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
2,570 reactions across 17 posts, in 4 distinct kinds. The most used accounts for 51.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🤬
1,325
51.6%
❤
908
35.3%
🔥
186
7.24%
👍
151
5.88%
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 17 of the 17 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 2,570 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 4 May 2025 to 15 October 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.
Хреновые новости. Комитет Госдумы по обороне внезапно реанимировал один из самых опасных для призывников законопроектов - отмену автоматической приостановки отправки в войска при подаче иска в суд на решение комиссии субъекта.
Напомню предысторию: весной проект предложил лишить призывников этого главного судебного щита. Но затем 11 из 12 депутатов-авторов отозвали подписи, а последний умер. Документ остался без авто…
Взрывы в Дата-центрах Яндекса задели бот выдачи статьи.
Пару дней назад все легло и быстро возобновилось, но повторный взрыв затянул техническое восстановление на стороне сервиса.
Upd. Все работает, у кого не пришли сообщения перезапустите пожалуйста бота.
Что делать, если пришла повестка в военкомат в 2026 году?
🔥Полный алгоритм действий: как определить, законна ли повестка, какие виды повесток существуют, как защитить свои права и не оказаться в армии по ошибке.
❗️Разбираем все нюансы нового призыва, который теперь идёт круглый год.
⬇️ В этом видео:
— Что делать в первые минуты после получения повестки
— Юридическая сила бумажных и электронных повесток
— Уважител…
Всё, статья-сайт снова в строю! 🚀
Пацаны, ещё раз огромное спасибо всем, кто откликнулся и накидал копий. Вы спасли мне кучу нервов и времени. Урок усвоен, бэкапы теперь делаю 😅.
Раз уж сел восстанавливать, то местами добавил немного дополнительной информации и заодно причесал статью под условия 2026 года. Ссылка в закрепленном сообщении.
По поводу контента: завтра-послезавтра выпущу новый ролик, и наконец-то виде…
Всем привет. У нас умер сервер со статьей. Умер окончательно похоронив все данные, как сообщила поддержка. Бэкап я не делал c 2024 года и редактировал статью через html редактор встроенный в панель управления... Будем все восстанавливать. Ps: не думал, что так быстро скинут копию сайта)) Спасибо большое всем, кто откликнулся
Свежий update по всем материалам ⬇️
Многие потеряли, спрашивают в личке: «Денис, ты где? Всё норм?»
Отвечаю всем сразу: Я никуда не пропал.
Просто работы столько, что на ведение канала и видео физически не оставалось времени. Процесс идет, результаты стабильные, хоть гайки и закручивают.
Но вынырнул я не с пустыми руками. Пока было затишье(январь спасибо, что ты есть), я провел полную ревизию всех материалов.
Чт…
Москва Шереметьево, запрет на вылет при электронной повестке. 11.09.25
Мужчина, 28, не служил, 8 сентября пришла электронная повестка (для прохождения медкомиссии, на 22 октября). До этого уклонялся, повесток не получал.
На сайте повесток сразу стал отображаться запрет на выезд, но так как отпуск был запланирован еще в мае, рискнул лететь.
На паспортном контроле в Шереметьево сразу без слов вызвали офицеров, которы…
Расписание болезней изменено!
29 августа Правительство РФ своим постановлением внесло изменения в Расписание болезней. Это главный документ, которым руководствуются врачи в военкомате при определении категории годности к военной службе.
Документ опубликован 5 сентября на Портале правовых актов РФ и вступил в силу.
С психушкой все в порядке, станет даже проще, мигрень так же не призывная и на месте 👌
Скоро выпущу …
Заработал Реестр повесток
Житель Тверской области, подлежащий призыву на срочную службу, получил два уведомления: смс с текстом «Вам направлена повестка в военкомат», а также уведомление через «Госуслуги» о размещении повестки в Реестре с указанием срока вручения и перечнем ограничений, включая запрет на выезд из России.
Все скриншоты отправил нам — они подтверждают, что речь идет не о фишинговых рассылках, а о раб…
Showing the 12 most recent of 17 posts we hold for @voenkomoff_pub. 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.
Posts edited after publishing
@voenkomoff_pub edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
13 October 2026
Most recent edit
13 October 2026
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
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 16 October 2026 — this
entry's latest reading, not the date you are reading this.
“Voenkomoff” (@voenkomoff_pub), 33,533 subscribers as measured 16 October 2026. Telegram Register, tgregister.com/channel/voenkomoff_pub.
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.