Channel
VMOU Helpline (vardhman mahaveer open university kota) 😊
@vmouhelpdesk
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,499subscribers
+20 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001353848800 |
|---|---|
| Type | Channel |
| Username | @vmouhelpdesk |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/vmouhelpdesk |
Topic
Education — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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, 02:24 | 2,499 | -4 |
| 1 Nov 2026, 22:56 | 2,503 | +2 |
| 29 Oct 2026, 21:31 | 2,501 | +5 |
| 27 Oct 2026, 06:16 | 2,496 | +4 |
| 24 Oct 2026, 01:58 | 2,492 | +2 |
| 20 Oct 2026, 23:59 | 2,490 | -3 |
| 18 Oct 2026, 08:28 | 2,493 | -2 |
| 15 Oct 2026, 10:39 | 2,495 | -1 |
| 12 Oct 2026, 16:09 | 2,496 | +7 |
| 5 Oct 2026, 14:57 | 2,489 | +8 |
| 27 Sept 2026, 16:01 | 2,481 | -5 |
| 18 Sept 2026, 03:55 | 2,486 | +4 |
| 16 Sept 2026, 00:06 | 2,482 | no change |
| 13 Sept 2026, 17:56 | 2,482 | -2 |
| 10 Sept 2026, 05:15 | 2,484 | +5 |
| 4 Sept 2026, 16:41 | 2,479 | +1 |
| 1 Sept 2026, 04:07 | 2,478 | -3 |
| 28 Aug 2026, 18:16 | 2,481 | +2 |
| 25 Aug 2026, 17:23 | 2,479 | +1 |
| 22 Aug 2026, 15:26 | 2,478 | 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.
@vmoueducationjobhelpline · 40,296
Telegram ranks this channel #2 of 64 here — alongside 63 others — read 29 August 2026
@rcbkr · 24,770
Telegram ranks this channel #5 of 68 here — alongside 67 others — read 15 September 2026
@vmou_kota_university · 63,889
Telegram ranks this channel #6 of 83 here — alongside 82 others — read 21 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.
“VMOU Helpline (vardhman mahaveer open university kota) 😊” (@vmouhelpdesk), 2,499 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/vmouhelpdesk.
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.