Channel
MSc Chemistry Notes PDF's👩🔬 HPU Shimla
@DP_MSc
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,847subscribers
+53 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001533396516 |
|---|---|
| Type | Channel |
| Username | @DP_MSc |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 23 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/DP_MSc |
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 23 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 |
|---|---|---|
| 7 Nov 2026, 00:00 | 1,847 | -3 |
| 4 Nov 2026, 00:01 | 1,850 | +3 |
| 29 Oct 2026, 11:19 | 1,847 | -3 |
| 26 Oct 2026, 05:37 | 1,850 | +3 |
| 23 Oct 2026, 14:00 | 1,847 | +2 |
| 20 Oct 2026, 13:44 | 1,845 | -2 |
| 17 Oct 2026, 07:46 | 1,847 | -1 |
| 14 Oct 2026, 07:47 | 1,848 | +4 |
| 10 Oct 2026, 15:19 | 1,844 | -2 |
| 4 Oct 2026, 20:40 | 1,846 | +11 |
| 25 Sept 2026, 15:41 | 1,835 | +8 |
| 23 Sept 2026, 01:34 | 1,827 | no change |
| 17 Sept 2026, 05:57 | 1,827 | -2 |
| 13 Sept 2026, 02:39 | 1,829 | +4 |
| 8 Sept 2026, 23:17 | 1,825 | +13 |
| 3 Sept 2026, 06:13 | 1,812 | +6 |
| 30 Aug 2026, 15:56 | 1,806 | +3 |
| 25 Aug 2026, 05:28 | 1,803 | +2 |
| 21 Aug 2026, 23:37 | 1,801 | +5 |
| 18 Aug 2026, 20:47 | 1,796 | 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.
@Unacademyofficialss · 153,451
Telegram ranks this channel #54 of 71 here — alongside 70 others — read 12 August 2026
@hpexamaffairs · 30,158
Telegram ranks this channel #61 of 68 here — alongside 67 others — read 7 September 2026
@UGC_NET_JRF_1st_Papers · 4
Telegram ranks this channel #63 of 78 here — alongside 77 others — read 12 August 2026
@UGC_NET_JRF_NTA_CSIR_SO · 144,089
Telegram ranks this channel #69 of 78 here — alongside 77 others — read 12 August 2026
This channel appears in 4 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“MSc Chemistry Notes PDF's👩🔬 HPU Shimla” (@DP_MSc), 1,847 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/DP_MSc.
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.