Channel
UPSC Essay Videos
@shabbir_sir_upsc_essay_videos_gz
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,377subscribers
+2 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001951846660 |
|---|---|
| Type | Channel |
| Username | @shabbir_sir_upsc_essay_videos_gz |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/shabbir_sir_upsc_essay_videos_gz |
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 17 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 |
|---|---|---|
| 27 Sept 2026, 17:36 | 2,377 | -1 |
| 18 Sept 2026, 17:37 | 2,378 | +4 |
| 17 Sept 2026, 00:10 | 2,374 | no change |
| 13 Sept 2026, 23:37 | 2,374 | -2 |
| 10 Sept 2026, 02:40 | 2,376 | -4 |
| 4 Sept 2026, 20:56 | 2,380 | -3 |
| 1 Sept 2026, 13:17 | 2,383 | +3 |
| 29 Aug 2026, 06:34 | 2,380 | +5 |
| 26 Aug 2026, 01:26 | 2,375 | -4 |
| 23 Aug 2026, 00:35 | 2,379 | +4 |
| 19 Aug 2026, 04:45 | 2,375 | 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.
@upsc_cse_prelims_mains_notes · 74,371
Telegram ranks this channel #5 of 57 here — alongside 56 others — read 19 August 2026
@amritaIAS · 22,033
Telegram ranks this channel #7 of 49 here — alongside 48 others — read 21 September 2026
@upsc_ias_hindi_notes · 76,659
Telegram ranks this channel #23 of 63 here — alongside 62 others — read 19 August 2026
@Harpreet_pwupscwallah · 21,704
Telegram ranks this channel #24 of 67 here — alongside 66 others — read 22 September 2026
@gaursepadho · 32,789
Telegram ranks this channel #32 of 63 here — alongside 62 others — read 5 September 2026
@SGS_IAS · 31,487
Telegram ranks this channel #38 of 50 here — alongside 49 others — read 5 September 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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“UPSC Essay Videos” (@shabbir_sir_upsc_essay_videos_gz), 2,377 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/shabbir_sir_upsc_essay_videos_gz.
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.