Channel
Medical_database
@Medical_Database
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,213subscribers
-13 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001058030499 |
|---|---|
| Type | Channel |
| Username | @Medical_Database |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 2 times, most recently 14 September 2026 |
| On Telegram | t.me/Medical_Database |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 22:19 | 3,213 | -4 |
| 9 Sept 2026, 23:57 | 3,217 | no change |
| 5 Sept 2026, 13:36 | 3,217 | +1 |
| 2 Sept 2026, 00:58 | 3,216 | -1 |
| 30 Aug 2026, 02:18 | 3,217 | -2 |
| 27 Aug 2026, 06:49 | 3,219 | -7 |
| 24 Aug 2026, 17:07 | 3,226 | -5 |
| 20 Aug 2026, 21:15 | 3,231 | +1 |
| 18 Aug 2026, 05:52 | 3,230 | -1 |
| 14 Aug 2026, 23:05 | 3,231 | +7 |
| 11 Aug 2026, 22:45 | 3,224 | +1 |
| 9 Aug 2026, 02:51 | 3,223 | -3 |
| 5 Aug 2026, 23:07 | 3,226 | 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.
@Physiology_videos · 71,283
Telegram ranks this channel #14 of 74 here — alongside 73 others — read 26 August 2026
@yassericu · 38,035
Telegram ranks this channel #22 of 78 here — alongside 77 others — read 15 September 2026
This channel appears in 2 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“Medical_database” (@Medical_Database), 3,213 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/Medical_Database.
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.