Channel
HP Public Service Commission
@HPPSC
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
8,416subscribers
+33 since we began measuring on 1 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001056498480 |
|---|---|
| Type | Channel |
| Username | @HPPSC |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 19 October 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 19 October 2026 |
| On Telegram | t.me/HPPSC |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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 Oct 2026, 07:06 | 8,416 | +3 |
| 15 Oct 2026, 20:45 | 8,413 | +5 |
| 5 Oct 2026, 16:17 | 8,408 | +2 |
| 28 Sept 2026, 03:16 | 8,406 | +1 |
| 18 Sept 2026, 06:58 | 8,405 | +5 |
| 13 Sept 2026, 19:56 | 8,400 | +2 |
| 10 Sept 2026, 05:01 | 8,398 | +7 |
| 5 Sept 2026, 02:00 | 8,391 | +9 |
| 1 Sept 2026, 18:42 | 8,382 | no change |
| 1 Sept 2026, 16:08 | 8,382 | -1 |
| 1 Sept 2026, 15:30 | 8,383 | 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.
@hpexamaffairs · 30,211
Telegram ranks this channel #8 of 68 here — alongside 67 others — read 7 September 2026
@himachalpradeshgk · 23,296
Telegram ranks this channel #9 of 71 here — alongside 70 others — read 18 September 2026
@o2ias · 22,528
Telegram ranks this channel #19 of 53 here — alongside 52 others — read 21 September 2026
@allexam31 · 36,764
Telegram ranks this channel #30 of 67 here — alongside 66 others — read 1 September 2026
@dtemagazine · 46,726
Telegram ranks this channel #33 of 65 here — alongside 64 others — read 4 September 2026
@geography_5 · 26,744
Telegram ranks this channel #51 of 54 here — alongside 53 others — read 11 September 2026
@Obs_gynee · 25,334
Telegram ranks this channel #69 of 70 here — alongside 69 others — read 26 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 19 October 2026 — this entry's latest reading, not the date you are reading this.
“HP Public Service Commission” (@HPPSC), 8,416 subscribers as measured 19 October 2026. Telegram Register, tgregister.com/channel/HPPSC.
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.