Telegram RegisterThe public register of Telegram
Telegram profile photo for Вакансии в Новотроицке

Channel

Вакансии в Новотроицке

@rabota_Novotroitsx

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Advertising · Posts · Citations · Cite this entry

10,404subscribers

-24 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001177104092
TypeChannel
Username@rabota_Novotroitsx
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/rabota_Novotroitsx

Topic

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 10 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.

Observations

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.

Views per post sit far below this size band

3.0 average views per post against 10,404 subscribers — an engagement rate of 0.029%. Across the 24,006 registered channels in the same cohort — 10,000–31,620 subscribers, posting mainly in Russian — the middle half sit between 5.52% and 23.2%, with a median of 11.6%.

What this was computed from
Window30 days (17 July 2026 16 August 2026)
Posts measured102 of 102 published in the window (102 exact, 0 rounded by Telegram)
Views totalled304
Mature posts only0.032% over 80 posts read at least 24h after publication
Subscribers10,404 measured 16 August 2026
Cohortb10000:rus · 24,006 channels · p10 2.56% · p25 5.52% · p50 11.6% · p75 23.2% · p90 41.4%
Position in cohort0.400th percentile · 1/500 the cohort median
Uncertainty±0.277% of the figure, from Telegram’s rounding
Post languageRussian · 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 16 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.

Growth

10,40410,42810,4167 August 2026 — 10,428 subscribers8 August 2026 — 10,423 subscribers9 August 2026 — 10,420 subscribers10 August 2026 — 10,417 subscribers11 August 2026 — 10,415 subscribers12 August 2026 — 10,412 subscribers13 August 2026 — 10,411 subscribers14 August 2026 — 10,408 subscribers16 August 2026 — 10,404 subscribers7 August 202616 August 2026
9 measurements spanning 9 days, net -24. 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 10,400–10,432 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 15:1310,404-4
14 Aug 2026, 23:4310,408-3
13 Aug 2026, 14:3710,411-1
12 Aug 2026, 11:0910,412-3
11 Aug 2026, 14:1510,415-2
10 Aug 2026, 11:0110,417-3
9 Aug 2026, 09:5310,420-3
8 Aug 2026, 08:3810,423-5
7 Aug 2026, 12:1510,428first reading

Engagement

102 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.029%
avg views ÷ 10,404 subscribers
Avg views / post
3.0
102 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
102
of 102 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
WindowRolling 30 days · latest post in window 15 August 2026
Posts held102 (5 August 202615 August 2026)
Views total304
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 18:44 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

Video runtime
10s
Average length
5s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Advertising

Ad load
2.94%
3 of 102 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 2 distinct tokens
Median views · ads
3.0
over 3 measured posts
Median views · rest
3.0
over 99 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd726 August 202611 August 2026
5jtCeReNwxHpfQTDve31wmc17 August 20267 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 102 most recent posts we hold, published 5 August 2026 to 15 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

15 Aug 2026, 14:19 UTC1 viewsread 15 August 2026

Менеджер маркетплейсов 80000 ₽ Обязанности: • Ведение одного из направлений в кабинете Озон (создание и заполнение карточек, работа с фотоконтентом, комплексное продвижение, ценообразование и т.д.) • Полное ведение кабинета на Яндекс Маркет (создание и заполнение карточек, работа с фотоконтентом, комплексное продвижение, ценообразование и т.д.) • Заполнение введённой отчетности • Организация и контроль поставок • Ко

15 Aug 2026, 13:03 UTC1 viewsread 15 August 2026

Электромонтажник 250000 ₽ Обязанности: • Монтаж кабеленесущих конструкций • Протяжка и укладка силовых кабельных линий • Монтаж и подключение электрооборудования • Расключение силового и щитового оборудования • Монтаж концевых и соединительных муфт • Выполнение электромонтажных работ согласно проектной документации Требования: • Опыт электромонтажных работ • Умение работать с электроинструментом • Понимание техноло

15 Aug 2026, 11:45 UTC2 viewsread 15 August 2026

Оператор call-центра 37000 ₽ Обязанности: • Принимать входящие звонки или совершать исходящие • Оказывать консультационные услуги и помогать клиентам ориентироваться в услугах наших партнеров Требования: • Грамотная речь • Знание ПК на уровне пользователя Мы предлагаем: • Управляемый доход , полностью зависящий от твоего графика и желания развиваться (гарантированный оклад + премия) • Выплаты два раза в месяц • Вы

15 Aug 2026, 10:25 UTC2 viewsread 15 August 2026

Личный ассистент руководителя 60000 ₽ Обязанности: • Поиск и анализ информации • Отчетность по работе мастеров, введение документов клиентов • Консультации клиентов в чатах и по телефону • Координация задач и сотрудников • Работа и консультация в соц сетях • Быть на связи с 08:30 и 21:30 оперативно реагировать на мои задачи и вопросы • Оперативно отвечать клиентам Требования: • Умение работать в программах Мастерс

15 Aug 2026, 09:10 UTC1 viewsread 15 August 2026
Photo

Приглашаем на службу по контракту граждан РФ (из любых регионов) и иностранных государств. Финансовые условия: Москва: 2 300 000 ₽ — разово | от 260 000 ₽/мес. Кострома: 1 400 000 ₽ — разово | от 210 000 ₽/мес. Мы берем на себя: Полную компенсацию проезда (авиа/ж/д) Бесплатное проживание и питание Полное сопровождение на всех этапах Качественную подготовку на полигоне Заключение контракта от 1 года Кто может по

15 Aug 2026, 08:01 UTC1 viewsread 15 August 2026

Сборщик на авиалинию Зарплата по договоренности. Обязанности: • Выполнять сборочные работы на конвейере — монтировать и соединять компоненты авиатехники в соответствии с технической документацией и стандартами качества • Контролировать точность установки деталей, проверять надёжность креплений и соответствие параметров заданным требованиям • Следить за соблюдением технологических процессов и нормативов на каждом эта

15 Aug 2026, 06:39 UTC1 viewsread 15 August 2026

Сварщик на полуавтомат Зарплата по договоренности. Обязанности: • Сборка металлических ограждений и металлоконструкций по чертежам. • Поддержание чистоты и порядка на рабочем месте. • Контроль качества выполняемой работы. Требования: • Чтение чертежей (приветствуется) • Опыт работы с металлоизделиями • Ответственность, высокая работоспособность • Желание работать и зарабатывать • Уметь пользоваться электроинструмен

15 Aug 2026, 05:17 UTC2 viewsread 15 August 2026

Менеджер по продажам 50000 ₽ Обязанности: • Обзвон салонов красоты • Общение с салонами в соц. сетях • Работа по скрипту • Сопровождение салона до полной регистрации в нашем приложении • Заполнение отчётности о проделанной работе Требования: • Умение общаться и выстраивать диалог • Нужно созваниваться, списываться или приходить в салоны и помогать им зарегестрироваться в нашем приложении Мы предлагаем: • Оплата тр

15 Aug 2026, 04:03 UTC1 viewsread 15 August 2026

Помощник повара 45/45,60/60 Север 178000 ₽ Обязанности: • Обработка овощей (мытьё, чистка) • Нарезка овощей, создание заготовок Требования: • Опыт работы вахтовым методом ( приветствуется) Мы предлагаем: • Зарплата без задержек два раза в месяц! • Заранее покупаем билеты на самолёт туда и обратно! • Сразу оплачиваем Мед. комиссию! • Бесплатное проживание в общежитии, питание, спецодежда! • Возможен карьерный рост

14 Aug 2026, 15:43 UTC2 viewsread 15 August 2026

Продавец-консультант 40000 ₽ Обязанности: • Следить за порядком в зале • Отпаривать товар • Консультировать покупателей • Работать за кассой Требования: • Аккуратность • Желание работать • Энтузиазм Мы предлагаем: • График работы: Полный день Контакты: +79033677802 [email protected]

14 Aug 2026, 14:22 UTC3 viewsread 15 August 2026

Мерчандайзер 50000 ₽ Обязанности: • Принимать и разгружать машину с товаром 1-2 раза в неделю • Аккуратно выкладывать товар и актуализировать ценники • Следить за порядком в магазине, проверять сроки годности товаров • Быть открытым, приветливым и готовым помочь каждому покупателю Требования: • Ценят порядок • Относятся к задачам с ответственностью • Готовы помогать другим • Опыт работы не требуется, но будет плюсо

14 Aug 2026, 13:05 UTC2 viewsread 15 August 2026

Менеджер по работе с клиентами Зарплата по договоренности. Обязанности: • Поиск клиентов • Помощь в регистрации в системе • Консультация клиентов по продуктам компании (косметика, парфюмерия, бытовая химия) Требования: • Коммуникабельность • Нацеленность на результат • Желание зарабатывать Мы предлагаем: • Удаленный формат работы • График работы: свободный • Покупки по ценам склада (от 20%) Контакты: +79386992940

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

Citation-graph rank — 1,091,005 of 1,481,243entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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 August 2026 — this entry's latest reading, not the date you are reading this.

“Вакансии в Новотроицке” (@rabota_Novotroitsx), 10,404 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/rabota_Novotroitsx.

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.