обновили заявку, присылайте кандидатов на заселение, праздники прошли, хорошей рабочей недели.
Signed Евгений

Channel
@nasha_vahta
On this record: Topic · Growth · Engagement · Posts · Cite this entry
356subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001845685556 |
|---|---|
| Type | Channel |
| Username | @nasha_vahta |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/nasha_vahta |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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, 21:02 | 356 | -3 |
| 17 Sept 2026, 05:18 | 359 | -1 |
| 30 Aug 2026, 16:45 | 360 | -2 |
| 23 Aug 2026, 23:45 | 362 | -1 |
| 8 Aug 2026, 06:32 | 363 | no change |
| 7 Aug 2026, 16:11 | 363 | first reading |
20 posts held, back to 26 May 2025 — 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 20 posts for this entry, the most recent from 16 June 2025. An engagement rate over an empty window would be a number about nothing.
обновили заявку, присылайте кандидатов на заселение, праздники прошли, хорошей рабочей недели.
Signed Евгений
Всем хорошего дня 💙
File, posted without a caption
Заявка на сегодня без изменений
Всем адекватных кандидатов и хорошего дня!)
Извиняемся за задержку))
На Мишн Фуд и ФАН ФАН срочно требуются сотрудники На Мишн Фуд в Ступино есть место для СП Комиссия за кандидатов 22500
File, posted without a caption
Обновили заявку, присылайте заявки на СБ и заселение, всем продуктивного рабочего дня
Signed Евгений
Актуальная_заявка на 05.06.2025..xlsx
Signed Евгений
К сожалению сегодня не удается обновить заявку, однако имейте ввиду, что сейчас лето, на каждый из объектов можно приглашать людей и по заявке на 03.06.2025. Начался не сезон, люди нужны везде и всегда Всем хорошего дня 💙
File, posted without a caption
Showing the 12 most recent of 20 posts we hold for @nasha_vahta. 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.
“НАША ВАХТА” (@nasha_vahta), 356 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/nasha_vahta.
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.