Telegram RegisterThe public register of Telegram
Telegram profile photo for Работа в Санкт-Петербурге

Supergroup

Работа в Санкт-Петербурге

@r_piter

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

2,040members

+135 since we began measuring on 7 August 2026

79 online right now

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

Register entry

Telegram ID-1001342309865
TypeSupergroup
Username@r_piter
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 September 2026
Last confirmed live15 November 2026
Measurements held25
Confirmed unchanged3 times, most recently 15 November 2026
On Telegramt.me/r_piter

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

1,8922,0401,9667 August 2026 — 1,905 members7 August 2026 — 1,909 members11 August 2026 — 1,892 members14 August 2026 — 1,903 members17 August 2026 — 1,920 members21 August 2026 — 1,928 members24 August 2026 — 1,934 members27 August 2026 — 1,937 members2 September 2026 — 1,951 members7 September 2026 — 1,983 members12 September 2026 — 2,017 members16 September 2026 — 2,029 members20 September 2026 — 2,029 members24 September 2026 — 2,038 members4 October 2026 — 2,035 members10 October 2026 — 2,026 members14 October 2026 — 2,025 members17 October 2026 — 2,027 members20 October 2026 — 2,019 members23 October 2026 — 2,037 members25 October 2026 — 2,031 members28 October 2026 — 2,033 members31 October 2026 — 2,019 members3 November 2026 — 2,031 members6 November 2026 — 2,040 members7 August 20266 November 2026
25 measurements spanning 92 days, net +135. 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 1,870–2,062 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 25
Measured (UTC)MembersChange
6 Nov 2026, 20:152,040+9
3 Nov 2026, 20:452,031+12
31 Oct 2026, 11:472,019-14
28 Oct 2026, 07:352,033+2
25 Oct 2026, 17:352,031-6
23 Oct 2026, 03:562,037+18
20 Oct 2026, 11:512,019-8
17 Oct 2026, 09:372,027+2
14 Oct 2026, 10:512,025-1
10 Oct 2026, 13:172,026-9
4 Oct 2026, 20:192,035-3
24 Sept 2026, 22:402,038+9
20 Sept 2026, 15:542,029no change
16 Sept 2026, 09:182,029+12
12 Sept 2026, 06:172,017+34
7 Sept 2026, 20:181,983+32
2 Sept 2026, 17:251,951+14
27 Aug 2026, 08:221,937+3
24 Aug 2026, 18:051,934+6
21 Aug 2026, 03:021,928first 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 November 2026 — this entry's latest reading, not the date you are reading this.

“Работа в Санкт-Петербурге” (@r_piter), 2,040 members as measured 6 November 2026. Telegram Register, tgregister.com/channel/r_piter.

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.