Telegram RegisterThe public register of Telegram

Channel

Вакансии в ИЖЕВСКЕ

@rabota_izhevsk5

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

8,487subscribers

-2 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-1001448225042
TypeChannel
Username@rabota_izhevsk5
DescriptionПубликация платная @Lizzamg
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 held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/rabota_izhevsk5

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 92% 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 4 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
@rabota_izhevsk5/1248 · this entry26 Jul 2026, 15:03 UTC@Rabota_krasnodar2/408626 Jul 2026, 15:04 UTC1.0072 seconds
@rabota_izhevsk5/1249 · this entry27 Jul 2026, 15:02 UTC@Rabota_krasnodar2/408727 Jul 2026, 15:03 UTC1.002 minutes
@rabota_izhevsk5/1250 · this entry28 Jul 2026, 15:03 UTC@Rabota_krasnodar2/408828 Jul 2026, 15:04 UTC1.00under a minute
@Rabota_krasnodar2/408929 Jul 2026, 06:00 UTC@rabota_izhevsk5/1251 · this entry29 Jul 2026, 06:01 UTC1.00under a minute
@Rabota_krasnodar2/409030 Jul 2026, 06:02 UTC@rabota_izhevsk5/1252 · this entry30 Jul 2026, 06:03 UTC1.00under a minute
@rabota_izhevsk5/1253 · this entry31 Jul 2026, 10:00 UTC@Rabota_krasnodar2/409231 Jul 2026, 10:03 UTC1.004 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@Rabota_krasnodar26 (6/6 hand-verifiable sample passed)1.00under a minutethis entry (42)
@Rabota_Krasnoyarsk26 (6/6 hand-verifiable sample passed)1.002 minutesthis entry (42)
@rabota_UFAs6 (6/6 hand-verifiable sample passed)1.0072 secondsthis entry (42)
@VAKHTAX5 (5/5 hand-verifiable sample passed)1.002 minutesthis entry (32)

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. None of the 8 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 22 May 2026 to 6 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 5, the earliest publisher we hold is @Rabota_krasnodar2. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · clone_source, last confirmed 7 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 4 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

8,4878,4898,4887 August 2026 — 8,489 subscribers7 August 2026 — 8,489 subscribers11 August 2026 — 8,487 subscribers7 August 202611 August 2026
3 measurements spanning 4 days, net -2. 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 8,487–8,489 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 11:338,487-2
7 Aug 2026, 15:008,489no change
7 Aug 2026, 14:518,489first reading

Engagement

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

ERR · 30 days
48.5%
avg views ÷ 8,487 subscribers
Avg views / post
4,120
9 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
9
of 20 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 6 August 2026
Posts held20 (22 May 20266 August 2026)
Views total37,040
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 16:19 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
351
Videos
3
Links
265

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. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

6 Aug 2026, 13:11 UTC≈2,660 viewsread 12 August 2026
Photo

‼️ ПРОЕКТ «СЕВЕРНЫЙ РУБЕЖ» СПЕЦИАЛЬНАЯ ПРОГРАММА ПОДГОТОВКИ РЕЗЕРВНОГО КОРПУСА ✅ от 7000000₽ за год✅ 💠 Участникам программы предоставляется полный пакет обеспечения и сопровождение на всех этапах подготовки. 🎖 Программа включает: 💰 ❗️ Единовременное вознаграждение 4 500 000₽❗️ 📍 Регистрация участников проводится через г. Санкт-Петербург 🔓 Списание долгов до 10 000 000 ₽ — государство полностью закрывает ваши

31 Jul 2026, 10:00 UTC≈5,240 viewsread 12 August 2026
Photo

⚡️Согласно Указу Президента РФ №526 от 27.07.2026г., в связи с созданием в ВС РФ военно-строительных подразделений установить штатную численность военнослужащих в количестве 2 426 130 человек. В связи с этим на базе частей материально-технического обеспечения и инженерно-саперных рот увеличен штат и формируются новые подразделения, согласно Указу Президента. Требуются: • Операторы БПЛА для разминирования путем сброс

30 Jul 2026, 06:03 UTC≈4,170 viewsread 12 August 2026
Photo

НАБОР В БАРС «МОСКВА» Ключевая задача – защита неба над Москвой. Мы формируем элитное добровольческое подразделение для работы с БПЛА-перехватчиками. Работа высокотехнологичными средствами противодействия – БПЛА-перехватчики, лазерные комплексы и иные инновационные средства Тип контракта – Контракт о пребывании в добровольческом формировании Статус – Доброволец Служба не относится к СВО . Контракт заключается стро

29 Jul 2026, 06:01 UTC≈5,590 viewsread 12 August 2026
Photo

Думаешь о контракте, но опасаешься «подводных камней»? Давай честно 👇 Мы знаем, как сейчас много разговоров, слухов и откровенного вранья вокруг военной службы. Кто-то обещает золотые горы, кто-то пугает, а кто-то просто берет трубку только до подписания контракта, а потом — «абонент недоступен». Мы работаем по-другому. Без понтов, без давления, по-честному. ✅ Деньги — перед подписанием садимся, берем калькулятор

28 Jul 2026, 15:03 UTC≈5,420 viewsread 12 August 2026
Photo

ДЕЛАЕМ ОТНОШЕНИЕ : МОСКОВСКИЙ ПОЛК 1429 ( ТЫЛ ) 12 Главное Управление МО 42 отдельный путевой Ж/Д батальон 71-я дивизия ремонтно-восстановительный батальон ( ТЫЛОВАЯ В/Ч г. Старый Оскол) 103-я отдельная бригада МТО ВМФ 155 бригада морской пехоты ПРЕДСТАВИТЕЛЬ ПОДРАЗДЕЛЕНИЯ НА СВЯЗИ 24/7,личное сопровождение в Пункте отбора ! Вакансии : - старший механик - начальник заправочного пункта - оператор - заправщик - старш

27 Jul 2026, 15:02 UTC≈5,040 viewsread 12 August 2026
Photo

​Набор в ремонтно-восстановительный батальон 71 дивизии по отношению! НЕ УЧАСТВУЮТ В СВО!!! ПВД (пункт временной дислокации) в белгородской области +- 200 км от ЛБС После подписания контракта 100% выезжаете в часть самостоятельно по ВПД (военно проездной документ). Направления отработаны. Всё работает. Без мутных схем, резервных частей и тд. ✅ Быстрое согласование. ✅ ЕДВ до 4 500 000 млн ✅ ЗП в ПВД от 250 000 руб.

26 Jul 2026, 15:03 UTC≈2,530 viewsread 12 August 2026
Photo

⚡️ МЫ НЕ ШТУРМОВИКИ !!! ‼️ НАБОР ПО ОТНОШЕНИЮ В ТЫЛ ‼️ 💰 Выплата до 4 500 000 млн рублей З/п от 210 000 ₽/мес ДАЕМ ПОДЪЕМНЫЕ 200 000 СРАЗУ ПОСЛЕ ПОДПИСАНИЯ КОНТРАКТА НА ЭКИПИРОВКУ И ОБОРУДОВАНИЕ ДЕЛАЕМ ОТНОШЕНИЕ : МОСКОВСКИЙ ПОЛК 1429 ( ТЫЛ ) 12 Главное Управление МО 42 отдельный путевой Ж/Д батальон 71-я дивизия ремонтно-восстановительный батальон ( ТЫЛОВАЯ В/Ч г. Старый Оскол) 103-я отдельная бригада МТО ВМФ 1

22 Jul 2026, 19:22 UTC≈2,160 viewsread 12 August 2026
Photo

Мастера отделочных работ на строительство вахтового поселка. Условия: • ЗП 150000-165 000 руб. (500р/час, смена 10-11 часов); • График работы: Работа вахтой от 60 смен; • Оформление по договору ГПХ со всеми полагающимися отчислениями (засчитывается в стаж для пенсии). Компания по производству модульных зданий (вахтовые поселки, жилые, административные, офисные здания, пождепо, КПП, ангары), успешно работаем на рынк

17 Jul 2026, 08:57 UTC≈4,230 viewsread 12 August 2026
Photo

8-912-750-14-71, Марина Заполните анкету, и мы перезвоним: vk.cc/cYe9se

6 Jul 2026, 06:03 UTC≈2,890 viewsread 12 August 2026

⚡️ Ищем продавца-консультанта в магазин техники (ТЦ Мой Порт) Мы — магазин электроники - АйПи Мобайл, техника Apple, Dyson, DJI, PS 5 и аксессуары Ищем в команду человека, который говорит с техникой на одном языке. Что нужно будет делать: • Консультировать клиентов по ассортименту (Apple, Dyson и не только) • Помогать с выбором и настройкой устройств. (если не знаете, всему можем научить) • Поддерживать порядок и

26 Jun 2026, 14:19 UTC≈5,500 viewsread 12 August 2026
Photo

8-912-750-14-71, Марина Заполните анкету, и мы перезвоним: vk.cc/cYe9se

26 Jun 2026, 11:46 UTC≈3,860 viewsread 12 August 2026

В ОНЛАЙН МАГАЗИН САМОКАТ СРОЧНО ТРЕБУЮТСЯ: ⚠️ АВТО/ВЕЛОКУРЬЕРЫ, СБОРЩИКИ ЗАКАЗОВ! 👋💛УСПЕЙ ЗАНЯТЬ СВОЕ МЕСТО В КОМАНДЕ МЕЧТЫ❤️ ✔️Адрес сотрудничества подберем более удобный по расположению ближе к дому. 🏆 ЗАРАБОТАЙ НА МЕЧТУ💥💥💥 Доход от 4000 руб в день! в зависимости от вашего города! Средняя оплата в час от 350 рублей + суммирующиеся надбавки 💵 Повышенный доход на приоритетных ЦФЗ ☔️ Надбавки за погодные условия

Showing the 12 most recent of 20 posts we hold for @rabota_izhevsk5. 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 — 773,431 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.

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

“Вакансии в ИЖЕВСКЕ” (@rabota_izhevsk5), 8,487 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/rabota_izhevsk5.

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.