
Channel
NEET JEE NOTES 2026
@NEET_JEE_NOTES_2026
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,984subscribers
-180 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002248466541 |
|---|---|
| Type | Channel |
| Username | @NEET_JEE_NOTES_2026 |
| Created | Between 1 May 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/NEET_JEE_NOTES_2026 |
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 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 07:01 | 4,984 | -9 |
| 12 Sept 2026, 20:39 | 4,993 | -28 |
| 9 Sept 2026, 00:57 | 5,021 | -27 |
| 3 Sept 2026, 10:46 | 5,048 | -24 |
| 1 Sept 2026, 12:26 | 5,072 | no change |
| 30 Aug 2026, 23:38 | 5,072 | -15 |
| 28 Aug 2026, 01:52 | 5,087 | -10 |
| 24 Aug 2026, 20:08 | 5,097 | -15 |
| 20 Aug 2026, 20:23 | 5,112 | -6 |
| 17 Aug 2026, 17:25 | 5,118 | -19 |
| 14 Aug 2026, 13:34 | 5,137 | -9 |
| 10 Aug 2026, 22:09 | 5,146 | -14 |
| 8 Aug 2026, 02:17 | 5,160 | -4 |
| 7 Aug 2026, 18:34 | 5,164 | 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.
@alpha_study_squad · 108,256
Telegram ranks this channel #16 of 17 here — alongside 16 others — read 14 August 2026
@Notes_Class_11th_12th_Science · 50,510
Telegram ranks this channel #17 of 56 here — alongside 55 others — read 25 August 2026
@NEET_JEE_Cbse_Notes_Pyq · 52,229
Telegram ranks this channel #24 of 30 here — alongside 29 others — read 24 August 2026
@TaniyaSharmaEnglishOfficial · 67,399
Telegram ranks this channel #49 of 54 here — alongside 53 others — read 20 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total, of which the 4 where it ranks highest are shown above. 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“NEET JEE NOTES 2026” (@NEET_JEE_NOTES_2026), 4,984 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/NEET_JEE_NOTES_2026.
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.