Telegram RegisterThe public register of Telegram
Telegram profile photo for Вакансии в Люберцах

Channel

Вакансии в Люберцах

@rabota_lyubertsyu

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

18,978subscribers

-19 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-1001195153448
TypeChannel
Username@rabota_lyubertsyu
DescriptionОпубликовать вакансию или рекламу: t.me/m/VBf1dTuzM2Ji (Среднее время ответа 2 минуты) Если ссылка не открылась: @global_manager
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 live16 November 2026
Measurements held54
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/rabota_lyubertsyu

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 in near-verbatim form on 12 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
@lyubertsy_rabotaq/108807 Aug 2026, 08:00 UTC@rabota_lyubertsyu/14853 · this entry7 Aug 2026, 08:00 UTC1.00under a minute
@lyubertsy_rabotaq/1101019 Aug 2026, 08:25 UTC@rabota_lyubertsyu/14983 · this entry19 Aug 2026, 08:25 UTC1.00under a minute
@lyubertsy_rabotaq/1101119 Aug 2026, 08:44 UTC@rabota_lyubertsyu/14984 · this entry19 Aug 2026, 08:44 UTC1.00under a minute
@lyubertsy_rabotaq/1107325 Aug 2026, 06:37 UTC@rabota_lyubertsyu/15046 · this entry25 Aug 2026, 06:37 UTC1.00under a minute
@lyubertsy_rabotaq/1107825 Aug 2026, 11:31 UTC@rabota_lyubertsyu/15051 · this entry25 Aug 2026, 11:31 UTC1.00under a minute
@lyubertsy_rabotaq/1108526 Aug 2026, 07:46 UTC@rabota_lyubertsyu/15058 · this entry26 Aug 2026, 07:46 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@lyubertsy_rabotaq21 (8/8 hand-verifiable sample passed)1.0037 minutes@lyubertsy_rabotaq (17–4)
@lytkarino_rabotae18 (8/8 hand-verifiable sample passed)0.993.4 hoursthis entry (13–5)
@balashikha_rabotaq18 (8/8 hand-verifiable sample passed)0.9988 minutesthis entry (10–8)
@rabota_zhukovsky15 (8/8 hand-verifiable sample passed)0.993.3 hoursthis entry (10–5)
@balashikha_rabotae15 (8/8 hand-verifiable sample passed)0.992.5 hoursthis entry (12–3)
@balashikha_vakansiyy14 (8/8 hand-verifiable sample passed)0.995.3 hours@balashikha_vakansiyy (8–6)
@rabota_vidnoee10 (8/8 hand-verifiable sample passed)1.002.6 hourseven
@khimky_rabota9 (8/8 hand-verifiable sample passed)0.995.1 hoursthis entry (5–4)
@odintsovo_rabotae9 (8/8 hand-verifiable sample passed)1.0084 minutesthis entry (6–3)
@Orekhovo_Zuevo_rabota8 (8/8 hand-verifiable sample passed)1.004.0 hoursthis entry (5–3)
@kolomna_rabotaz8 (8/8 hand-verifiable sample passed)1.003.7 hours@kolomna_rabotaz (7–1)
@rabotaz_dolgoprudnyi8 (8/8 hand-verifiable sample passed)1.002.7 hoursthis entry (5–3)

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. 114 of the 114 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 464 comparable posts for this entry, running 5 August 2026 to 16 November 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).

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 17 November 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.

Growth

18,97819,05019,0147 August 2026 — 18,997 subscribers7 August 2026 — 18,997 subscribers8 August 2026 — 18,995 subscribers9 August 2026 — 18,997 subscribers10 August 2026 — 18,993 subscribers12 August 2026 — 18,990 subscribers13 August 2026 — 18,991 subscribers14 August 2026 — 18,990 subscribers16 August 2026 — 18,988 subscribers18 August 2026 — 18,993 subscribers19 August 2026 — 18,994 subscribers21 August 2026 — 18,996 subscribers25 August 2026 — 18,998 subscribers27 August 2026 — 19,000 subscribers28 August 2026 — 19,003 subscribers29 August 2026 — 19,001 subscribers30 August 2026 — 18,998 subscribers1 September 2026 — 19,000 subscribers2 September 2026 — 19,004 subscribers4 September 2026 — 19,002 subscribers7 September 2026 — 18,996 subscribers10 September 2026 — 19,050 subscribers12 September 2026 — 19,043 subscribers14 September 2026 — 19,045 subscribers16 September 2026 — 19,044 subscribers30 September 2026 — 19,040 subscribers6 October 2026 — 19,037 subscribers10 October 2026 — 19,023 subscribers13 October 2026 — 19,017 subscribers14 October 2026 — 19,009 subscribers15 October 2026 — 18,996 subscribers16 October 2026 — 18,991 subscribers17 October 2026 — 18,989 subscribers18 October 2026 — 18,987 subscribers19 October 2026 — 18,992 subscribers20 October 2026 — 18,993 subscribers21 October 2026 — 18,996 subscribers22 October 2026 — 18,997 subscribers23 October 2026 — 18,996 subscribers24 October 2026 — 18,995 subscribers27 October 2026 — 18,997 subscribers28 October 2026 — 18,995 subscribers29 October 2026 — 18,993 subscribers31 October 2026 — 18,992 subscribers1 November 2026 — 18,991 subscribers2 November 2026 — 18,989 subscribers3 November 2026 — 18,990 subscribers4 November 2026 — 18,991 subscribers5 November 2026 — 18,989 subscribers6 November 2026 — 18,988 subscribers7 November 2026 — 18,986 subscribers9 November 2026 — 18,982 subscribers12 November 2026 — 18,983 subscribers16 November 2026 — 18,978 subscribers7 August 202616 November 2026
54 measurements spanning 101 days, net -19. 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 18,967–19,061 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 54
Measured (UTC)SubscribersChange
16 Nov 2026, 00:0918,978-5
12 Nov 2026, 11:1118,983+1
9 Nov 2026, 01:3818,982-4
7 Nov 2026, 19:0818,986-2
6 Nov 2026, 15:1618,988-1
5 Nov 2026, 12:2518,989-2
4 Nov 2026, 10:4418,991+1
3 Nov 2026, 12:3718,990+1
2 Nov 2026, 13:3918,989-2
1 Nov 2026, 15:3918,991-1
31 Oct 2026, 17:0618,992-1
29 Oct 2026, 16:4918,993-2
28 Oct 2026, 16:1018,995-2
27 Oct 2026, 19:1818,997+2
24 Oct 2026, 21:0418,995-1
23 Oct 2026, 22:0618,996-1
22 Oct 2026, 23:3818,997+1
21 Oct 2026, 23:1518,996+3
20 Oct 2026, 16:3618,993+1
19 Oct 2026, 18:2118,992first reading

Engagement

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

ERR · 30 days
14.0%
avg views ÷ 18,978 subscribers
Avg views / post
2,660
186 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
186
of 486 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 17 November 2026
Posts held486 (5 August 2026 – 17 November 2026)
Views total494,721
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 17:09 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
≈3,090
Videos
≈73
Links
≈9,820

Lifetime counters from Telegram’s own channel header, read 17 November 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
40s
Average length
5s

Measured directly from 8 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.32%
21 of 486 posts carry an ad marker
Regulatory tokens
21
posts carrying an erid · 5 distinct tokens
Median views · ads
2,510
over 21 measured posts
Median views · rest
2,290
over 456 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
CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd776 August 202631 August 2026
CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd7G52 November 202616 November 2026
5jtCeReNwxHpfQTDve31wmc47 August 202611 November 2026
2SDnjdDRjvV31 November 202614 November 2026
2W5zFHRnKXf28 November 202615 November 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 486 most recent posts we hold, published 5 August 2026 to 17 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: 3 of 186 posts held from the last 30 days (1.61%) 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).

17 Nov 2026, 15:37 UTC146 viewsread 17 November 2026

Инженер-механик Зарплата по договоренности. Обязанности: • Организация бесперебойной и стабильной работы всего оборудования, приборов • Разработка планов и графиков регулярного и профилактического осмотра, технического обслуживания и капитального... Требования: • Высшее, среднее-специальное, техническое образование Контакты: +79651682892

17 Nov 2026, 14:21 UTC210 viewsread 17 November 2026

Врач-терапевт Зарплата по договоренности. Обязанности: • Выполняет перечень работ и услуг для диагностики заболевания, оценки состояния больного и клинической ситуации в соответствии со стандартом медицинской помощи. • Обосновывает клинический диагноз, план и тактику ведения больного. • Выполняет перечень работ и услуг для лечения заболевания, состояния, клинической ситуации в соответствии со стандартом медицинской …

17 Nov 2026, 13:02 UTC562 viewsread 17 November 2026

Электрик по ремонту и обслуживанию на производство Зарплата по договоренности. Обязанности: • Диагностика состояния оборудования, своевременное выявление дефектов и принятие решений по устранению неполадок • Выполнение работ по поддержанию исправного состояния электрооборудования в производственных помещениях • Ведение необходимой технической документации (акты приёмки-передачи, журналы учета и испытаний оборудовани…

17 Nov 2026, 11:44 UTC877 viewsread 17 November 2026

🚨СРОЧНО 🚨На рыбное производство требуются сотрудники цеха ,опыт работы приветствуется,но необязателен,при желании работать в нашей компании обучим всему необходимому. График работы: Обсуждается с руководством. Питание: Трехразовое. Жилье предоставляем. Оформление: Официальное. Для иностранных граждан:Трудовой патент обязателен. Иностранным гражданам,патент оплачивается за счет компании. Зарплата :100000 руб в месяц.…

17 Nov 2026, 11:14 UTC966 viewsread 17 November 2026

Слесарь-сборщик металлоконструкций 90000 ₽ Обязанности: • Изготовление воздуховодов и элементов для систем вентиляции на станках и вручную • Изготовление замков на станках для последующей сборки деталей Требования: • Желателен опыт работы с тонколистным металлом • Готовность к физическим нагрузкам • Навыки работы с ручным и электроинструментом • Приветствуется опыт работы на металлообрабатывающем оборудовании • Жел…

17 Nov 2026, 09:56 UTC≈1,220 viewsread 17 November 2026

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

17 Nov 2026, 08:39 UTC≈1,380 viewsread 17 November 2026

Врач-ревматолог 250000 ₽ Обязанности: • Амбулаторный прием пациентов • Владение трактовкой лабораторных исследований. • Выписка справок, рецептов. • Умение делать внутрисуставные блокады (приветствуется) Требования: • Действующий сертификат специалиста (дополнительные сертификаты и обучения приветствуются) • Опыт работы от 6-х лет по специальности. • Опыт работы в коммерческих медицинских учреждениях приветствуется…

17 Nov 2026, 07:22 UTC≈1,640 viewsread 17 November 2026

Вязальщик жгутов 181896 ₽ Обязанности: • Вязка по шаблонам простых схемных жгутов и кабелей из жестких и мягких проводов для радиоаппаратуры и приборов различного назначения • Пайка • Опрессовка кабелей Требования: • Опыт проведения аналогичных работ от 3 лет • Разряд 4-6 Мы предлагаем: • Работа на производственном предприятии в г. Рязань • Вахтовый метод работы 60/30 и др. • Прямой работодатель • Трудоустройство …

17 Nov 2026, 06:05 UTC≈1,700 viewsread 17 November 2026

Водитель вилочного штабелера 112720 - 117720 ₽ Обязанности: • Приёмка, отгрузка и комплектация заказов на складе • Перемещение товаров по складу • Размещение и снятие товара со стеллажей с помощью высотной... Требования: • Опыт работы на высотном штабелере (ричтрак) от 1-го года • Удостоверение тракториста-машиниста категории В (с отметкой Водитель погрузчика или... Контакты: +79032317017

16 Nov 2026, 18:23 UTC≈2,260 viewsread 17 November 2026
Advertisementerid CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd7GPhoto

Работа без опыта, без собеседований, без «мы вам перезвоним» Подработка курьером Яндекс Еды и Яндекс Лавки: анкета онлайн — и можно выходить на первый слот. Набор ведёт официальный партнёр сервиса. 📍 из документов — только удостоверение личности 📍 никаких собеседований и стажировок за бесплатно 📍 оформление как самозанятый — официально 😍 не нужен свой транспорт: велосипед Яндекс Байк — за 1 ₽ Регистрация онлайн, з…

Showing the 12 most recent of 486 posts we hold for @rabota_lyubertsyu. 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 edited after publishing

@rabota_lyubertsyu edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
26 August 2026
Most recent edit
26 August 2026

Posts recorded as deleted after publishing

We recorded 2 posts on @rabota_lyubertsyu 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
16 August 2026
Most recent seen missing
17 August 2026
Median time before seen missing
27 hours
Seen missing in the last 30 days
0

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.

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.

Вакансии в Люберцах
@lyubertsy_rabotaq · 5,263
#1
Вакансии в ЛЮБЕРЦАХ
@Rabota_Lyubertsym · 5,035
#2
Вакансии в Сургуте
@rabota_surgutd · 9,190
#3
Вакансии в Раменском
@ramenskoe_rabotaz · 4,636
#4
Вакансии в Рязани
@rabota_Ryazann · 38,876
#5
Вакансии в Майкопе
@rabota_maikop · 5,805
#6
Вакансии в Славянске-на-Кубани
@rabota_na_kubani_slavyansk · 6,860
#7
Вакансии в Братске
@rabota_bratskz · 10,646
#8
Вакансии в Белогорске
@rabota_belogorskz · 6,915
#9
Вакансии в Егорьевске
@egorevsx_rabotae · 8,038
#10
Вакансии в Борисоглебске
@rabota_borisoglebskz · 6,726
#11
Вакансии в Новочеркасске
@vakansii_novocherkassx · 4,060
#12
Вакансии в Пушкино
@rabota_pushkinoe · 6,222
#13
Вакансии в Ногинске
@rabota_noginski · 6,656
#14
Вакансии в Коломне
@kolomna_rabotae · 6,177
#15
Вакансии в Нальчике
@rabota_nalchikc · 10,180
#16
Работа в Бийске
@bysx_vakansiy · 5,476
#17
Вакансии в Лобне
@rabota_lobnyae · 11,944
#18
Вакансии в Абакане
@abakan_rabotac · 12,315
#19
Вакансии в Магадане
@rabota_magadanc · 10,809
#20
Вакансии в Йошкар-Оле
@rabota_ola_yoshkar · 11,165
#21
Вакансии в Видном
@rabota_vidnoee · 10,561
#22
Оренбург Вакансии
@orenburg_rabotam · 21,010
#23
Вакансии в Хасавюрте
@khasavyurt_rabotac · 7,575
#24
Вакансии в Улан-Удэ
@ulan_ude_rabotac · 12,245
#25
Вакансии в Пскове
@rabota_pskovv · 10,693
#26
Вакансии в Королёве
@rabota_korolevc · 13,563
#27
Вакансии в Выборге
@rabota_Vyborgc · 8,921
#28
Вакансии в Жуковском
@rabota_zhukovsky · 13,665
#29
Работа в Гомеле | Гомель
@pratsa_vakansiia · 41,567
#30
Вакансии в Мурманске
@rabota_murmanskc · 26,476
#31
Вакансии в Намангане
@rabota_namangan1 · 18,942
#32
Вакансии в Пензе
@rabota_Penzaq · 30,171
#33
Мои Люберцы ®️
@myluber · 109,262
#34
Работа в Гродно
@pratsa_vakansiie · 12
#35
Работа в Могилеве
@pratsa_vakansiif · 11
#36
Вакансии в Мариуполе
@Rabota_Mariupol2 · 1,268
#37
Брест Работа
@pratsa_vakansiiz · 12
#38
Работа в Минске
@pratsa_vakansiil · 11
#39
Вакансии в Питере
@rabota_piter · 117,971
#40
Работа в Казахстане
@vakansii_almatye · 30,976
#41
Работа в Борисове
@pratsa_vakansiiw · 19,468
#42
Вакансии в Рязани
@rabota_Ryazanz · 15
#43
Вакансии в Москве
@moskva_rabota · 29,163
#44
Вакансии в Раменском
@rabota_ramenskoee · 6,011
#45
Santa_Murzilka - 🌏 -
@murzilka_inc · 241
#46
Berega.turi
@berega_turi · 487
#47
Вакансии в Реутове
@reutov_rabotae · 3,091
#48
Управление культуры АМО «Кошехабльский район»
@ukkoshehabl · 219
#49
МотоИнструктор МотоТуры Дагестан
@YUG23M · 373
#50
Танцующий кондитер 👠
@natali_sweets_klm · 141
#51
ОБЛИЦОВКА ДОМОВ | Fasad Stroy
@FasadStroy_05 · 301 (as read 4 October 2026)
#52
Сергей Лобанов
@SMO26 · 856
#53
Летим на отдых | ПчелаТур 🐝
@pchelatour · 894
#54
Работа в Макеевке
@vakansii_makeyevkaa · 2,318
#55
☕️Психология кофейной гущи с Тамарой Кабаковой
@tamaraikoffe · 1,148
#56
Восточные танцы базовые движения и мини уроки танец живота bellydance 💃💃💃 @melnikovajeni
@melnikovajeni · 341
#57
КАБИНЕТ РЕДКОСТЕЙ АНТИКВАРИАТ/ИСТОРИЯ
@tvorheskydom · 657
#58
МСК Вакансии
@rabota_mskr · 131,545
#59
Бродячие Псы 🍒
@bsdpon13 · 288
#60
Геометрия Спорта | Туры из Ростова-на-Дону
@geometry_sporta · 1,239
#61
Интересный Крым
@kryms · 4,125
#62
Я тебя продам!
@ohkurkova · 587
#63
Лена про WB | Закупки из Китая | 1688
@lena_pro_taobao · 608
#64
Нумеролог Яковлева Елена
@numerog · 489
#65
Ельский
@elskilive · 840
#66
цитрусовый сад.
@sagotalll · 134
#67
ПСИХОЛОГ Институт Эмоциональных Технологий
@EmotionalTechnology · 458
#68

Read from Telegram’s recommendation API, most recently 4 October 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.

Вакансии в Воронеже
@rabota_voronezh5 · 95,732
Telegram ranks this channel #15 of 74 here — alongside 73 others — read 6 September 2026
Вакансии в Красногорске
@Rabota_Krasnogorskw · 34,249
Telegram ranks this channel #16 of 77 here — alongside 76 others — read 3 September 2026
Вакансии в Рязани
@rabota_Ryazann · 38,876
Telegram ranks this channel #24 of 76 here — alongside 75 others — read 31 August 2026
Крым Вакансии
@sevastopole_Simferopole · 4,056
Telegram ranks this channel #28 of 73 here — alongside 72 others — read 28 August 2026
Вакансии во Владимире
@rabota_vladimirt · 20,191
Telegram ranks this channel #40 of 78 here — alongside 77 others — read 28 September 2026
Работа в Москве
@moskva_vakansii · 117,056
Telegram ranks this channel #44 of 82 here — alongside 81 others — read 22 August 2026
Вакансии в Кургане
@kurgan_rabotaq · 24,360
Telegram ranks this channel #56 of 71 here — alongside 70 others — read 28 September 2026
Вакансии в Москве
@moskva_rabota · 29,163
Telegram ranks this channel #56 of 67 here — alongside 66 others — read 6 September 2026
Вакансии в Великом Новгороде
@Rabota_Velikyy · 18,871
Telegram ranks this channel #65 of 85 here — alongside 84 others — read 2 October 2026

This channel appears in 9 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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“Вакансии в Люберцах” (@rabota_lyubertsyu), 18,978 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/rabota_lyubertsyu.

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.