Channel
@Rabota_v_Zlatouste_1
On this record: Topic · Observations · Growth · Engagement · Posts · Citations · Cite this entry
1,232subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001779918449 |
|---|---|
| Type | Channel |
| Username | @Rabota_v_Zlatouste_1 |
| Created | Between 1 December 2021 and 31 March 2023— 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/Rabota_v_Zlatouste_1 |
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.
1.2 average views per post against 1,232 subscribers — an engagement rate of 0.097%. 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 | 24 |
| Mature posts only | 0.103% over 15 posts read at least 24h after publication |
| Subscribers | 1,232 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.491th percentile · 1/200 the cohort median |
| Uncertainty | ±0.234% 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, 21:35 | 1,232 | no change |
| 12 Aug 2026, 07:02 | 1,232 | first reading |
20 posts held, back to 8 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 (8 August 2026 – 12 August 2026) |
| Views total | 24 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 07:02 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.
Администратор магазина (Златоуст, Северо-Запад 1-й, 3) 💰 50 100 – 64 600 ₽ 📍 Город: Златоуст 🏢 Формат: 📑 Занятость: Полная 📅 График: 📌 Обязанности: • Организация работы магазина и сотрудников. Выполнение плана по товарообороту, минимизация потерь. Взаимодействие с проверяющими органами. Ведение отчетности и анализ плановых... 🎯 Требования: • Образование не ниже среднего профессионального или среднего общего (11 кла…
Администратор магазина ТЦ "Тарелка" 💰 51 500 – 51 500 ₽ 📍 Город: Златоуст 🏢 Формат: На месте работодателя 📑 Занятость: Полная 📅 График: Другое 📌 Обязанности: • Управление командой: распределение обязанностей, контроль исполнения задач, подбор, адаптация, мотивация и развитие персонала. Достижение поставленных планов по продажам и ключевых... 🎯 Требования: • Уверенный пользователь ПК, знание кассовой дисциплины. Хор…
❗❗ Срочно - Добровольцы на контракт с МО РФ - Самые высокие выплаты + льготы от государства❗❗ ТОЛЬКО МУЖЧИНЫ! Не комиссованные, не офицеры. Не занимаемся переводом в другие части!! ❗️Берем на оператора БПЛА / водителей гуманитарки / артиллерия - Проезд БЕСПЛАТНО из любого города! - Официальный контракт с Минобороны РФ - После подписания контракта 2 500 000. (от МО РФ - 400 000р., плюс 2 100 000р. региональные).…
Заместитель директора магазина Златоуст, пр. Гагарина 1-я лин , проспект 18 💰 40 000 – 60 000 ₽ 📍 Город: Златоуст 🏢 Формат: На месте работодателя 📑 Занятость: Полная 📅 График: 2/2 📌 Обязанности: • Организовывать торговый процесс в магазине. Осуществлять прием товара. Производить заказ товаров в магазин. Контролировать товародвижение в магазине. Работать с кассовой... 🎯 Требования: • Уверенный пользователь ПК (Word,…
Специалист по продажам 💰 От 95 000 ₽ 📍 Город: Златоуст 🏢 Формат: На месте работодателя 📑 Занятость: Полная 📅 График: 5/2 📌 Обязанности: • Поиск и проведение переговоров с клиентами и потенциальными партнерами, представителями гос. структур. Подготовка и участие в презентациях по экспортным продуктам. 🎯 Требования: • Образование: высшее профессиональное (менеджмент, техническое). Навык: Навык владения пакетом Micros…
Ведущий инженер (куратор - строительное управление) 💰 От 95 000 ₽ 📍 Город: Златоуст 🏢 Формат: На месте работодателя 📑 Занятость: Полная 📅 График: 5/2 📌 Обязанности: • Осуществлять контроль за качеством строительства объектов, а именно: Проверка наличия документов, подтверждающих качество применяемых материалов ресурсов (сертификаты, технические паспорта, лабораторные... 🎯 Требования: • Высшее техническое или строит…
Ученик слесаря на завод 💰 126 000 – 152 000 ₽ 📍 Город: Златоуст 🏢 Формат: На месте работодателя 📑 Занятость: Вахта 📅 График: 6/1 🎯 Требования: • На автомобильный завод требуются рабочие на сборку агрегатов и узлов на конвейерной линии. Опыт не нужен — всему обучаем на месте. Контакты: https://hh.ru/vacancy/135167202 Горячие вакансии 🔥 👇 https://vk.ru/@rabota_i_karyera-goryachie-vakansii
Помощник машиниста буровой установки (УРБ - 4Т) 💰 От 150 000 ₽ 📍 Город: Златоуст 🏢 Формат: На месте работодателя 📑 Занятость: Вахта 📅 График: 6/1 📌 Обязанности: • Ведение работ технологического процесса бурения. 🎯 Требования: • Документы, подтверждающие квалификацию (удостоверение помощника машиниста БУ, либо машиниста БУ). Опыт работы. Контакты: https://hh.ru/vacancy/136101249 Горячие вакансии 🔥 👇 https://vk.ru/@…
Администратор магазина, г. Златоуст 💰 49 500 – 65 500 ₽ 📍 Город: Златоуст 🏢 Формат: На месте работодателя 📑 Занятость: Полная 📅 График: 2/2 📌 Обязанности: • Организовывать работу грузчиков и продавцов-кассиров. Замещать заведующего магазином на время его отсутствия. Аккуратно выкладывать товар и актуализировать ценники. 🎯 Требования: • При себе необходимо иметь паспорт, трудовую книжку. Контакты: https://hh.ru/vac…
Заведующий магазином (Златоуст) 💰 63 500 – 103 500 ₽ 📍 Город: Златоуст 🏢 Формат: На месте работодателя 📑 Занятость: Полная 📅 График: 5/2 📌 Обязанности: • Организация и поддержание эффективной работы магазина на всех уровнях. Управление командой сотрудников магазина и контроль за их работой. 🎯 Требования: • Опыт работы от 6 месяцев в розничной торговле на позициях директор (управляющий) магазина, руководитель торгов…
🔥Су-шеф (от 4300 руб/смена) 🔥Администратор (от 3700 руб./смена) 🔥Старший повар (от 60 000 руб./месяц) 🔥Повар (от 50 000 руб./месяц) 🔥Курьер на л/а (от 3500 руб/смена) Заработанная плата без задержек два раза в месяц, сменный график работы 2/2, обучение профессии, работа в дружном коллективе, скидки на продукцию. 📲Оставь отклик любым удобным способом: ✔Заполни анкету по ссылке vk.cc/co91q7 ✔Напиши рекрутеру vk.com/r…
Менеджер по продажам 💰 От 60 000 ₽ 📍 Город: Златоуст 🏢 Формат: На месте работодателя 📑 Занятость: Полная 📅 График: 5/2 📌 Обязанности: • Работа с существующей базой клиентов, развитие клиентов. Поиск и привлечение новых клиентов. Проведение встреч и переговоров с клиентами. 🎯 Требования: • Опыт работы в любых продажах приветствуется. Уверенный пользователь ПК. Умение находить общий язык с людьми. Желание учиться нов…
Showing the 12 most recent of 20 posts we hold for @Rabota_v_Zlatouste_1. 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.
“Вакансии в Златоусте” (@Rabota_v_Zlatouste_1), 1,232 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Rabota_v_Zlatouste_1.
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.