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

Channel

Вакансии в Тамбове

@rabota_Tambovw

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Advertising · Posts · Posts recorded as deleted · Handles named that no longer answer · Telegram's recommendations · Cite this entry

23,429subscribers

-79 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-1001462582125
TypeChannel
Username@rabota_Tambovw
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 live6 November 2026
Measurements held52
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/rabota_Tambovw

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 the other topics.

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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@rabota_Tambovw/12547 · this entry5 Aug 2026, 11:35 UTC@tambov_rabotae/105225 Aug 2026, 11:35 UTC1.00under a minute
@tambov_rabotae/105245 Aug 2026, 14:06 UTC@rabota_Tambovw/12549 · this entry5 Aug 2026, 14:06 UTC1.00under a minute
@rabota_Tambovw/12550 · this entry5 Aug 2026, 15:22 UTC@tambov_rabotae/105276 Aug 2026, 06:04 UTC1.0015 hours
@rabota_Tambovw/12553 · this entry6 Aug 2026, 07:24 UTC@tambov_rabotae/105366 Aug 2026, 16:28 UTC1.009.1 hours
@tambov_rabotae/105316 Aug 2026, 10:23 UTC@rabota_Tambovw/12558 · this entry6 Aug 2026, 12:57 UTC1.002.6 hours
@tambov_rabotae/105437 Aug 2026, 12:52 UTC@rabota_Tambovw/12569 · this entry7 Aug 2026, 12:52 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@tambov_rabotae7 (7/7 hand-verifiable sample passed)1.003.7 hours@tambov_rabotae (5–2)

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. 3 of the 5 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 29 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_Tambovw — 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

23,42423,50823,4667 August 2026 — 23,508 subscribers7 August 2026 — 23,508 subscribers8 August 2026 — 23,505 subscribers9 August 2026 — 23,504 subscribers10 August 2026 — 23,501 subscribers11 August 2026 — 23,500 subscribers13 August 2026 — 23,499 subscribers14 August 2026 — 23,496 subscribers15 August 2026 — 23,492 subscribers17 August 2026 — 23,491 subscribers18 August 2026 — 23,489 subscribers19 August 2026 — 23,491 subscribers20 August 2026 — 23,490 subscribers24 August 2026 — 23,493 subscribers25 August 2026 — 23,491 subscribers26 August 2026 — 23,489 subscribers27 August 2026 — 23,485 subscribers28 August 2026 — 23,486 subscribers29 August 2026 — 23,488 subscribers30 August 2026 — 23,490 subscribers3 September 2026 — 23,487 subscribers4 September 2026 — 23,486 subscribers7 September 2026 — 23,481 subscribers12 September 2026 — 23,477 subscribers14 September 2026 — 23,479 subscribers16 September 2026 — 23,477 subscribers18 September 2026 — 23,476 subscribers25 September 2026 — 23,465 subscribers3 October 2026 — 23,457 subscribers8 October 2026 — 23,454 subscribers12 October 2026 — 23,448 subscribers14 October 2026 — 23,450 subscribers16 October 2026 — 23,447 subscribers17 October 2026 — 23,446 subscribers18 October 2026 — 23,442 subscribers19 October 2026 — 23,445 subscribers20 October 2026 — 23,443 subscribers22 October 2026 — 23,442 subscribers23 October 2026 — 23,439 subscribers24 October 2026 — 23,437 subscribers25 October 2026 — 23,432 subscribers26 October 2026 — 23,429 subscribers27 October 2026 — 23,430 subscribers28 October 2026 — 23,429 subscribers29 October 2026 — 23,426 subscribers30 October 2026 — 23,427 subscribers31 October 2026 — 23,430 subscribers1 November 2026 — 23,428 subscribers2 November 2026 — 23,424 subscribers3 November 2026 — 23,425 subscribers4 November 2026 — 23,426 subscribers6 November 2026 — 23,429 subscribers23,4297 August 20266 November 2026
52 measurements spanning 91 days, net -79. 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 23,411–23,521 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 52
Measured (UTC)SubscribersChange
6 Nov 2026, 07:3123,429+3
4 Nov 2026, 08:1523,426+1
3 Nov 2026, 07:1923,425+1
2 Nov 2026, 05:4123,424-4
1 Nov 2026, 07:4623,428-2
31 Oct 2026, 10:3623,430+3
30 Oct 2026, 08:1623,427+1
29 Oct 2026, 06:2923,426-3
28 Oct 2026, 06:2623,429-1
27 Oct 2026, 04:0523,430+1
26 Oct 2026, 03:3723,429-3
25 Oct 2026, 00:4623,432-5
24 Oct 2026, 00:0523,437-2
23 Oct 2026, 02:4423,439-3
22 Oct 2026, 00:4523,442-1
20 Oct 2026, 16:2023,443-2
19 Oct 2026, 12:5923,445+3
18 Oct 2026, 09:4023,442-4
17 Oct 2026, 11:4623,446-1
16 Oct 2026, 08:3523,447first reading

Engagement

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

ERR · 30 days
13.5%
avg views ÷ 23,429 subscribers
Avg views / post
3,170
231 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
231
of 663 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 5 November 2026
Posts held663 (5 August 2026 – 5 November 2026)
Views total732,747
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 02:21 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
1m 28s
Average length
7s

Measured directly from 13 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.98%
33 of 663 posts carry an ad marker
Regulatory tokens
33
posts carrying an erid · 5 distinct tokens
Median views · ads
3,460
over 33 measured posts
Median views · rest
3,040
over 625 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
CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd7G1128 September 20265 November 2026
CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd776 August 202631 August 2026
2SDnjdDRjvV64 October 20261 November 2026
5jtCeReNwxHpfQTDve31wmc67 August 20264 November 2026
2W5zFHRnKXf311 October 202625 October 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 663 most recent posts we hold, published 5 August 2026 to 5 November 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

Telegram’s own ‘edited’ marker: 1 of 231 posts held from the last 30 days (0.433%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

5 Nov 2026, 19:26 UTC462 viewsread 6 November 2026
Advertisementerid CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd7GVideo

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

5 Nov 2026, 16:53 UTC885 viewsread 6 November 2026

Вакансия из города Мичуринск Формовщик г. Рязань Зарплата по договоренности. Обязанности: • Осуществлять приготовление эпоксидного компаунда в соответствии с требованиями конструкторской и технологической документации. • Осуществлять изготовление изделий из стеклопластика методом контактного формования и вакуумной ламинацией в соответствии с требованиями конструкторской и технологической документации. • Строго собл…

5 Nov 2026, 15:36 UTC≈1,080 viewsread 6 November 2026

Вакансия из города Мичуринск Энергодиспетчер 76000 ₽ Обязанности: • Оперативное диспетчерское управление устройствами электроснабжения (оборудование тяговых подстанций, контактной сети, линий электроснабжения устройств СЦБ и др) • Контроль за своевременным внесением изменений в схемы устройств энергоснабжения, ремонтных работ, устранением повреждений • Учет неисправного оборудования и контроль ввода его в работу • …

5 Nov 2026, 14:21 UTC≈1,490 viewsread 6 November 2026

Вакансия из города Мичуринск Продавец Подработка 55000 ₽ Обязанности: • Работа в торговом зале • Консультация покупателей • Выкладка и отслеживание сроков годности товаров Требования: • Желание работать с покупателями Мы предлагаем: • Смены от 4-х часов, по выходным или по вечерам • Возможность совмещать с учебой или работой • Быстрое оформление по ТК РФ - с помощью Госуслуг • Фиксированный оклад + премии и надба…

5 Nov 2026, 13:05 UTC≈1,730 viewsread 6 November 2026

Формовщик г. Рязань Зарплата по договоренности. Обязанности: • Осуществлять приготовление эпоксидного компаунда в соответствии с требованиями конструкторской и технологической документации. • Осуществлять изготовление изделий из стеклопластика методом контактного формования и вакуумной ламинацией в соответствии с требованиями конструкторской и технологической документации. • Строго соблюдать этапы технологического п…

5 Nov 2026, 11:48 UTC≈2,000 viewsread 6 November 2026

Агент по недвижимости Зарплата по договоренности. Требования: • Горишь желанием развиваться • Любишь общаться с людьми • Готов брать на себя ответственность Мы предлагаем: • Бесплатный входной билет в профессию: Наше обучение в Бизнес-школе CENTURY 21 • Высокий процент + сделки с недвижимостью по всей России и за границей • Крутой маркетинг и всей необходимая поддержка (юристы, ипотека, CRM, реклама) • Возможность …

5 Nov 2026, 10:33 UTC≈2,380 viewsread 6 November 2026

Слесарь Зарплата по договоренности. Обязанности: • Конвейерная сборка отдельных узлов и агрегатов (можно без опыта!) Требования: • Без опыта Мы предлагаем: • Вахтовый метод, продолжительность 60/30,40/20 • График 6/1 по 12 часов • Оформление по трудовому договору • Бесплатное проживание для иногородних-хостел • Бесплатные комплексные обеды • Бесплатный трансфер • Работа в цехе • Спецодежда и обувь на первое время …

5 Nov 2026, 09:17 UTC≈2,550 viewsread 6 November 2026

Монтажник РЭАиП Зарплата по договоренности. Обязанности: • Сборка радиоуправляемых игрушек • Чтeниe карт paскладки провoдов, монтажных схем и чертежей • Осуществление монтажа электронных плат, компонентов, проводов жгутов и соединительных хомутов • Вязка («вязка») и монтаж жгутов различной сложности • Работы по монтажу и устройству приборов радиоэлектронной аппаратуры • Контроль качества пайки и паяных соединений на…

5 Nov 2026, 08:04 UTC≈2,800 viewsread 6 November 2026
Photo

🎖СЛУЖБА ПО КОНТРАКТУ 🎖 🇷🇺В Вооруженных Силах РФ 🇷🇺 ✅Полное сопровождение. Регион прописки значения не имеет. Принимаются граждане РФ и других стран. ✅Выплаты до 4.500.000 ₽ единовременно + от 260.000 ₽/мес. Выплаты зависят от должности. ✅Вакантные должности: БПЛА подразделения IT технологии Водители B,C,E,D, в том числе материального обеспечения Артиллерийские подразделения Ремонтные подразделения Отделения связи …

5 Nov 2026, 07:19 UTC≈2,910 viewsread 6 November 2026

Продавец-кассир 55000 ₽ Обязанности: • Работа за кассой и в торговом зале • Консультация покупателей • Выкладка и отслеживание сроков годности товаров Требования: • Желание работать с покупателями • Для иностранных специалистов обязательно наличие патента в случаях прямо предусмотренных действующим законодательством Мы предлагаем: • Быстрое оформление по ТК РФ - с помощью Госуслуг • Фиксированный оклад + премии и …

5 Nov 2026, 06:04 UTC≈3,110 viewsread 6 November 2026

Бетонщик 214000 - 247000 ₽ Обязанности: • Приготовление бетонной смеси • Дозирование компонентов (цемента, песка, щебня, воды) по массе и объёму с соблюдением технологических требований • Укладка смеси Требования: • Действующее удостоверение Бетонщика Контакты: [email protected]

5 Nov 2026, 05:39 UTC≈3,120 viewsread 6 November 2026

Рабочие на монтаж лотков (150 000 руб.) Ищем людей или бригаду на объект в г. Котовск (Тамбовская обл.). Опыт не нужен, всему научим! Работа простая: крепить металлическое лотки на готовые опоры (без электрики и кабеля). Условия: • Оплата: 150 000 рублей на человека за объем. • Срок: около 3 недель (объем 3 км). • За наш счет: проживание, трансфер, инструмент и спецодежда. • Выплаты: выдаем регулярные авансы на еду…

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

Posts recorded as deleted after publishing

We recorded 3 posts on @rabota_Tambovw as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
17 August 2026
Most recent seen missing
15 October 2026
Median time before seen missing
29 hours
Seen missing in the last 30 days
1

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Работа в Витебске
@pratsa_vakansiiy · 3
#1
Брест Работа
@pratsa_vakansiiz · 11
#2
Вакансии в Королёве
@rabota_korolevc · 13,567
#3
Вакансии в Питере
@rabota_piter · 69,923
#4
Работа в Гомеле | Гомель
@pratsa_vakansiia · 38,984
#5
Вакансии в Костроме
@rabota_kostromaz · 23,411
#6
Работа в Борисове
@pratsa_vakansiiw · 19,751
#7
Ростов Вакансии
@rabota_rostov · 53,943
#8
Работа в Бобруйске
@pratsa_vakansiix · 20,907
#9
Вакансии в Феодосии
@rabota_feodosiaq · 14,384
#10
Вакансии в Новосибирске
@rabota_novosibirsxv · 47,504
#11
Вакансии в Курске
@rabota_kurskc · 22,639
#12
Вакансии в Щелково
@rabota_shchelkovoy · 17,735
#13
Работа в Краснодаре
@vakansiy_krasnodare_v · 42,627
#14
Нижний Новгород Работа
@rabota_nizhnyc · 5,238
#15
Работа в Красноярске
@rabota_krasnoyarskn · 15
#16
Вакансии в Ялте
@rabota_yaltaa · 17,806
#17
Краснодар Вакансии
@rabota_v_krasnodarez · 48,750
#18
Вакансии в Крыму
@krym_rabota · 70,205
#19
Вакансии в Туле
@rabota_tulaq · 26,896
#20
Вакансии Ставрополь
@v_stavropole_rabota · 10,977
#21
Вакансии в Сургуте
@rabota_surgutd · 9,188
#22
Работа Ростов
@rostove_vakansiy · 54,978
#23
Вакансии в Братске
@rabota_bratskz · 10,653
#24
Вакансии ЕКБ
@rabota_v_ekbe · 61,000
#25
Вакансии в Уфе
@rabota_ufac · 70,085
#26
Вакансии в Белогорске
@rabota_belogorskz · 6,988
#27
Вакансии в Майкопе
@rabota_maikop · 5,803
#28
Вакансии в Славянске-на-Кубани
@rabota_na_kubani_slavyansk · 23
#29
Работа Гомель
@pratsa_vakansiiq · 6
#30
Вакансии в Когалыме
@kogalym_rabotac · 7,711
#31
Вакансии в Самаре
@rabotan_samara · 56,363
#32
Вакансии в Егорьевске
@egorevsx_rabotae · 8,309
#33
Вакансии в Борисоглебске
@rabota_borisoglebskz · 6,797
#34
Вакансии в Ногинске
@rabota_noginski · 6,656
#35
Вакансии в Балхаше
@Balkhash_rabotaz · 9,703
#36
Работа в Сочи
@vakansii_sochy · 54,288
#37
Вакансии в Каменск-Шахтинском
@rabota_shakhtinsky_kamensk · 9,943
#38
Кемерово Вакансии
@rabota_Kemerovom · 10,213
#39
Работа в Нижневартовске
@vakansii_nizhnevartovsx · 11,138
#40
Вакансии в Лобне
@rabota_lobnyae · 12,137
#41
Вакансии в Азове
@azov_rabotac · 10,312
#42
Работа Казань
@vakansiy_kazany · 57,011
#43
Работа в Могилеве
@pratsa_vakansiif · 4
#44
Работа в Гродно
@pratsa_vakansiie · 25,416
#45
Тамбов | Куда пойти? | Что поделать? Афиша Тамбов
@tambov_afisha · 4,239
#46
Работа в Казахстане
@vakansii_almatye · 31,202
#47
Работа в Минске
@pratsa_vakansiil · 3
#48
Вакансии в Алании
@alania_rabotai · 18,296
#49
Вакансии в Твери
@rabota_tverw · 19,673
#50
Работа в Пинске
@pratsa_vakansiip · 19,169
#51
Работа в Алматы
@zhumys_vakansiif · 18
#52
Работа Актобе
@zhumys_vakansiiu · 23,221
#53
Работа в Шымкенте
@zhumys_vakansiic · 40,487
#54
Работа Атырау
@zhumys_vakansiid · 28,663
#55
rabota_stambulq перехвачен telegraber.ru
@rabota_stambulq · 6
#56
Работа в Могилеве
@pratsa_vakansiim · 24,386
#57
Работа в Минске
@pratsa_vakansiic · 3
#58
Работа Алматы
@zhumys_vakansiis · 17
#59
Работа в Зеленограде
@zelenograd_vakansiy · 21,799
#60
Работа в Витебске
@pratsa_vakansiiv · 24,610
#61
Вакансии в Невинномысске
@rabota_nevinnomysskz · 2,790
#62
Вакансии в Зеленограде
@zelenograd_rabotaz · 9,904
#63
Работа в Гродно
@pratsa_vakansiig · 26,138
#64
EXPERT_EKOLOG_TEAM
@expert_ekolog_team · 125
#65
Работа в Бресте
@pratsa_vakansiib · 22,944
#66
Вакансии в Хабаровске
@rabota_khabarovskc · 32,456
#67
Работа в Пинске
@pratsa_vakansiid · 5,162
#68
Вакансии в Алании | Алания
@rabota_alaniyaz · 20,784
#69
Вакансии в Нефтекамске
@rabota_neftekamskb · 14
#70
Вакансии в Ростове
@rabota_rostovz · 100,607
#71
Вакансии Алматы
@almaty_rabota · 56,260
#72
Вакансии в Анталии
@rabota_antaliai · 24,936
#73
Набор сотрудников в команду по арбитражу монет
@stambul_rabotae · 10
#74
Работа в Карловых Варах
@vakansii_karlovy_vary · 5,802
#75
Набор сотрудников в команду по арбитражу монет
@pragae_chekhia · 5
#76
МСК Вакансии
@rabota_mskr · 70,438
#77
Работа Брно
@rabota_brno · 1
#78
Вакансии Прага | Работа
@praga_chekhiae · 15
#79
Вакансии в Раменском
@rabota_ramenskoee · 6,010
#80
Застройщик УДСД
@udsd89 · 215
#81
Народный фронт | Тамбовская область
@nf_tambov · 577
#82
Борисовка ❤️
@borisovka_online · 3,954
#83

Read from Telegram’s recommendation API, most recently 18 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

Работа в Борисове
@pratsa_vakansiiw · 19,751
Telegram ranks this channel #5 of 82 here — alongside 81 others — read 29 September 2026
Работа в Бобруйске
@pratsa_vakansiix · 20,907
Telegram ranks this channel #5 of 82 here — alongside 81 others — read 24 September 2026
Вакансии в Костроме
@rabota_kostromaz · 23,411
Telegram ranks this channel #5 of 80 here — alongside 79 others — read 18 September 2026
Вакансии в Туле
@rabota_tulaq · 26,896
Telegram ranks this channel #6 of 77 here — alongside 76 others — read 11 September 2026
Работа в Гомеле | Гомель
@pratsa_vakansiia · 38,984
Telegram ranks this channel #8 of 84 here — alongside 83 others — read 28 September 2026
Вакансии в Питере
@rabota_piter · 69,923
Telegram ranks this channel #8 of 100 here — alongside 99 others — read 22 August 2026
Вакансии ЕКБ
@rabota_v_ekbe · 61,000
Telegram ranks this channel #9 of 89 here — alongside 88 others — read 23 August 2026
Краснодар Вакансии
@rabota_v_krasnodarez · 48,750
Telegram ranks this channel #11 of 89 here — alongside 88 others — read 26 August 2026
Работа Казань
@vakansiy_kazany · 57,011
Telegram ranks this channel #11 of 90 here — alongside 89 others — read 23 August 2026
Вакансии в Крыму
@krym_rabota · 70,205
Telegram ranks this channel #11 of 94 here — alongside 93 others — read 22 August 2026
Вакансии в Курске
@rabota_kurskc · 22,639
Telegram ranks this channel #12 of 83 here — alongside 82 others — read 20 September 2026
Работа в Краснодаре
@vakansiy_krasnodare_v · 42,627
Telegram ranks this channel #12 of 96 here — alongside 95 others — read 26 August 2026
Нижний Новгород Работа
@rabota_nizhnyc · 5,238
Telegram ranks this channel #12 of 88 here — alongside 87 others — read 25 August 2026
Вакансии в Смоленске
@Rabota_Smolenskc · 21,634
Telegram ranks this channel #13 of 63 here — alongside 62 others — read 23 September 2026
Вакансии в Уфе
@rabota_ufac · 70,085
Telegram ranks this channel #13 of 88 here — alongside 87 others — read 23 August 2026
Вакансии в Твери
@rabota_tverw · 19,673
Telegram ranks this channel #14 of 77 here — alongside 76 others — read 30 September 2026
Вакансии в Новосибирске
@rabota_novosibirsxv · 47,504
Telegram ranks this channel #14 of 98 here — alongside 97 others — read 26 August 2026
Вакансии в Орле
@orel_rabotaq · 21,896
Telegram ranks this channel #15 of 48 here — alongside 47 others — read 16 September 2026
Вакансии в Воронеже
@rabota_voronezh5 · 41,287
Telegram ranks this channel #16 of 74 here — alongside 73 others — read 6 September 2026
rabota_stambulq перехвачен telegraber.ru
@rabota_stambulq · 6
Telegram ranks this channel #17 of 78 here — alongside 77 others — read 22 September 2026
Работа в Красноярске
@rabota_krasnoyarskn · 15
Telegram ranks this channel #17 of 87 here — alongside 86 others — read 27 August 2026
Вакансии в Самаре
@rabotan_samara · 56,363
Telegram ranks this channel #18 of 87 here — alongside 86 others — read 22 August 2026
МСК Вакансии
@rabota_mskr · 70,438
Telegram ranks this channel #19 of 98 here — alongside 97 others — read 22 August 2026
Работа в Алматы
@zhumys_vakansiif · 18
Telegram ranks this channel #20 of 80 here — alongside 79 others — read 21 September 2026

This channel appears in 65 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 6 November 2026 — this entry's latest reading, not the date you are reading this.

“Вакансии в Тамбове” (@rabota_Tambovw), 23,429 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/rabota_Tambovw.

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.