Telegram RegisterThe public register of Telegram

Channel

Вакансии в Йошкар-Оле

@yoshkar_ola_rabotac

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Advertising · Posts · Cite this entry

12,431subscribers

-14 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-1001498218442
TypeChannel
Username@yoshkar_ola_rabotac
DescriptionОпубликовать вакансию или рекламу: @global_man (Среднее время ответа 2 минуты)
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/yoshkar_ola_rabotac

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.

Content that also appears on other registered channels

Posts published here appear word for word on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@yoshkar_ola_rabotac/8488 · this entry5 Aug 2026, 15:22 UTC@yoshkar_ola_rabotaz/81695 Aug 2026, 15:22 UTC1.00under a minute
@yoshkar_ola_rabotac/8489 · this entry5 Aug 2026, 16:35 UTC@yoshkar_ola_rabotaz/81705 Aug 2026, 16:35 UTC1.00under a minute
@yoshkar_ola_rabotac/8492 · this entry6 Aug 2026, 07:24 UTC@yoshkar_ola_rabotaz/81736 Aug 2026, 07:24 UTC1.00under a minute
@yoshkar_ola_rabotaz/81786 Aug 2026, 12:57 UTC@yoshkar_ola_rabotac/8498 · this entry6 Aug 2026, 14:11 UTC1.0074 minutes
@yoshkar_ola_rabotaz/81847 Aug 2026, 08:44 UTC@yoshkar_ola_rabotac/8506 · this entry7 Aug 2026, 11:36 UTC1.002.9 hours
@yoshkar_ola_rabotaz/81867 Aug 2026, 10:18 UTC@yoshkar_ola_rabotac/8509 · this entry7 Aug 2026, 15:23 UTC1.005.1 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@yoshkar_ola_rabotaz6 (6/6 hand-verifiable sample passed)1.0076 minutes@yoshkar_ola_rabotaz (60)
@yoshkar_ola_rabotax6 (6/6 hand-verifiable sample passed)1.0073 minutes@yoshkar_ola_rabotax (42)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 7 of the 10 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 25 comparable posts for this entry, running 5 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 3, the earliest publisher we hold is @yoshkar_ola_rabotaz. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 8 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

12,43112,44512,4387 August 2026 — 12,445 subscribers7 August 2026 — 12,445 subscribers9 August 2026 — 12,438 subscribers10 August 2026 — 12,436 subscribers10 August 2026 — 12,435 subscribers11 August 2026 — 12,431 subscribers7 August 202611 August 2026
6 measurements spanning 4 days, net -14. 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 12,429–12,447 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 22:4712,431-4
10 Aug 2026, 21:0612,435-1
10 Aug 2026, 00:0312,436-2
9 Aug 2026, 01:1012,438-7
7 Aug 2026, 22:3312,445no change
7 Aug 2026, 12:1612,445first reading

Engagement

73 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 15 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.192%
avg views ÷ 12,431 subscribers
Avg views / post
23.8
72 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
73
of 73 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 12 August 2026
Posts held73 (5 August 202612 August 2026)
Views total1,715
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 12:27 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
987
Videos
11
Links
6,360

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

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

12 Aug 2026, 11:39 UTC5 viewsread 12 August 2026

Менеджер по недвижимости 180000 ₽ Обязанности: • Осуществлять поиск локаций для объектов в соответствии с требованиями CVP форматов в достаточном количестве для выполнения плана развития Компании • Проводить переговоры с Арендодателями по условиям Договора аренды, отстаивать интересы Компании • Согласовывать с Арендодателями и Арендатором условия Договора аренды • Получать документы от собственника, необходимые для

12 Aug 2026, 10:20 UTC8 viewsread 12 August 2026

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

12 Aug 2026, 09:04 UTC8 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️₽ 🇷🇺Принимаются граждане РФ (прописка в любом регионе) и других СТРАН 📌Условия: ✅Оплачиваем Вам проезд ( авиа, ж/д ) ✅Оплачиваем Вам пр

12 Aug 2026, 08:45 UTC10 viewsread 12 August 2026

Повар 4 разряда (вахта) 162425 ₽ Обязанности: • Приготовление горячих и холодных блюд по утвержденному меню (салаты, супы, вторые блюда, бульоны, холодные закуски, каши и пр.) • Контроль количества и качества входящего сырья, соблюдение сроков годности и условий хранения • Мойка, бланшировка, смешивание продуктов и компонентов, жарка, запекание, варка на пару, изготовление соусов. • Приготовление блюд в соответствии

12 Aug 2026, 07:25 UTC12 viewsread 12 August 2026

Техник-универсал Зарплата по договоренности. Обязанности: • Требуется техник-универсал в Арбитражный суд • Оказание всевозможных услуг на территории суда Требования: • Ответственность • Внимательность Мы предлагаем: • Официальное трудоустройство • Соц.пакет Контакты: +79093685581 house24a@mail.ru

12 Aug 2026, 06:06 UTC13 viewsread 12 August 2026

Водитель категории Е Зарплата по договоренности. Обязанности: • Перевозка грузов • Контроль за состоянием автомобиля. содержание автомобиля в чистоте • Осуществление мелкого ремонта Требования: • Опыт работы от 5 лет • Ответственность • Пунктуальность • Безаварийное вождение • Наличие прав категории Е Мы предлагаем: • График работы по договоренности • Официальное трудоустройство • Заработная плата по договоренност

11 Aug 2026, 17:50 UTC21 viewsread 12 August 2026
Advertisementerid CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd7Video

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

11 Aug 2026, 16:40 UTC20 viewsread 12 August 2026

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

11 Aug 2026, 15:27 UTC17 viewsread 12 August 2026

Повар-Мясник 60/60 (Чукотка) 280000 ₽ Обязанности: • Работа с сырой мясной продукцией. • Поддержание чистоты и порядка на рабочем месте • Соблюдение санитарно-гигиенических норм, технологии приготовления и качества пищи, правил личной гигиены. Мы предлагаем: • Место работы: Чукотский автономный округ, Билибинский район. • Вахтовый метод работы с графиками 60/60 • Заработная плата от 240 000 за вахту 60 дней, выплат

11 Aug 2026, 14:10 UTC21 viewsread 12 August 2026

Программист 1С Зарплата по договоренности. Обязанности: • Участие в анализе требований заказчиков, поиске наиболее эффективных решений • Реализация запросов на изменение конфигурации по ТЗ • Анализ разработанного ранее функционала, внесение предложений по оптимизации, исправление ошибок (поиск проблемы и решения), корректировка данных • Разработка и внедрение нового функционала, а также интеграция с другими системам

11 Aug 2026, 12:55 UTC22 viewsread 12 August 2026

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

11 Aug 2026, 11:37 UTC21 viewsread 12 August 2026

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

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

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

“Вакансии в Йошкар-Оле” (@yoshkar_ola_rabotac), 12,431 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/yoshkar_ola_rabotac.

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.