Channel
Internal Medicine MCQ
@imedmcq
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,401subscribers
+32 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001402682177 |
|---|---|
| Type | Channel |
| Username | @imedmcq |
| Created | Between 1 January 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 2 times, most recently 30 October 2026 |
| On Telegram | t.me/imedmcq |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 27 Oct 2026, 19:17 | 4,401 | +1 |
| 24 Oct 2026, 14:46 | 4,400 | +5 |
| 21 Oct 2026, 19:58 | 4,395 | +5 |
| 18 Oct 2026, 21:28 | 4,390 | +1 |
| 15 Oct 2026, 13:19 | 4,389 | +4 |
| 12 Oct 2026, 22:46 | 4,385 | -2 |
| 6 Oct 2026, 07:01 | 4,387 | -3 |
| 29 Sept 2026, 01:58 | 4,390 | +9 |
| 19 Sept 2026, 11:22 | 4,381 | +5 |
| 11 Sept 2026, 21:15 | 4,376 | +3 |
| 7 Sept 2026, 10:38 | 4,373 | +4 |
| 3 Sept 2026, 22:57 | 4,369 | no change |
| 2 Sept 2026, 14:27 | 4,369 | -2 |
| 30 Aug 2026, 16:43 | 4,371 | +3 |
| 27 Aug 2026, 15:56 | 4,368 | -1 |
| 26 Aug 2026, 18:30 | 4,369 | 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.
@usmle_in_arabic · 75,990
Telegram ranks this channel #52 of 76 here — alongside 75 others — read 26 August 2026
@AlAzharAssiutMedicalSchool · 26,690
Telegram ranks this channel #64 of 73 here — alongside 72 others — read 13 September 2026
@Boards_Beyond_videos · 42,841
Telegram ranks this channel #64 of 76 here — alongside 75 others — read 30 August 2026
@Updates_in_Medicine · 49,330
Telegram ranks this channel #71 of 74 here — alongside 73 others — read 26 August 2026
@Medical_Patna · 47,287
Telegram ranks this channel #83 of 91 here — alongside 90 others — read 28 August 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 27 October 2026 — this entry's latest reading, not the date you are reading this.
“Internal Medicine MCQ” (@imedmcq), 4,401 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/imedmcq.
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.