Channel
@vakansiii_belgorod
On this record: Topic · Observations · Growth · Engagement · Posts · Citations · Cite this entry
3,110subscribers
-2 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001397983587 |
|---|---|
| Type | Channel |
| Username | @vakansiii_belgorod |
| Created | Between 1 May 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/vakansiii_belgorod |
Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 12 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
2.9 average views per post against 3,110 subscribers — an engagement rate of 0.092%. Across the 54,164 registered channels in the same cohort — 1,000–3,162 subscribers, posting mainly in Russian — the middle half sit between 10.5% and 35.6%, with a median of 20.1%.
| Window | 30 days (13 July 2026 – 12 August 2026) |
|---|---|
| Posts measured | 20 of 20 published in the window (20 exact, 0 rounded by Telegram) |
| Views totalled | 57 |
| Mature posts only | 0.114% over 13 posts read at least 24h after publication |
| Subscribers | 3,110 measured 12 August 2026 |
| Cohort | b1000:rus · 54,164 channels · p10 5.33% · p25 10.5% · p50 20.1% · p75 35.6% · p90 57.1% |
| Position in cohort | 0.321th percentile · 1/200 the cohort median |
| Uncertainty | ±0.093% of the figure, from Telegram’s rounding |
| Post language | Russian · 100.0%of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_low, last confirmed 12 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 08:23 | 3,110 | -2 |
| 12 Aug 2026, 07:01 | 3,112 | first reading |
20 posts held, back to 9 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 20 (9 August 2026 – 12 August 2026) |
| Views total | 57 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 07: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.
Проходчик (ручная проходка) 💰 200 000 – 450 000 ₽ 📍 Город: Белгород 🏢 Формат: На месте работодателя 📑 Занятость: Вахта 📅 График: Другое 📌 Обязанности: • Выполнение всего комплекса работ по проходке наклонных и вертикальных горных выработок. Бурение шпуров. Выполнение работ по отгрузке горной массы. 🎯 Требования: • Среднее, среднее профессиональное образование. Опыт работы проходчиком от 3 лет (ручная проходка на до…
Сварщик НАКС 💰 250 000 – 280 000 ₽ 📍 Город: Белгород 🏢 Формат: На месте работодателя 📑 Занятость: Вахта 📅 График: 6/1 📌 Обязанности: • Что предстоит делать: Сварка металлоконструкций и технологических трубопроводов. 🎯 Требования: • Области аттестации НАКС - СК п. 1,3 или ГДО п.1, или ОХНВП п. 16. Можно копии НАКС. Контакты: https://hh.ru/vacancy/136149174 Горячие вакансии 🔥 👇 https://vk.ru/@rabota_i_karyera-goryac…
Электромонтажник 💰 180 000 – 190 000 ₽ 📍 Город: Белгород 🏢 Формат: На месте работодателя 📑 Занятость: Вахта 📅 График: 6/1 📌 Обязанности: • 1. Какую работу необходимо выполнять? Монтаж кабеля сечением до 70 мм2. Монтаж кабеленесущих конструкций. Подключение кабеля и оборудования. 🎯 Требования: • Наличие среднего профессионального либо высшего образования (Электротехнические специальности). Официальный опыт работы. …
Бетонщик 💰 От 160 000 ₽ 📍 Город: Белгород 🏢 Формат: На месте работодателя 📑 Занятость: Вахта 📅 График: Другое 📌 Обязанности: • Возведение здания с нуля. Заливка колонн, балки, плит. 🎯 Требования: • Отсутствие медицинских противопоказаний. Физическая выносливость. Опыт работы вахтой. Опыт работы на монолитном строительстве. Контакты: https://hh.ru/vacancy/135444520 Горячие вакансии 🔥 👇 https://vk.ru/@rabota_i_karye…
❗❗ Срочно - Добровольцы на контракт с МО РФ - Самые высокие выплаты + льготы от государства❗❗ ТОЛЬКО МУЖЧИНЫ! Не комиссованные, не офицеры. Не занимаемся переводом в другие части!! ❗️Берем на оператора БПЛА / водителей гуманитарки / артиллерия - Проезд БЕСПЛАТНО из любого города! - Официальный контракт с Минобороны РФ - После подписания контракта 2 500 000. (от МО РФ - 400 000р., плюс 2 100 000р. региональные).…
Помошник бухгалтера 💰 От 60 000 ₽ 📍 Город: Белгород 🏢 Формат: На месте работодателя 📑 Занятость: Полная 📅 График: 5/2 📌 Обязанности: • Ведение бухгалтерского и налогового учета. Ведение бухгалтерского и налогового учета , счета 51, 71,70, 60,62, 58, 76. 🎯 Требования: • Знание 1 с , эдо. Контакты: https://hh.ru/vacancy/135236271 Горячие вакансии 🔥 👇 https://vk.ru/@rabota_i_karyera-goryachie-vakansii
Главный бухгалтер 💰 От 135 000 ₽ 📍 Город: Белгород 🏢 Формат: На месте работодателя 📑 Занятость: Полная 📅 График: 5/2 📌 Обязанности: • Полное ведение бухгалтерского и налогового учета, подготовка и сдача отчетности в ФНС, СФР, Росстат. Формирование финансовой и управленческой отчетности, своевременное... 🎯 Требования: • Высшее профильное образование (бухучет, экономика, финансы). Опыт ведения налогового учета на УСН…
Слесарь-ремонтник 💰 59 000 – 59 000 ₽ 📍 Город: Белгород 🏢 Формат: На месте работодателя 📑 Занятость: Полная 📅 График: 5/2 📌 Обязанности: • Осмотр, наладка и ремонт оборудования. 🎯 Требования: • Профессиональное образование. Опыт работы желателен. Контакты: https://hh.ru/vacancy/136106899 Горячие вакансии 🔥 👇 https://vk.ru/@rabota_i_karyera-goryachie-vakansii
Машинист экскаватора-погрузчика 💰 До 150 000 ₽ 📍 Город: Белгород 🏢 Формат: На месте работодателя 📑 Занятость: Полная 📅 График: 5/2 📌 Обязанности: • Управлять экскаватором-погрузчиком на строительных площадках. Выполнять работы по разработке, планировке и перемещению грунта. Осуществлять подвоз строительных материалов. 🎯 Требования: • Опыт работы машинистом экскаватора-погрузчика от 3 лет. Наличие удостоверения маши…
Пилот FPV 💰 От 442 500 ₽ 📍 Город: Белгород 🏢 Формат: На месте работодателя, Разъездной 📑 Занятость: Полная 📅 График: 1/2 📌 Обязанности: • Проведение регулярных наблюдений за небом с использованием FPV-дронов. Фиксация и анализ данных (астрономические явления, погодные условия, движение воздушных судов... 🎯 Требования: • Опыт работы в управлении FPV-дронами. Внимательность к деталям, способность к монотонной работе …
Слесарь механосборочных работ 💰 75 000 – 75 000 ₽ 📍 Город: Белгород 🏢 Формат: На месте работодателя 📑 Занятость: Полная 📅 График: 5/2 📌 Обязанности: • Изготовление и доводка отдельных деталей и узлов. Проведение испытаний готового изделия. 🎯 Требования: • Средне - специальное образование (предпочтительно техническое). Навыки чтения машиностроительных чертежей. Понимание основ механической обработки материалов. Кон…
Главный бухгалтер 💰 110 000 – 150 000 ₽ 📍 Город: Белгород 🏢 Формат: На месте работодателя 📑 Занятость: Полная 📅 График: 5/2 📌 Обязанности: • Организация, контроль и ведение бухгалтерского и налогового учета хозяйственной деятельности предприятия в 1: С "Бухгалтерия" 8.3 в соответствии с... 🎯 Требования: • высшее профильное образование. - опыт работы Главным бухгалтером от 5 лет. - знание бухгалтерского учета, налог…
Showing the 12 most recent of 20 posts we hold for @vakansiii_belgorod. 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.
Citation-graph rank — 1,148,940 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Работа в Белгороде” (@vakansiii_belgorod), 3,110 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/vakansiii_belgorod.
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.