Telegram RegisterThe public register of Telegram
Telegram profile photo for Jobs in Mumbai

Supergroup

Jobs in Mumbai

@mumbaijobs

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

4,997members

-187 since we began measuring on 6 August 2026

3 online right now

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

Register entry

Telegram ID-1001342641863
TypeSupergroup
Username@mumbaijobs
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded1 September 2026
Last confirmed live4 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/mumbaijobs

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

4,9975,1865,091.56 August 2026 — 5,184 members7 August 2026 — 5,186 members9 August 2026 — 5,174 members12 August 2026 — 5,151 members16 August 2026 — 5,152 members19 August 2026 — 5,134 members23 August 2026 — 5,128 members25 August 2026 — 5,120 members29 August 2026 — 5,128 members31 August 2026 — 5,126 members1 September 2026 — 5,126 members4 September 2026 — 5,131 members9 September 2026 — 5,099 members13 September 2026 — 5,082 members18 September 2026 — 5,079 members26 September 2026 — 5,100 members5 October 2026 — 5,079 members11 October 2026 — 5,091 members14 October 2026 — 5,108 members17 October 2026 — 5,110 members20 October 2026 — 5,059 members23 October 2026 — 5,051 members26 October 2026 — 5,037 members29 October 2026 — 5,019 members2 November 2026 — 5,003 members4 November 2026 — 4,997 members6 August 20264 November 2026
26 measurements spanning 91 days, net -187. 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,969–5,214 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 26
Measured (UTC)MembersChange
4 Nov 2026, 22:144,997-6
2 Nov 2026, 01:505,003-16
29 Oct 2026, 23:375,019-18
26 Oct 2026, 23:145,037-14
23 Oct 2026, 18:105,051-8
20 Oct 2026, 12:185,059-51
17 Oct 2026, 22:155,110+2
14 Oct 2026, 18:315,108+17
11 Oct 2026, 03:205,091+12
5 Oct 2026, 07:015,079-21
26 Sept 2026, 18:195,100+21
18 Sept 2026, 03:025,079-3
13 Sept 2026, 15:415,082-17
9 Sept 2026, 23:005,099-32
4 Sept 2026, 20:565,131+5
1 Sept 2026, 11:475,126no change
31 Aug 2026, 21:265,126-2
29 Aug 2026, 01:165,128+8
25 Aug 2026, 19:125,120-8
23 Aug 2026, 01:435,128first 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 4 November 2026 — this entry's latest reading, not the date you are reading this.

“Jobs in Mumbai” (@mumbaijobs), 4,997 members as measured 4 November 2026. Telegram Register, tgregister.com/channel/mumbaijobs.

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.