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

Channel

Вакансии в Орске

@v_orske_rabota

2 usernames

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

9,438subscribers

-91 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-1001379920820
TypeChannel
Usernames@rabota_orskb @v_orske_rabota
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 live19 September 2026
Measurements held19
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/v_orske_rabota

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 1 other registered channel. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@rabota_orskb/78295 Aug 2026, 15:29 UTC@rabota_orskn/78666 Aug 2026, 07:55 UTC1.0016 hours
@rabota_orskb/78316 Aug 2026, 04:04 UTC@rabota_orskn/78636 Aug 2026, 04:04 UTC1.00under a minute
@rabota_orskb/78326 Aug 2026, 05:17 UTC@rabota_orskn/78646 Aug 2026, 05:17 UTC1.00under a minute
@rabota_orskb/78336 Aug 2026, 06:36 UTC@rabota_orskn/78656 Aug 2026, 06:36 UTC1.00under a minute
@rabota_orskn/78787 Aug 2026, 09:07 UTC@rabota_orskb/78487 Aug 2026, 11:43 UTC1.002.6 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@rabota_orskn5 (5/5 hand-verifiable sample passed)1.0077 minutes@rabota_orskn (41)

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. 4 of the 4 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 23 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 2, the earliest publisher we hold is @rabota_orskb — which is this entry. 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 1 other registered channel, 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

29,5294,765.57 August 2026 — 9,529 subscribers7 August 2026 — 9,529 subscribers7 August 2026 — 9,528 subscribers11 August 2026 — 9,517 subscribers14 August 2026 — 9,511 subscribers17 August 2026 — 2 subscribers25 August 2026 — 4 subscribers26 August 2026 — 9,488 subscribers26 August 2026 — 9,488 subscribers27 August 2026 — 9,487 subscribers29 August 2026 — 9,479 subscribers31 August 2026 — 5 subscribers1 September 2026 — 9,474 subscribers5 September 2026 — 9,464 subscribers9 September 2026 — 10 subscribers10 September 2026 — 9,454 subscribers14 September 2026 — 9,448 subscribers18 September 2026 — 15 subscribers19 September 2026 — 9,438 subscribers9,4387 August 202619 September 2026
19 measurements spanning 43 days, net -91. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 11:219,438+9,423
18 Sept 2026, 15:5815-9,433
14 Sept 2026, 15:189,448-6
10 Sept 2026, 23:579,454+9,444
9 Sept 2026, 23:1910-9,454
5 Sept 2026, 20:179,464-10
1 Sept 2026, 08:179,474+9,469
31 Aug 2026, 21:255-9,474
29 Aug 2026, 17:429,479-8
27 Aug 2026, 00:249,487-1
26 Aug 2026, 11:429,488no change
26 Aug 2026, 11:309,488+9,484
25 Aug 2026, 03:084+2
17 Aug 2026, 10:552-9,509
14 Aug 2026, 01:439,511-6
11 Aug 2026, 04:379,517-11
7 Aug 2026, 22:359,528-1
7 Aug 2026, 12:319,529no change
7 Aug 2026, 12:209,529first reading

Engagement

119 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 18 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
23.3%
avg views ÷ 9,438 subscribers
Avg views / post
2,190
46 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
46
of 119 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 29 August 2026
Posts held119 (5 August 202629 August 2026)
Views total100,946
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 06: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.

What this channel posts

Video runtime
20s
Average length
5s

Measured directly from 4 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
5.04%
6 of 119 posts carry an ad marker
Regulatory tokens
6
posts carrying an erid · 2 distinct tokens
Median views · ads
9.0
over 6 measured posts
Median views · rest
8.0
over 113 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. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd746 August 202627 August 2026
5jtCeReNwxHpfQTDve31wmc27 August 202626 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 119 most recent posts we hold, published 5 August 2026 to 29 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

29 Aug 2026, 05:19 UTC45 viewsread 29 August 2026

Лицензированный охранник грузов 180000 ₽ Обязанности: • Сопровождение грузов по территории РФ со служебным оружием Требования: • Наличие действующего УЧО 6 разряда • Наличие действующих справок 002 Оу, 003 Оу, 002 ЧОу (полученных по месту регистрации) • Периодическая проверка желательно Мы предлагаем: • Оплата всех командировочных расходов (проезд, проживание) Контакты: +79014777440 [email protected]

29 Aug 2026, 04:02 UTC131 viewsread 29 August 2026

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

28 Aug 2026, 15:22 UTC≈1,160 viewsread 29 August 2026

Охранник ГБР (вахта) 115000 ₽ Обязанности: • Оперативный выезд на объекты при срабатывании сигнализации • Оценка ситуации на месте, предотвращение противоправных действий • Взаимодействие с сотрудниками полиции и экстренных служб при необходимости • Оформление отчета по итогам реагирования • Поддержание готовности экипировки и служебного автомобиля Требования: • Ответственность, стрессоустойчивость, умение быстро п

28 Aug 2026, 14:09 UTC≈1,360 viewsread 29 August 2026

Начальник отдела 74000 ₽ Обязанности: • Осуществляет контроль: – безопасной эксплуатации средств ЭХЗ (в том числе вспомогательного оборудования и устройств для обеспечения защиты от коррозии) сети газораспределения и газопотребления на объектах филиала с учетом требований ПБ; – выполнения филиалом требований предписаний органов государственного контроля (надзора) в части соблюдения государственных требований ПБ; – о

28 Aug 2026, 12:50 UTC≈1,620 viewsread 29 August 2026

Слесарь по эксплуатации и ремонту подземных газопроводов 40000 ₽ Обязанности: • Выполнение технического обслуживания сети газораспределения и газопотребления Бузулукского района. Требования: • Наличие профессионального обучения(при отсутствии - обучим бесплатно в своем УМЦ) • Дисциплинированность • Ответственность • Коммуникационный навыки Мы предлагаем: • Обучим бесплатно в своем УМЦ • График работы: понедельник

28 Aug 2026, 11:31 UTC≈1,990 viewsread 29 August 2026

Менеджер по продажам Зарплата по договоренности. Обязанности: • Ведение интернет-магазина • Работа с клиентами • Консультирование Требования: • Опыт в продажах не менее года • Коммуникабельность • Ответственность • Профессиональное образование по направлению "менеджмент" будет преимуществом Мы предлагаем: • Гибкий график работы от 4-х часов в день • Премирование • Бесплатное обучение • Возможность карьерного роста

28 Aug 2026, 10:17 UTC≈2,250 viewsread 29 August 2026

Слесарь-сантехник Зарплата по договоренности. Обязанности: • Обеспечивать исправное состояние, безаварийную и надежную работу обслуживаемых систем центрального отопления, водоснабжения, канализации и водостоков, правильную их эксплуатацию, своевременный качественный ремонт и др. Требования: • Среднее специальное образование • Стаж работы не менее 2 лет Мы предлагаем: • Официальное трудоустройство • Сменный график

28 Aug 2026, 08:58 UTC≈2,470 viewsread 29 August 2026
Photo

Стань контрактником МО РФ | Полный пакет обеспечения Ищешь надежные условия? Набираем граждан РФ (любой регион) и иностранных граждан на контракт от 1 года. • МОСКВА: 2 300 000 ₽ сразу + от 260 000 ₽ ежемесячно Что мы предоставляем: Оплата проезда (авиа/ж/д) из твоего города Бесплатное проживание и питание Обучение на полигоне Встреча и сопровождение по всем вопросам Кому подойдет: Возраст от 18 до 60 лет. Берем

28 Aug 2026, 07:48 UTC≈2,680 viewsread 29 August 2026

Уборщик производственных и служебных помещений 80000 ₽ Обязанности: • Bлaжнaя уборка общежитий, cлужебныx и произвoдствeнных помещений, вагон-городков • Cбop муcoра • Поддержaние чиcтоты вo вcех помещениях Требования: • Ответствeннoе oтношeние к рабoчeму пpoцeсcу, aккуpатнocть Мы предлагаем: • Рaбoтa ваxтовым мeтoдом 45/45; 60/60 • Компенсация медосмотра • Компенсация питания ( выплачивается в зарплату) • Оплачива

28 Aug 2026, 06:33 UTC≈2,800 viewsread 29 August 2026

Су шеф на Чукотку (60/60) 330000 ₽ Обязанности: • Коoрдинирoваниe, oрганизaция пpaвильнoй pаботы повapов и куxoнных pабoтникoв • Koнтpoль сoблюдения сaнитaрныx норм • Управление запасами • Составление различных меню Требования: • Опыт работы в должности не менее 1 года • Опыт руководства коллективом • Умение работать по ТТК Мы предлагаем: • Официальное трудоустройство согласно ТК РФ • Питание, проживание, проезд и

28 Aug 2026, 05:17 UTC≈2,880 viewsread 29 August 2026

Вакансия из города Новотроицк Лицензированный охранник 180000 ₽ Обязанности: • Сопровождение грузов по территории РФ со служебным оружием Требования: • Наличие действующего УЧО 6 разряда • Наличие действующих справок 002 Оу, 003 Оу, 002 ЧОу (полученных по месту регистрации) • Периодическая проверка желательно Мы предлагаем: • Оплата всех командировочных расходов (проезд, проживание) Контакты: +79014777440 916381

28 Aug 2026, 04:02 UTC≈2,890 viewsread 29 August 2026

Вакансия из города Новотроицк Оператор колл-центра (удаленно) 180 - 200 ₽ Обязанности: • Звонить по готовой базе и проводить короткие опросы • Вносить ответы в простую форму • Общаться вежливо и доброжелательно Требования: • Стабильный интернет • Компьютер или ноутбук • Гарнитура • Грамотная, чёткая речь Мы предлагаем: • Официальное трудоустройство • Опыт работы не требуется — всему обучим • Свободный график: мож

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Бизнес идеи 2026
@topbizidei · 35,906
Telegram ranks this channel #17 of 42 here — alongside 41 others — read 1 September 2026
Работа в Краснодаре
@vakansii_krasnodarx · 49,336
Telegram ranks this channel #27 of 87 here — alongside 86 others — read 26 August 2026
Вакансии в Ростове-на-Дону
@na_donu_rostov_vakansiy · 46,252
Telegram ranks this channel #66 of 95 here — alongside 94 others — read 27 August 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Вакансии в Орске” (@v_orske_rabota), 9,438 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/v_orske_rabota.

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.