Channel
Channel.mohaamd.elx
@mohaamad_elx
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,520subscribers
-39 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002210254274 |
|---|---|
| Type | Channel |
| Username | @mohaamad_elx |
| Description | اهنگ ها رو اینجا میزاریم 😍❤️✈️ پیـج اینستـاگـــــرام🆔 https://www.instagram.com/mohaamd.elx?igsh=OTljbmFobGtzMnF3 . . |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 September 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 11 |
| On Telegram | t.me/mohaamad_elx |
Topic
Music — 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 15 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 14:36 | 2,520 | no change |
| 15 Sept 2026, 14:01 | 2,520 | -2 |
| 12 Sept 2026, 00:20 | 2,522 | -7 |
| 7 Sept 2026, 05:59 | 2,529 | -12 |
| 2 Sept 2026, 06:11 | 2,541 | -5 |
| 30 Aug 2026, 00:24 | 2,546 | -4 |
| 24 Aug 2026, 12:18 | 2,550 | -13 |
| 20 Aug 2026, 11:38 | 2,563 | -2 |
| 17 Aug 2026, 15:06 | 2,565 | +12 |
| 14 Aug 2026, 15:05 | 2,553 | -6 |
| 11 Aug 2026, 01:30 | 2,559 | 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.
@shotitube · 252,188
Telegram ranks this channel #9 of 62 here — alongside 61 others — read 11 August 2026
@ir31_405_mix · 41,904
Telegram ranks this channel #11 of 63 here — alongside 62 others — read 29 August 2026
@DJKINGABAS · 194,140
Telegram ranks this channel #21 of 82 here — alongside 81 others — read 11 August 2026
@RemixK1 · 211,647
Telegram ranks this channel #24 of 76 here — alongside 75 others — read 12 August 2026
@mrhoseiin · 30,389
Telegram ranks this channel #34 of 43 here — alongside 42 others — read 7 September 2026
@dancebet_sait · 46,058
Telegram ranks this channel #59 of 77 here — alongside 76 others — read 26 August 2026
@chaluscity1 · 30,775
Telegram ranks this channel #63 of 74 here — alongside 73 others — read 6 September 2026
This channel appears in 7 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Channel.mohaamd.elx” (@mohaamad_elx), 2,520 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/mohaamad_elx.
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.