Channel
upscupdates2026
@UPSCupdates2026
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3subscribers
-6,363 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001588994493 |
|---|---|
| Type | Channel |
| Username | @UPSCupdates2026 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 22 October 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 2 times, most recently 22 October 2026 |
| On Telegram | t.me/UPSCupdates2026 |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 15 Oct 2026, 13:40 | 3 | -6,331 |
| 11 Sept 2026, 03:38 | 6,334 | -8 |
| 6 Sept 2026, 15:37 | 6,342 | -3 |
| 2 Sept 2026, 08:22 | 6,345 | -10 |
| 30 Aug 2026, 05:56 | 6,355 | -3 |
| 28 Aug 2026, 21:32 | 6,358 | no change |
| 26 Aug 2026, 21:55 | 6,358 | -2 |
| 23 Aug 2026, 15:07 | 6,360 | +2 |
| 20 Aug 2026, 08:58 | 6,358 | -5 |
| 17 Aug 2026, 10:07 | 6,363 | -3 |
| 16 Aug 2026, 08:30 | 6,366 | 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.
@civilaspirantsankhla · 46,836
Telegram ranks this channel #4 of 73 here — alongside 72 others — read 26 August 2026
@o2ias · 22,528
Telegram ranks this channel #7 of 53 here — alongside 52 others — read 21 September 2026
@CryptoNews_proo · 47,052
Telegram ranks this channel #7 of 53 here — alongside 52 others — read 25 August 2026
@iasips_mentor · 82,906
Telegram ranks this channel #42 of 85 here — alongside 84 others — read 18 August 2026
@Studyiaswithdharmendrajakhar · 94,197
Telegram ranks this channel #54 of 77 here — alongside 76 others — read 16 August 2026
@UPSC_Prelims_Free_Test_Series · 51,910
Telegram ranks this channel #59 of 86 here — alongside 85 others — read 24 August 2026
@UH_Dailyquiz · 36,402
Telegram ranks this channel #60 of 65 here — alongside 64 others — read 1 September 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 15 October 2026 — this entry's latest reading, not the date you are reading this.
“upscupdates2026” (@UPSCupdates2026), 3 subscribers as measured 15 October 2026. Telegram Register, tgregister.com/channel/UPSCupdates2026.
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.