Channel
JEE mains + jee advanced 2024 , 2025 & 2026
@JEE_mains_Advanced_2024_Paper
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,163subscribers
-17 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001951500554 |
|---|---|
| Type | Channel |
| Username | @JEE_mains_Advanced_2024_Paper |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 October 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 5 October 2026 |
| On Telegram | t.me/JEE_mains_Advanced_2024_Paper |
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 5 October 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 05:56 | 1,163 | -5 |
| 5 Oct 2026, 03:53 | 1,168 | no change |
| 27 Sept 2026, 03:21 | 1,168 | -5 |
| 17 Sept 2026, 21:17 | 1,173 | -6 |
| 14 Sept 2026, 03:36 | 1,179 | -5 |
| 10 Sept 2026, 09:59 | 1,184 | +2 |
| 5 Sept 2026, 09:00 | 1,182 | -1 |
| 1 Sept 2026, 15:12 | 1,183 | -2 |
| 29 Aug 2026, 08:34 | 1,185 | +10 |
| 26 Aug 2026, 07:06 | 1,175 | -2 |
| 23 Aug 2026, 16:37 | 1,177 | +1 |
| 20 Aug 2026, 11:13 | 1,176 | -5 |
| 17 Aug 2026, 12:17 | 1,181 | +1 |
| 16 Aug 2026, 02:45 | 1,180 | 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.
@IIT_JEENOTES · 61,833
Telegram ranks this channel #7 of 54 here — alongside 53 others — read 21 August 2026
@IITJEE_Advanced · 20,902
Telegram ranks this channel #14 of 53 here — alongside 52 others — read 27 September 2026
@IIT_JEE_Mains_Advance_Materials · 92,763
Telegram ranks this channel #27 of 58 here — alongside 57 others — read 16 August 2026
@PW_Arjuna_JEE_Batch_Lecture_2026 · 31,941
Telegram ranks this channel #33 of 36 here — alongside 35 others — read 2 September 2026
This channel appears in 4 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 October 2026 — this entry's latest reading, not the date you are reading this.
“JEE mains + jee advanced 2024 , 2025 & 2026” (@JEE_mains_Advanced_2024_Paper), 1,163 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/JEE_mains_Advanced_2024_Paper.
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.