Channel
MedBax
@Medbax
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,664subscribers
-86 since we began measuring on 5 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001638494829 |
|---|---|
| Type | Channel |
| Username | @Medbax |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/Medbax |
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 93% 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, 20:50 | 3,664 | -8 |
| 2 Nov 2026, 14:06 | 3,672 | -7 |
| 30 Oct 2026, 17:00 | 3,679 | -1 |
| 27 Oct 2026, 15:48 | 3,680 | -4 |
| 24 Oct 2026, 18:40 | 3,684 | +1 |
| 21 Oct 2026, 13:27 | 3,683 | +2 |
| 18 Oct 2026, 16:20 | 3,681 | -2 |
| 15 Oct 2026, 07:05 | 3,683 | -8 |
| 12 Oct 2026, 02:56 | 3,691 | -12 |
| 5 Oct 2026, 11:17 | 3,703 | -21 |
| 27 Sept 2026, 01:57 | 3,724 | -9 |
| 17 Sept 2026, 12:58 | 3,733 | -8 |
| 13 Sept 2026, 06:20 | 3,741 | -7 |
| 9 Sept 2026, 04:21 | 3,748 | -2 |
| 6 Sept 2026, 22:54 | 3,750 | no change |
| 5 Sept 2026, 20:47 | 3,750 | 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.
@Team_MedicalSciences · 26,246
Telegram ranks this channel #32 of 87 here — alongside 86 others — read 13 September 2026
@nbookcity · 32,007
Telegram ranks this channel #46 of 68 here — alongside 67 others — read 5 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“MedBax” (@Medbax), 3,664 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/Medbax.
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.