Channel
MedStudy Internal Medicine
@MedStudy_Internal_Medicine
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,430subscribers
+64 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 | -1001605507743 |
|---|---|
| Type | Channel |
| Username | @MedStudy_Internal_Medicine |
| Created | Between 1 November 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/MedStudy_Internal_Medicine |
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 14 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 11:10 | 3,430 | +3 |
| 2 Nov 2026, 15:45 | 3,427 | +4 |
| 30 Oct 2026, 19:37 | 3,423 | +2 |
| 28 Oct 2026, 02:21 | 3,421 | +1 |
| 25 Oct 2026, 04:57 | 3,420 | +1 |
| 21 Oct 2026, 20:54 | 3,419 | +2 |
| 18 Oct 2026, 12:44 | 3,417 | -2 |
| 12 Oct 2026, 13:05 | 3,419 | -4 |
| 6 Oct 2026, 00:59 | 3,423 | +9 |
| 28 Sept 2026, 13:55 | 3,414 | +32 |
| 14 Sept 2026, 11:56 | 3,382 | +5 |
| 10 Sept 2026, 20:42 | 3,377 | +5 |
| 8 Sept 2026, 23:43 | 3,372 | no change |
| 5 Sept 2026, 19:18 | 3,372 | -2 |
| 1 Sept 2026, 18:36 | 3,374 | +5 |
| 29 Aug 2026, 23:17 | 3,369 | +3 |
| 26 Aug 2026, 17:30 | 3,366 | 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.
@U_SMLE · 69,054
Telegram ranks this channel #16 of 72 here — alongside 71 others — read 26 August 2026
@Notes_772 · 82,539
Telegram ranks this channel #20 of 76 here — alongside 75 others — read 26 August 2026
@FamilyPhysician_1 · 28,425
Telegram ranks this channel #34 of 75 here — alongside 74 others — read 10 September 2026
@neetpg_fmge_mcq · 28,787
Telegram ranks this channel #45 of 68 here — alongside 67 others — read 11 September 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“MedStudy Internal Medicine” (@MedStudy_Internal_Medicine), 3,430 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/MedStudy_Internal_Medicine.
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.