Channel
Knowledge with notes (Pharmacy)
@pharmacypk
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,222subscribers
-45 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001402796014 |
|---|---|
| Type | Channel |
| Username | @pharmacypk |
| Created | Between 1 February 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/pharmacypk |
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 18 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 |
|---|---|---|
| 2 Nov 2026, 04:58 | 2,222 | -2 |
| 30 Oct 2026, 04:45 | 2,224 | -5 |
| 26 Oct 2026, 20:58 | 2,229 | +2 |
| 23 Oct 2026, 22:56 | 2,227 | -5 |
| 21 Oct 2026, 09:39 | 2,232 | -3 |
| 18 Oct 2026, 09:46 | 2,235 | -2 |
| 12 Oct 2026, 22:37 | 2,237 | -1 |
| 6 Oct 2026, 13:40 | 2,238 | -4 |
| 29 Sept 2026, 23:39 | 2,242 | -13 |
| 18 Sept 2026, 01:14 | 2,255 | no change |
| 12 Sept 2026, 17:39 | 2,255 | -4 |
| 9 Sept 2026, 00:18 | 2,259 | -3 |
| 3 Sept 2026, 10:01 | 2,262 | -6 |
| 31 Aug 2026, 10:05 | 2,268 | +1 |
| 27 Aug 2026, 05:15 | 2,267 | 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.
@pksmpsclasses · 42,594
Telegram ranks this channel #19 of 81 here — alongside 80 others — read 28 August 2026
@pharmacywala15M · 23,652
Telegram ranks this channel #25 of 57 here — alongside 56 others — read 17 September 2026
@carewellpharma · 139,035
Telegram ranks this channel #25 of 80 here — alongside 79 others — read 27 August 2026
@imperfectpharmacy · 122,910
Telegram ranks this channel #44 of 79 here — alongside 78 others — read 9 September 2026
@pharmacology2017 · 32,042
Telegram ranks this channel #69 of 80 here — alongside 79 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.
“Knowledge with notes (Pharmacy)” (@pharmacypk), 2,222 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/pharmacypk.
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.