Channel
NDA Maths by Akhil Roy Unacademy
@Akhil_Roy_Maths
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,084subscribers
-125 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002000267608 |
|---|---|
| Type | Channel |
| Username | @Akhil_Roy_Maths |
| Created | Between 1 November 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Akhil_Roy_Maths |
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 96% 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, 04:15 | 4,084 | -17 |
| 13 Sept 2026, 14:40 | 4,101 | -17 |
| 9 Sept 2026, 22:14 | 4,118 | -12 |
| 4 Sept 2026, 23:11 | 4,130 | no change |
| 4 Sept 2026, 21:36 | 4,130 | -15 |
| 1 Sept 2026, 05:25 | 4,145 | -15 |
| 29 Aug 2026, 09:25 | 4,160 | -3 |
| 26 Aug 2026, 14:53 | 4,163 | -13 |
| 24 Aug 2026, 00:25 | 4,176 | -4 |
| 20 Aug 2026, 05:52 | 4,180 | -12 |
| 16 Aug 2026, 20:45 | 4,192 | -15 |
| 13 Aug 2026, 15:06 | 4,207 | -2 |
| 13 Aug 2026, 11:03 | 4,209 | 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.
@Chemistrybyvikrantsir · 45,106
Telegram ranks this channel #10 of 37 here — alongside 36 others — read 27 August 2026
@pwdefencewallah · 135,858
Telegram ranks this channel #15 of 40 here — alongside 39 others — read 13 August 2026
@Currentaffairsbyaasimsir · 37,800
Telegram ranks this channel #19 of 40 here — alongside 39 others — read 31 August 2026
@soumyamaam_defencewallah · 34,845
Telegram ranks this channel #20 of 32 here — alongside 31 others — read 2 September 2026
@rahulsir_defencewallah · 64,720
Telegram ranks this channel #20 of 42 here — alongside 41 others — read 21 August 2026
This channel appears in 5 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“NDA Maths by Akhil Roy Unacademy” (@Akhil_Roy_Maths), 4,084 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Akhil_Roy_Maths.
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.