Channel
@rabotaYandexOTG
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2,502subscribers
+93 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003378565134 |
|---|---|
| Type | Channel |
| Username | @rabotaYandexOTG |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/rabotaYandexOTG |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 06:15 | 2,502 | -16 |
| 3 Sept 2026, 07:03 | 2,518 | +1 |
| 30 Aug 2026, 18:54 | 2,517 | +3 |
| 27 Aug 2026, 22:14 | 2,514 | +18 |
| 25 Aug 2026, 08:35 | 2,496 | -9 |
| 22 Aug 2026, 14:48 | 2,505 | +5 |
| 18 Aug 2026, 20:44 | 2,500 | +18 |
| 15 Aug 2026, 17:16 | 2,482 | +21 |
| 12 Aug 2026, 03:45 | 2,461 | +40 |
| 8 Aug 2026, 19:28 | 2,421 | +12 |
| 8 Aug 2026, 01:47 | 2,409 | first reading |
16 posts held, back to 7 June 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
Сборщик-комплектовщик (чистый склад одежды) На склад магазина одежды и обуви требуется "Сборщик заказов" Сделка - до 270 000 руб за месяц ✅ Берем без опыта, обучение на складе - работа простая но физическая. ✅ Жилье даем бесплатно - рядом хостел в 2х минутах ходьбы от склада. ✅ Проезд до места работы - организуем купим билет! Все организовано для Вас - только осталось приехать и заработать! Что делать: Работа с…
Пишите менеджеру пожалуйста Расскажем все о работе Покажем процесс на видео Спрашивайте любой вопрос @OTGcompany
https://t.me/OTGcompany
💰 Хочешь заработать за 2 месяца сумму, которую дома копят полгода? ВАХТА В МОСКВЕ Работа на современном теплом складе 📦 Без опыта — всему научим Сколько можно заработать? 💵 Первые 2 смены — гарантированно 3900 ₽ Далее — сдельная оплата. ⚡Чем быстрее работаешь — тем больше получаешь. До 12 000 ₽ за смену До 420 000 ₽ за вахту 60 смен ❗Не обещаем одинаковую зарплату каждому. Заработок зависит от вашей скорости…
Кто готов пишите Остальные города тоже есть выезды
Шымкент Астана Выезд в пятницу ___________ Актобе Алматы Бишкек Выезд каждый день
Photo, posted without a caption
Video, posted without a caption
‼️ кто готов ЗАВТРА с Астаны - и Костанай выезжаем завтра вечером на Минивене Хотите начать зарабатывать, тогда не нужно откладывать Выезжаем завтра Пишите рформим выезд @annagotovchits
Video, posted without a caption
🚨🚨По всем вопросам обращайтесь к Игорю Наш рекрутер https://t.me/OTGcompany
НАШ Официальный сайт 👇 🌐 https://подработчики.рф
Showing the 12 most recent of 16 posts we hold for @rabotaYandexOTG. 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.
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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“Работа на СКЛАДЕ | Москва Яндекс” (@rabotaYandexOTG), 2,502 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/rabotaYandexOTG.
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.