Channel
Job Opportunities by Urvashi Rajai Amarvani
@jobopportunities24
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,740subscribers
-193 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001219470448 |
|---|---|
| Type | Channel |
| Username | @jobopportunities24 |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/jobopportunities24 |
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 100% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 23:40 | 4,740 | -8 |
| 2 Nov 2026, 16:49 | 4,748 | -8 |
| 30 Oct 2026, 16:26 | 4,756 | -6 |
| 27 Oct 2026, 15:06 | 4,762 | -15 |
| 20 Oct 2026, 22:04 | 4,777 | -10 |
| 17 Oct 2026, 23:16 | 4,787 | -15 |
| 14 Oct 2026, 21:47 | 4,802 | -3 |
| 11 Oct 2026, 21:21 | 4,805 | -22 |
| 4 Oct 2026, 22:42 | 4,827 | -13 |
| 26 Sept 2026, 01:56 | 4,840 | -34 |
| 17 Sept 2026, 04:18 | 4,874 | -7 |
| 12 Sept 2026, 20:20 | 4,881 | -7 |
| 9 Sept 2026, 03:35 | 4,888 | -7 |
| 3 Sept 2026, 10:05 | 4,895 | -8 |
| 1 Sept 2026, 22:33 | 4,903 | no change |
| 31 Aug 2026, 00:55 | 4,903 | -11 |
| 27 Aug 2026, 19:46 | 4,914 | -3 |
| 25 Aug 2026, 01:39 | 4,917 | -14 |
| 21 Aug 2026, 09:35 | 4,931 | -2 |
| 20 Aug 2026, 19:30 | 4,933 | first 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@linktopusjobupdates · 64,276
Telegram ranks this channel #1 of 79 here — alongside 78 others — read 20 August 2026
@camonk8 · 27,221
Telegram ranks this channel #23 of 80 here — alongside 79 others — read 10 September 2026
@Jobs4CA · 44,094
Telegram ranks this channel #25 of 97 here — alongside 96 others — read 28 August 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“Job Opportunities by Urvashi Rajai Amarvani” (@jobopportunities24), 4,740 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/jobopportunities24.
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.