Channel
Eklavya Batch VMC
@EklavyaVMC
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
986subscribers
-6 since we began measuring on 3 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002087162248 |
|---|---|
| Type | Channel |
| Username | @EklavyaVMC |
| Description | For Workbook, Workshop & Question Wise Video Solution: https://t.me/+3ceVJm0eqfVhZGQ1 Must Checkout for more such content : https://genetry.carrd.co |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 October 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 5 |
| On Telegram | t.me/EklavyaVMC |
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 9 October 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Oct 2026, 05:30 | 986 | no change |
| 7 Oct 2026, 06:39 | 986 | -2 |
| 13 Sept 2026, 23:41 | 988 | -3 |
| 5 Sept 2026, 13:38 | 991 | -1 |
| 3 Sept 2026, 23:17 | 992 | 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.
@unacademyatoms · 28,107
Telegram ranks this channel #11 of 62 here — alongside 61 others — read 9 September 2026
@Etoos_Lectures1 · 58,087
Telegram ranks this channel #14 of 44 here — alongside 43 others — read 26 September 2026
@IIT_JEE_2026_Test_Series · 19,614
Telegram ranks this channel #26 of 51 here — alongside 50 others — read 1 October 2026
@IIT_JEE_Mains_2026_Test_Series · 18,949
Telegram ranks this channel #38 of 45 here — alongside 44 others — read 4 October 2026
@skm_chemistry_lectures · 20,633
Telegram ranks this channel #41 of 57 here — alongside 56 others — read 26 September 2026
@resonance_Modules_lectures · 21,378
Telegram ranks this channel #42 of 52 here — alongside 51 others — read 24 September 2026
@amarnathanandsir · 20,045
Telegram ranks this channel #48 of 62 here — alongside 61 others — read 1 October 2026
@namochat · 33,240
Telegram ranks this channel #58 of 66 here — alongside 65 others — read 3 September 2026
This channel appears in 8 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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“Eklavya Batch VMC” (@EklavyaVMC), 986 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/EklavyaVMC.
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.