Channel
જ્ઞાનઆરસી by Aastha Rajput🌅✍📚
@gyanaarsiofficial
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,998subscribers
-45 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001783836768 |
|---|---|
| Type | Channel |
| Username | @gyanaarsiofficial |
| Description | Aastha Rajput 👍 ✅GPSC Class 1/2 , Dy.SO, STI, PI, PSI-ASI, TET-TAT CCE (તલાટી, જૂ.ક્લાર્ક, બિન સચિવાલય) તથા કોન્સ્ટેબલ, વન રક્ષક વગેરે માટે ઉપયોગી... ✅Quiz : NCERT + GCERT અને માહિતી ખાતાની પુસ્તકો આધારિત હશે. |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 September 2026 |
| Last confirmed live | 21 September 2026 |
| Measurements held | 12 |
| On Telegram | t.me/gyanaarsiofficial |
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 21 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 |
|---|---|---|
| 21 Sept 2026, 01:07 | 1,998 | no change |
| 15 Sept 2026, 16:18 | 1,998 | -1 |
| 11 Sept 2026, 22:36 | 1,999 | -6 |
| 7 Sept 2026, 10:40 | 2,005 | -9 |
| 2 Sept 2026, 10:24 | 2,014 | -3 |
| 27 Aug 2026, 06:53 | 2,017 | -4 |
| 24 Aug 2026, 10:12 | 2,021 | -3 |
| 20 Aug 2026, 08:13 | 2,024 | -1 |
| 17 Aug 2026, 17:09 | 2,025 | -1 |
| 14 Aug 2026, 20:45 | 2,026 | -8 |
| 11 Aug 2026, 04:31 | 2,034 | -9 |
| 7 Aug 2026, 12:37 | 2,043 | 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.
@patiyaacademy · 26,900
Telegram ranks this channel #13 of 75 here — alongside 74 others — read 12 September 2026
@LakshyamAcademyofficial · 63,998
Telegram ranks this channel #36 of 68 here — alongside 67 others — read 26 August 2026
@gkbypradippatel · 33,340
Telegram ranks this channel #55 of 68 here — alongside 67 others — read 4 September 2026
@gpsc_examss · 25,872
Telegram ranks this channel #59 of 72 here — alongside 71 others — read 13 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 21 September 2026 — this entry's latest reading, not the date you are reading this.
“જ્ઞાનઆરસી by Aastha Rajput🌅✍📚” (@gyanaarsiofficial), 1,998 subscribers as measured 21 September 2026. Telegram Register, tgregister.com/channel/gyanaarsiofficial.
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.