Telegram RegisterThe public register of Telegram
Telegram profile photo for РАБОТА! Челябинск

Supergroup

РАБОТА! Челябинск

@rabota_4elaba

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

5,548members

+992 since we began measuring on 7 August 2026

50 online right now

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

Register entry

Telegram ID-1002046709544
TypeSupergroup
Username@rabota_4elaba
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 September 2026
Last confirmed live5 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/rabota_4elaba

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 13 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.

Growth

4,5545,5485,0517 August 2026 — 4,556 members8 August 2026 — 4,558 members11 August 2026 — 4,554 members15 August 2026 — 4,573 members17 August 2026 — 4,606 members20 August 2026 — 4,647 members24 August 2026 — 4,650 members27 August 2026 — 4,693 members30 August 2026 — 4,687 members2 September 2026 — 4,680 members2 September 2026 — 4,680 members7 September 2026 — 4,714 members11 September 2026 — 4,771 members15 September 2026 — 4,809 members27 September 2026 — 4,886 members5 October 2026 — 4,993 members11 October 2026 — 5,061 members15 October 2026 — 5,074 members18 October 2026 — 5,103 members20 October 2026 — 5,136 members23 October 2026 — 5,230 members27 October 2026 — 5,322 members30 October 2026 — 5,411 members2 November 2026 — 5,467 members5 November 2026 — 5,548 members7 August 20265 November 2026
25 measurements spanning 90 days, net +992. 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 4,405–5,697 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 25
Measured (UTC)MembersChange
5 Nov 2026, 06:465,548+81
2 Nov 2026, 11:465,467+56
30 Oct 2026, 12:545,411+89
27 Oct 2026, 07:395,322+92
23 Oct 2026, 22:095,230+94
20 Oct 2026, 19:005,136+33
18 Oct 2026, 04:115,103+29
15 Oct 2026, 01:315,074+13
11 Oct 2026, 12:415,061+68
5 Oct 2026, 12:364,993+107
27 Sept 2026, 14:014,886+77
15 Sept 2026, 19:394,809+38
11 Sept 2026, 18:174,771+57
7 Sept 2026, 14:184,714+34
2 Sept 2026, 21:484,680no change
2 Sept 2026, 14:554,680-7
30 Aug 2026, 22:244,687-6
27 Aug 2026, 17:344,693+43
24 Aug 2026, 14:174,650+3
20 Aug 2026, 21:554,647first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

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

“РАБОТА! Челябинск” (@rabota_4elaba), 5,548 members as measured 5 November 2026. Telegram Register, tgregister.com/channel/rabota_4elaba.

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.