Channel
PSIR with Anuj Sharma | Polity + IR
@PSIRbyAnujjSharma
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,042subscribers
-14 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001751582784 |
|---|---|
| Type | Channel |
| Username | @PSIRbyAnujjSharma |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/PSIRbyAnujjSharma |
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 20 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 11:29 | 2,042 | -3 |
| 2 Nov 2026, 04:51 | 2,045 | -5 |
| 24 Oct 2026, 11:35 | 2,050 | -1 |
| 21 Oct 2026, 08:16 | 2,051 | +1 |
| 18 Oct 2026, 00:58 | 2,050 | +3 |
| 15 Oct 2026, 06:08 | 2,047 | -3 |
| 12 Oct 2026, 11:52 | 2,050 | -9 |
| 5 Oct 2026, 15:15 | 2,059 | -8 |
| 28 Sept 2026, 02:19 | 2,067 | +4 |
| 20 Sept 2026, 02:17 | 2,063 | no change |
| 18 Sept 2026, 22:59 | 2,063 | -3 |
| 10 Sept 2026, 23:36 | 2,066 | -2 |
| 6 Sept 2026, 00:57 | 2,068 | +4 |
| 1 Sept 2026, 13:38 | 2,064 | +5 |
| 29 Aug 2026, 09:06 | 2,059 | +3 |
| 25 Aug 2026, 19:45 | 2,056 | 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.
@excelcivilsacademy · 15,623
Telegram ranks this channel #1 of 70 here — alongside 69 others — read 2 October 2026
@rajmalhotraias · 38,264
Telegram ranks this channel #1 of 78 here — alongside 77 others — read 30 August 2026
@alljobforyou · 25,941
Telegram ranks this channel #26 of 57 here — alongside 56 others — read 11 September 2026
@caiibwithashok · 58,995
Telegram ranks this channel #39 of 60 here — alongside 59 others — read 31 August 2026
@UPSC_Previous_Year_Papers · 47,325
Telegram ranks this channel #61 of 91 here — alongside 90 others — read 25 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“PSIR with Anuj Sharma | Polity + IR” (@PSIRbyAnujjSharma), 2,042 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/PSIRbyAnujjSharma.
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.