Channel
𝟸ɴᴅ ɢʀᴀᴅᴇ ᴍᴀᴛʜs
@RPSC_2nd_Grade_Mathematics
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,092subscribers
-17 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002067937727 |
|---|---|
| Type | Channel |
| Username | @RPSC_2nd_Grade_Mathematics |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/RPSC_2nd_Grade_Mathematics |
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 14 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 |
|---|---|---|
| 18 Sept 2026, 17:58 | 3,092 | -1 |
| 14 Sept 2026, 00:36 | 3,093 | -5 |
| 10 Sept 2026, 23:16 | 3,098 | no change |
| 10 Sept 2026, 10:18 | 3,098 | -1 |
| 5 Sept 2026, 07:54 | 3,099 | +2 |
| 1 Sept 2026, 02:45 | 3,097 | -6 |
| 26 Aug 2026, 01:47 | 3,103 | -4 |
| 23 Aug 2026, 08:07 | 3,107 | -5 |
| 19 Aug 2026, 13:34 | 3,112 | +3 |
| 18 Aug 2026, 20:15 | 3,109 | 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.
@Theperfectstudyofficial · 27,673
Telegram ranks this channel #38 of 54 here — alongside 53 others — read 11 September 2026
@rpscoldpaper · 24,111
Telegram ranks this channel #46 of 60 here — alongside 59 others — read 17 September 2026
@khembeniwalrank24 · 26,310
Telegram ranks this channel #46 of 57 here — alongside 56 others — read 12 September 2026
@sankalponline · 57,400
Telegram ranks this channel #52 of 73 here — alongside 72 others — read 23 August 2026
@UniAlerts_BKN · 79,769
Telegram ranks this channel #67 of 86 here — alongside 85 others — read 18 August 2026
@GkGajanandsir · 53,498
Telegram ranks this channel #69 of 69 here — alongside 68 others — read 24 August 2026
This channel appears in 6 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“𝟸ɴᴅ ɢʀᴀᴅᴇ ᴍᴀᴛʜs” (@RPSC_2nd_Grade_Mathematics), 3,092 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/RPSC_2nd_Grade_Mathematics.
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.