Channel
Miralisher Khanjarov
@miralisherkhan
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,023subscribers
-75 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001952361576 |
|---|---|
| Type | Channel |
| Username | @miralisherkhan |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 October 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/miralisherkhan |
Topic
Personal blog — 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 8 October 2026 and assigned it the closest of 31 fixed categories, at 97% 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:16 | 1,023 | -1 |
| 2 Nov 2026, 12:56 | 1,024 | -3 |
| 30 Oct 2026, 14:36 | 1,027 | -3 |
| 24 Oct 2026, 20:41 | 1,030 | -4 |
| 22 Oct 2026, 05:47 | 1,034 | -2 |
| 19 Oct 2026, 03:17 | 1,036 | -7 |
| 16 Oct 2026, 02:06 | 1,043 | -4 |
| 12 Oct 2026, 15:46 | 1,047 | -8 |
| 8 Oct 2026, 03:43 | 1,055 | no change |
| 6 Oct 2026, 02:54 | 1,055 | -4 |
| 28 Sept 2026, 15:56 | 1,059 | -6 |
| 18 Sept 2026, 22:17 | 1,065 | -9 |
| 14 Sept 2026, 11:57 | 1,074 | -7 |
| 10 Sept 2026, 15:56 | 1,081 | -3 |
| 5 Sept 2026, 19:16 | 1,084 | -3 |
| 1 Sept 2026, 14:58 | 1,087 | -2 |
| 29 Aug 2026, 09:15 | 1,089 | -4 |
| 26 Aug 2026, 17:28 | 1,093 | -3 |
| 23 Aug 2026, 10:16 | 1,096 | -1 |
| 19 Aug 2026, 21:22 | 1,097 | 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.
@bola_tarbiyasi · 45,349
Telegram ranks this channel #12 of 54 here — alongside 53 others — read 26 August 2026
@kunlik_retseptlar · 82,566
Telegram ranks this channel #19 of 24 here — alongside 23 others — read 18 August 2026
@ozish_uchun_mashq_raqs · 54,169
Telegram ranks this channel #21 of 40 here — alongside 39 others — read 23 August 2026
@DORIXONA_APTEKA_KASALIKLAR · 19,479
Telegram ranks this channel #22 of 47 here — alongside 46 others — read 26 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.
“Miralisher Khanjarov” (@miralisherkhan), 1,023 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/miralisherkhan.
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.