Telegram RegisterThe public register of Telegram
Telegram profile photo for Ish Moscow | Vakansiya

Supergroup

Ish Moscow | Vakansiya

@moscow_vakansiya

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

3,810members

-34 since we began measuring on 8 August 2026

71 online right now

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

Register entry

Telegram ID-1002180413212
TypeSupergroup
Username@moscow_vakansiya
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 September 2026
Last confirmed live17 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/moscow_vakansiya

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

3,8073,8443,825.58 August 2026 — 3,844 members9 August 2026 — 3,836 members12 August 2026 — 3,835 members16 August 2026 — 3,817 members19 August 2026 — 3,823 members22 August 2026 — 3,810 members25 August 2026 — 3,807 members28 August 2026 — 3,817 members31 August 2026 — 3,812 members4 September 2026 — 3,820 members6 September 2026 — 3,820 members10 September 2026 — 3,825 members13 September 2026 — 3,826 members17 September 2026 — 3,810 members3,8108 August 202617 September 2026
14 measurements spanning 40 days, net -34. 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 3,801–3,850 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
17 Sept 2026, 22:163,810-16
13 Sept 2026, 15:173,826+1
10 Sept 2026, 02:013,825+5
6 Sept 2026, 13:403,820no change
4 Sept 2026, 10:593,820+8
31 Aug 2026, 19:053,812-5
28 Aug 2026, 17:543,817+10
25 Aug 2026, 12:233,807-3
22 Aug 2026, 18:443,810-13
19 Aug 2026, 17:123,823+6
16 Aug 2026, 15:133,817-18
12 Aug 2026, 13:543,835-1
9 Aug 2026, 10:083,836-8
8 Aug 2026, 12:163,844first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“Ish Moscow | Vakansiya” (@moscow_vakansiya), 3,810 members as measured 17 September 2026. Telegram Register, tgregister.com/channel/moscow_vakansiya.

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.