Channel
upscpulse
@upscpulse
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,300subscribers
-107 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001684279044 |
|---|---|
| Type | Channel |
| Username | @upscpulse |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/upscpulse |
Topic
Other / unclassifiable — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 2 Nov 2026, 02:47 | 3,300 | -5 |
| 29 Oct 2026, 16:40 | 3,305 | -4 |
| 26 Oct 2026, 07:06 | 3,309 | -2 |
| 23 Oct 2026, 11:37 | 3,311 | -5 |
| 20 Oct 2026, 16:31 | 3,316 | -4 |
| 17 Oct 2026, 09:11 | 3,320 | -4 |
| 14 Oct 2026, 10:36 | 3,324 | -5 |
| 10 Oct 2026, 22:39 | 3,329 | -2 |
| 4 Oct 2026, 23:55 | 3,331 | -17 |
| 25 Sept 2026, 17:57 | 3,348 | -14 |
| 15 Sept 2026, 03:00 | 3,362 | -6 |
| 11 Sept 2026, 03:21 | 3,368 | -6 |
| 8 Sept 2026, 23:41 | 3,374 | no change |
| 5 Sept 2026, 19:00 | 3,374 | +2 |
| 1 Sept 2026, 10:34 | 3,372 | -3 |
| 29 Aug 2026, 06:27 | 3,375 | -2 |
| 25 Aug 2026, 22:37 | 3,377 | -1 |
| 23 Aug 2026, 08:16 | 3,378 | -10 |
| 20 Aug 2026, 02:22 | 3,388 | -5 |
| 16 Aug 2026, 21:48 | 3,393 | 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.
@Adityatiwarisir_upscwallah · 22,718
Telegram ranks this channel #7 of 43 here — alongside 42 others — read 20 September 2026
@Sumit_jaiswal_Quant · 21,502
Telegram ranks this channel #17 of 47 here — alongside 46 others — read 28 September 2026
@UPSC_Polity_PSIR_Notes · 33,200
Telegram ranks this channel #19 of 57 here — alongside 56 others — read 3 September 2026
@csewithsainilnagare · 74,838
Telegram ranks this channel #22 of 67 here — alongside 66 others — read 19 August 2026
@SGS_IAS · 32,787
Telegram ranks this channel #40 of 50 here — alongside 49 others — read 5 September 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“upscpulse” (@upscpulse), 3,300 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/upscpulse.
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.