Telegram RegisterThe public register of Telegram
Telegram profile photo for Сланцы Работа | Подработка

Channel

Сланцы Работа | Подработка

@rabotat_slantsy

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

13subscribers

-1,114 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003923699910
TypeChannel
Username@rabotat_slantsy
CreatedBetween 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 October 2026
Last confirmed live6 October 2026
Measurements held13
Confirmed unchanged1 time, most recently 6 October 2026
On Telegramt.me/rabotat_slantsy

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 6 October 2026 and assigned it the closest of 31 fixed categories, at 89% 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

131,148580.57 August 2026 — 1,127 subscribers8 August 2026 — 1,129 subscribers17 August 2026 — 1,132 subscribers20 August 2026 — 1,137 subscribers24 August 2026 — 1,139 subscribers27 August 2026 — 1,138 subscribers30 August 2026 — 1,139 subscribers6 September 2026 — 1,142 subscribers10 September 2026 — 1,145 subscribers18 September 2026 — 1,148 subscribers28 September 2026 — 1,142 subscribers6 October 2026 — 1,142 subscribers6 October 2026 — 13 subscribers7 August 20266 October 2026
13 measurements spanning 60 days, net -1,114. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Oct 2026, 03:1713-1,129
6 Oct 2026, 01:211,142no change
28 Sept 2026, 21:421,142-6
18 Sept 2026, 18:571,148+3
10 Sept 2026, 21:161,145+3
6 Sept 2026, 04:411,142+3
30 Aug 2026, 12:491,139+1
27 Aug 2026, 02:541,138-1
24 Aug 2026, 08:181,139+2
20 Aug 2026, 13:521,137+5
17 Aug 2026, 20:441,132+3
8 Aug 2026, 05:511,129+2
7 Aug 2026, 13:431,127first 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 6 October 2026 — this entry's latest reading, not the date you are reading this.

“Сланцы Работа | Подработка” (@rabotat_slantsy), 13 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/rabotat_slantsy.

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.