Channel
Rajyaseva Pre and Mains
@rajyasevatarget
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,624subscribers
-2 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001222993403 |
|---|---|
| Type | Channel |
| Username | @rajyasevatarget |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/rajyasevatarget |
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 15 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 |
|---|---|---|
| 19 Sept 2026, 07:16 | 2,624 | -7 |
| 14 Sept 2026, 14:39 | 2,631 | no change |
| 14 Sept 2026, 12:38 | 2,631 | -5 |
| 11 Sept 2026, 02:38 | 2,636 | +7 |
| 6 Sept 2026, 04:16 | 2,629 | +3 |
| 1 Sept 2026, 20:08 | 2,626 | +1 |
| 29 Aug 2026, 22:55 | 2,625 | +9 |
| 27 Aug 2026, 04:53 | 2,616 | -4 |
| 24 Aug 2026, 10:34 | 2,620 | -4 |
| 20 Aug 2026, 22:23 | 2,624 | -2 |
| 17 Aug 2026, 10:30 | 2,626 | 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.
@ShingareGSAcademy · 37,085
Telegram ranks this channel #9 of 68 here — alongside 67 others — read 1 September 2026
@sanjaypahadesir · 41,389
Telegram ranks this channel #10 of 64 here — alongside 63 others — read 29 August 2026
@MPSCEnglish · 54,418
Telegram ranks this channel #12 of 76 here — alongside 75 others — read 23 August 2026
@bhagirathacademypune · 45,257
Telegram ranks this channel #20 of 82 here — alongside 81 others — read 27 August 2026
@jobkatta · 40,018
Telegram ranks this channel #29 of 67 here — alongside 66 others — read 30 August 2026
@ChougulePramod · 32,731
Telegram ranks this channel #74 of 79 here — alongside 78 others — read 4 September 2026
@vidharbhaiasacadamy · 94,389
Telegram ranks this channel #83 of 93 here — alongside 92 others — read 17 August 2026
This channel appears in 7 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Rajyaseva Pre and Mains” (@rajyasevatarget), 2,624 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/rajyasevatarget.
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.