Channel
مخمور¹¹⁰
@Makhmoor_110
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,305subscribers
+92 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001141112705 |
|---|---|
| Type | Channel |
| Username | @Makhmoor_110 |
| Created | Between 1 May 2016 and 31 December 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/Makhmoor_110 |
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 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 21:21 | 3,305 | +17 |
| 15 Sept 2026, 18:56 | 3,288 | +2 |
| 12 Sept 2026, 05:19 | 3,286 | +4 |
| 9 Sept 2026, 20:22 | 3,282 | no change |
| 7 Sept 2026, 22:22 | 3,282 | +3 |
| 2 Sept 2026, 17:07 | 3,279 | +2 |
| 30 Aug 2026, 23:28 | 3,277 | -1 |
| 28 Aug 2026, 04:25 | 3,278 | +5 |
| 25 Aug 2026, 11:33 | 3,273 | +2 |
| 22 Aug 2026, 16:17 | 3,271 | +18 |
| 19 Aug 2026, 13:28 | 3,253 | +14 |
| 16 Aug 2026, 03:54 | 3,239 | +9 |
| 12 Aug 2026, 10:58 | 3,230 | +14 |
| 9 Aug 2026, 19:22 | 3,216 | +2 |
| 6 Aug 2026, 18:10 | 3,214 | +1 |
| 6 Aug 2026, 03:32 | 3,213 | 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.
@Mahdii_ranaee · 20,639
Telegram ranks this channel #49 of 90 here — alongside 89 others — read 26 September 2026
@pelan_3 · 37,626
Telegram ranks this channel #76 of 95 here — alongside 94 others — read 1 September 2026
@amirhoseinhazrati128 · 38,669
Telegram ranks this channel #79 of 94 here — alongside 93 others — read 31 August 2026
This channel appears in 3 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“مخمور¹¹⁰” (@Makhmoor_110), 3,305 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/Makhmoor_110.
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.