Channel
MedWI
@MeddWI
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,896subscribers
+99 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001671823554 |
|---|---|
| Type | Channel |
| Username | @MeddWI |
| 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 | 18 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/MeddWI |
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 100% 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, 00:46 | 3,896 | -1 |
| 1 Nov 2026, 14:06 | 3,897 | +3 |
| 29 Oct 2026, 19:50 | 3,894 | -5 |
| 26 Oct 2026, 22:45 | 3,899 | +3 |
| 24 Oct 2026, 04:18 | 3,896 | +1 |
| 21 Oct 2026, 08:29 | 3,895 | +8 |
| 18 Oct 2026, 10:20 | 3,887 | -1 |
| 15 Oct 2026, 03:39 | 3,888 | -6 |
| 12 Oct 2026, 09:40 | 3,894 | -9 |
| 5 Oct 2026, 16:41 | 3,903 | +9 |
| 27 Sept 2026, 21:35 | 3,894 | +24 |
| 18 Sept 2026, 03:19 | 3,870 | +6 |
| 14 Sept 2026, 06:57 | 3,864 | +9 |
| 10 Sept 2026, 09:59 | 3,855 | +34 |
| 6 Sept 2026, 13:40 | 3,821 | no change |
| 5 Sept 2026, 11:57 | 3,821 | +7 |
| 1 Sept 2026, 16:49 | 3,814 | +17 |
| 28 Aug 2026, 20:45 | 3,797 | 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.
@ifnmu_book · 34,917
Telegram ranks this channel #7 of 72 here — alongside 71 others — read 27 September 2026
@nmulib · 35,882
Telegram ranks this channel #9 of 74 here — alongside 73 others — read 27 September 2026
@znohub_bio · 19,896
Telegram ranks this channel #32 of 80 here — alongside 79 others — read 4 October 2026
@vstup · 38,639
Telegram ranks this channel #61 of 84 here — alongside 83 others — read 28 August 2026
@vstupinfoUA · 29,496
Telegram ranks this channel #68 of 83 here — alongside 82 others — read 5 September 2026
@vstup_education_ua · 23,962
Telegram ranks this channel #71 of 77 here — alongside 76 others — read 12 September 2026
This channel appears in 6 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.
“MedWI” (@MeddWI), 3,896 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/MeddWI.
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.