Channel
@RABOTA_IRKUTSK_REZUME
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,754subscribers
-918 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002626698175 |
|---|---|
| Type | Channel |
| Username | @RABOTA_IRKUTSK_REZUME |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/RABOTA_IRKUTSK_REZUME |
Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 16 September 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 14:01 | 1,754 | -53 |
| 4 Oct 2026, 22:20 | 1,807 | -14 |
| 25 Sept 2026, 09:41 | 1,821 | -68 |
| 17 Sept 2026, 00:20 | 1,889 | -79 |
| 12 Sept 2026, 17:21 | 1,968 | -93 |
| 8 Sept 2026, 08:38 | 2,061 | -27 |
| 3 Sept 2026, 13:02 | 2,088 | -38 |
| 30 Aug 2026, 20:14 | 2,126 | -261 |
| 27 Aug 2026, 13:44 | 2,387 | -15 |
| 24 Aug 2026, 23:09 | 2,402 | -56 |
| 21 Aug 2026, 05:05 | 2,458 | -37 |
| 17 Aug 2026, 19:23 | 2,495 | -70 |
| 14 Aug 2026, 21:52 | 2,565 | -29 |
| 11 Aug 2026, 13:02 | 2,594 | -62 |
| 8 Aug 2026, 11:25 | 2,656 | -16 |
| 7 Aug 2026, 16:32 | 2,672 | no change |
| 7 Aug 2026, 16:28 | 2,672 | first reading |
1 post held, back to 7 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 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 1 post for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
❗️СРОЧНО ТРЕБУЮТСЯ КУРЬЕРЫ Партнер сервиса Яндекс Еда🍔 в поисках курьеров! Основная задача: ➖Доставка заказов из ресторанов наших партнеров. ✅Заполнить анкету: https://ya.cc/t/ufmm3NAcAMuQ9G Доход в день - зависит от количества выполненных доставок и указан без учета чаевых. 🏃♂️Пеший курьер - до 4500 руб/день 🚴♀️Велокурьер - до 7000 руб/день 🚗Автокурьер - до 8000 руб/день + БОНУСЫ 💰Выплаты - Ежедневно/Е…
Showing the 1 most recent of 1 post we hold for @RABOTA_IRKUTSK_REZUME. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“🚀 РАБОТА ИРКУТСК | ВАКАНСИИ И РЕЗЮМЕ” (@RABOTA_IRKUTSK_REZUME), 1,754 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/RABOTA_IRKUTSK_REZUME.
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.