Channel
MediDent
@MediDent_group
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,298subscribers
+12 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001850398955 |
|---|---|
| Type | Channel |
| Username | @MediDent_group |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 October 2026 |
| Last confirmed live | 24 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 3 times, most recently 24 October 2026 |
| On Telegram | t.me/MediDent_group |
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 2 October 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 18 Oct 2026, 04:07 | 1,298 | -1 |
| 15 Oct 2026, 09:39 | 1,299 | -6 |
| 12 Oct 2026, 15:10 | 1,305 | +1 |
| 5 Oct 2026, 22:21 | 1,304 | +5 |
| 2 Oct 2026, 03:17 | 1,299 | no change |
| 28 Sept 2026, 23:37 | 1,299 | +2 |
| 19 Sept 2026, 00:56 | 1,297 | +5 |
| 14 Sept 2026, 20:22 | 1,292 | +4 |
| 10 Sept 2026, 23:41 | 1,288 | -1 |
| 5 Sept 2026, 14:58 | 1,289 | +1 |
| 1 Sept 2026, 23:45 | 1,288 | +1 |
| 29 Aug 2026, 14:33 | 1,287 | +1 |
| 26 Aug 2026, 11:08 | 1,286 | +1 |
| 20 Aug 2026, 03:25 | 1,285 | -1 |
| 19 Aug 2026, 15:45 | 1,286 | 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.
@medicall_students · 79,878
Telegram ranks this channel #24 of 79 here — alongside 78 others — read 19 August 2026
@itstinass · 26,068
Telegram ranks this channel #34 of 57 here — alongside 56 others — read 12 September 2026
@russtudents · 24,995
Telegram ranks this channel #36 of 74 here — alongside 73 others — read 24 September 2026
@fit_sh_o · 19,969
Telegram ranks this channel #38 of 75 here — alongside 74 others — read 23 September 2026
@Radio_Amboy · 39,475
Telegram ranks this channel #47 of 59 here — alongside 58 others — read 5 September 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 18 October 2026 — this entry's latest reading, not the date you are reading this.
“MediDent” (@MediDent_group), 1,298 subscribers as measured 18 October 2026. Telegram Register, tgregister.com/channel/MediDent_group.
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.