Telegram RegisterThe public register of Telegram
Telegram profile photo for Вакансии в Тавде

Channel

Вакансии в Тавде

@rabota_tavdaq

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

5,835subscribers

-6 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001443285375
TypeChannel
Username@rabota_tavdaq
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/rabota_tavdaq

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

Growth

5,8335,8425,837.57 August 2026 — 5,841 subscribers7 August 2026 — 5,841 subscribers8 August 2026 — 5,842 subscribers11 August 2026 — 5,840 subscribers14 August 2026 — 5,838 subscribers17 August 2026 — 5,835 subscribers21 August 2026 — 5,834 subscribers27 August 2026 — 5,833 subscribers30 August 2026 — 5,835 subscribers3 September 2026 — 5,836 subscribers8 September 2026 — 5,833 subscribers16 September 2026 — 5,835 subscribers5,8357 August 202616 September 2026
12 measurements spanning 40 days, net -6. 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 5,832–5,843 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 21:225,835+2
8 Sept 2026, 19:405,833-3
3 Sept 2026, 11:365,836+1
30 Aug 2026, 22:465,835+2
27 Aug 2026, 20:135,833-1
21 Aug 2026, 03:535,834-1
17 Aug 2026, 17:265,835-3
14 Aug 2026, 21:275,838-2
11 Aug 2026, 06:435,840-2
8 Aug 2026, 09:405,842+1
7 Aug 2026, 13:025,841no change
7 Aug 2026, 12:555,841first reading

Engagement

64 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 8 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 64 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.

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
4.69%
3 of 64 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 2 distinct tokens
Median views · ads
1.0
over 3 measured posts
Median views · rest
1.0
over 61 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 64 most recent posts we hold, published 5 August 2026 to 11 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

11 Aug 2026, 18:25 UTC1 viewsread 12 August 2026
Advertisementerid CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd7Video

💛 Подработка курьером в вашем городе — доставка заказов Яндекс Еды и Яндекс Лавки Набор ведёт официальный партнёр сервиса. Условия: 📍 доход до 8 500 ₽ в день, выплаты каждый день (оформление как самозанятый) 📍 график выбираете сами — слоты свободные, заказы поступают 24/7 📍 все чаевые — ваши 📍 из документов — требуется только удостоверение личности + смартфон Бонусы для курьеров сейчас: 😍 велосипед Яндекс Байк — з

11 Aug 2026, 14:24 UTC1 viewsread 12 August 2026

Автослесарь-автомеханик 180000 ₽ Обязанности: • Ремонт легковых автомобилей • Диагностика неисправности • Проведение планового ТО • Ремонт ходовой части • Простой ремонт агрегатов, (можно и сложный) • Шиномонтаж • Простая электрика Требования: • Опыт работы с автомобилями преимущественно иностранного производства • Опыт работы в дилерском центре приветствуется • Знание регламента ТО и особенностей ремонта • Высокое

11 Aug 2026, 13:10 UTC1 viewsread 12 August 2026

Маркетолог в онлайн-школу 200000 ₽ Обязанности: • Разработка маркетинговой стратегии • Построение холодных и прогревочных воронок. (лендинги, воронки писем, бесплатники и пр.) • Работа с холодной аудиторией и базой клиентов • Ассортиментная матрица продуктов • Лидогенерация • Медиапланирование • Работа с брендом • Постановка задач команде: Трафик, копирайт, дизайн, тех специалист. • Контроль, результат Требования:

11 Aug 2026, 11:53 UTC1 viewsread 12 August 2026

Парикмахер-универсал 70000 ₽ Обязанности: • Стрижки мужские, женские, окрашивание, хим. Завивка , итд Требования: • Пунктуальность • Ответственность • Знание своего дела • Желание работать! Мы предлагаем: • 50/50 стрижки • Окрашивание 60/40 без вычета материалов • Гарантированный выход 2000 • График 2/2, с 10.00 до 20.00 Контакты: +79223777880 [email protected]

11 Aug 2026, 10:35 UTC1 viewsread 12 August 2026

Менеджер по продажам Битрикс24 200000 ₽ Обязанности: • Работать по нашей базе клиентов и с входящими заявками, прошедшими квалификацию • Заниматься поиском и привлечением клиентов • Вести коммуникации с клиентами через Битрикс24 • Выходить на первые лица компании (ЛПР), выявлять точки роста в бизнесе клиента. Исходя из этого презентовать Битрикс24 и работать с возражениями • Проводить онлайн-встречи с клиентами • Ра

11 Aug 2026, 09:16 UTC1 viewsread 12 August 2026
Photo

🛑ПУНКТ ОТБОРА НА ВОЕННУЮ СЛУЖБУ ПО КОНТРАКТУ Министерства Обороны РФ ✅МОСКВА 💰ЕДИНОВРЕМЕННАЯ ВЫПЛАТА : 2️.3️0️0️.0️0️0️₽💰 Ежемесячные: Министерство Обороны РФ от 2️6️0️.0️0️0️₽ ✅КОСТРОМА 💰ЕДИНОВРЕМЕННАЯ ВЫПЛАТА: 1️.4️0️0️.0️0️0️₽-Ежемесячные Министерства Обороны РФ от 2️1️0️.0️0️0️₽ 🇷🇺Принимаются граждане РФ (прописка в любом регионе) и других СТРАН 📌Условия: ✅Оплачиваем Вам проезд ( авиа, ж/д ) ✅Оплачиваем Вам пр

11 Aug 2026, 09:08 UTC1 viewsread 12 August 2026

Менеджер по продажам Зарплата по договоренности. Обязанности: • Работа с текущей клиентской базой (активные звонки, встречи и переговоры с ЛПР и ТОП-руководителями, выявление актуальных задач), расширение и активация клиентской базы • Полное самостоятельное сопровождение клиента от первого касания до закрытия сделки (проведение переговоров, заключение договора, контроль поставки товара) • Продажа и реализация сложны

11 Aug 2026, 07:49 UTC1 viewsread 12 August 2026

Вакансия из города Тюмень Инженер Заработная плата по договоренности Обязанности: • Работа с серверами и рабочими местами на базе Windows и Linux. • Взаимодействие со службами каталогов и сетевыми сервисами (AD, GPO, DNS, DHCP). • Работа с сетевым оборудованием, серверной инфраструктурой и системами виртуализации. • Работа со скриптами. Использование в работе PowerShell. • Участие в модернизации оборудования (сбор

11 Aug 2026, 06:30 UTC1 viewsread 12 August 2026

Вакансия из города Тюмень Повар в столовую 280 000 ₽ Обязанности: • Организация, приготовление и выдача блюд в соответствии с утверждённым меню (завтраки, обеды, ужины) • Контроль соблюдения санитарных норм и правил гигиены на производстве • Руководство и координация работы помощников повара и кухонных работников • Обслуживание на линии раздачи: выкладка готовых блюд, обеспечение наличия ассортимента, вежливое взаи

11 Aug 2026, 05:13 UTC1 viewsread 12 August 2026

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

11 Aug 2026, 04:00 UTC1 viewsread 12 August 2026

Вакансия из города Тюмень Пекарь/Пекарь-кондитер на вахту (Север) 170 000 ₽ - 210 000 ₽ Обязанности: • Подготовка сырья • Формирование и выпекания изделий • Контроль процесса брожения теста • Выпечка хлеба, булочек, блинов, оладий • Приготовление несложных кондитерских изделий • Контроль качества продукции Требования: • Имеете опыт работы на кухне • Готовы работать вахтовым методом • Ответственны и исполнительны

10 Aug 2026, 14:46 UTC2 viewsread 12 August 2026

Вакансия из города Тюмень Повар-универсал 100000 ₽ Обязанности: • Приготовление блюд согласно ТТК (основной акцент: японская кухня, закуски, горячие блюда) • Соблюдение стандартов санитарии и чистоты (СанПиН) • Участие в жизни кухни: обновление меню Требования: • Знаете базу • Имеете медкнижку • Понимаете важность "санитарного минимума" • Честность • Пунктуальность • Адекватность • Умеете сохранять позитивный наст

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

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.

Mentions

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.

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

“Вакансии в Тавде” (@rabota_tavdaq), 5,835 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/rabota_tavdaq.

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.