Telegram RegisterThe public register of Telegram
Telegram profile photo for Официанты Тюмень | Работа в ресторане, свежие вакансии, резюме, подработка в общепите, чат

Supergroup

Официанты Тюмень | Работа в ресторане, свежие вакансии, резюме, подработка в общепите, чат

@ofitsianty_tyumen_rabota_chat

On this record: Topic · Growth · Engagement · Cite this entry

9,895members

+1,686 since we began measuring on 7 August 2026

18 online right now

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001940061784
TypeSupergroup
Username@ofitsianty_tyumen_rabota_chat
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded24 August 2026
Last confirmed live18 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/ofitsianty_tyumen_rabota_chat

Topic

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 11 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.

Growth

8,2099,8959,0527 August 2026 — 8,209 members8 August 2026 — 8,222 members10 August 2026 — 8,296 members13 August 2026 — 8,421 members16 August 2026 — 8,555 members19 August 2026 — 8,700 members23 August 2026 — 8,796 members24 August 2026 — 8,796 members26 August 2026 — 8,855 members29 August 2026 — 8,975 members1 September 2026 — 9,104 members4 September 2026 — 9,283 members10 September 2026 — 9,533 members13 September 2026 — 9,650 members18 September 2026 — 9,895 members7 August 202618 September 2026
15 measurements spanning 42 days, net +1,686. 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 7,956–10,148 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
18 Sept 2026, 09:019,895+245
13 Sept 2026, 19:399,650+117
10 Sept 2026, 09:369,533+250
4 Sept 2026, 19:189,283+179
1 Sept 2026, 14:449,104+129
29 Aug 2026, 05:168,975+120
26 Aug 2026, 13:588,855+59
24 Aug 2026, 17:408,796no change
23 Aug 2026, 10:598,796+96
19 Aug 2026, 18:268,700+145
16 Aug 2026, 17:238,555+134
13 Aug 2026, 12:448,421+125
10 Aug 2026, 18:338,296+74
8 Aug 2026, 04:528,222+13
7 Aug 2026, 15:078,209first reading

Engagement

No public post preview. We read this entry on 24 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“Официанты Тюмень | Работа в ресторане, свежие вакансии, резюме, подработка в общепите, чат” (@ofitsianty_tyumen_rabota_chat), 9,895 members as measured 18 September 2026. Telegram Register, tgregister.com/channel/ofitsianty_tyumen_rabota_chat.

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.