Channel
Clinical with mohassed
@mohassedza
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,495subscribers
+33 since we began measuring on 8 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002156149473 |
|---|---|
| Type | Channel |
| Username | @mohassedza |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/mohassedza |
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 27 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 |
|---|---|---|
| 11 Nov 2026, 22:46 | 2,495 | +1 |
| 7 Nov 2026, 17:16 | 2,494 | +1 |
| 4 Nov 2026, 08:15 | 2,493 | +1 |
| 1 Nov 2026, 03:29 | 2,492 | +3 |
| 29 Oct 2026, 02:49 | 2,489 | -2 |
| 23 Oct 2026, 03:28 | 2,491 | +5 |
| 20 Oct 2026, 07:46 | 2,486 | +4 |
| 17 Oct 2026, 10:01 | 2,482 | +4 |
| 14 Oct 2026, 18:08 | 2,478 | +4 |
| 5 Oct 2026, 14:40 | 2,474 | +2 |
| 27 Sept 2026, 15:19 | 2,472 | +11 |
| 18 Sept 2026, 06:59 | 2,461 | +4 |
| 16 Sept 2026, 00:53 | 2,457 | no change |
| 14 Sept 2026, 05:16 | 2,457 | -3 |
| 10 Sept 2026, 21:17 | 2,460 | -2 |
| 8 Sept 2026, 06:47 | 2,462 | 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.
@surgerywithzaid · 19,848
Telegram ranks this channel #32 of 77 here — alongside 76 others — read 4 October 2026
@Amedicalnotes · 20,404
Telegram ranks this channel #34 of 87 here — alongside 86 others — read 28 September 2026
@ECG2023 · 28,588
Telegram ranks this channel #37 of 85 here — alongside 84 others — read 11 September 2026
@MED_ACE · 26,402
Telegram ranks this channel #44 of 79 here — alongside 78 others — read 14 September 2026
@Drhaidermedicalcourses · 30,387
Telegram ranks this channel #56 of 88 here — alongside 87 others — read 8 September 2026
@seminars4student · 21,140
Telegram ranks this channel #61 of 89 here — alongside 88 others — read 23 September 2026
This channel appears in 6 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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“Clinical with mohassed” (@mohassedza), 2,495 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/mohassedza.
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.