Channel
Mohammadbahrami_music
@mohammadbahrami_music
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,497subscribers
+1,680 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 | -1001245794393 |
|---|---|
| Type | Channel |
| Username | @mohammadbahrami_music |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/mohammadbahrami_music |
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 85% 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, 19:17 | 3,497 | +288 |
| 2 Nov 2026, 14:37 | 3,209 | +45 |
| 30 Oct 2026, 17:04 | 3,164 | +6 |
| 28 Oct 2026, 01:57 | 3,158 | +17 |
| 25 Oct 2026, 01:37 | 3,141 | -1 |
| 22 Oct 2026, 09:49 | 3,142 | +8 |
| 18 Oct 2026, 18:07 | 3,134 | +3 |
| 15 Oct 2026, 17:20 | 3,131 | +4 |
| 12 Oct 2026, 17:14 | 3,127 | +17 |
| 5 Oct 2026, 23:57 | 3,110 | +128 |
| 28 Sept 2026, 10:55 | 2,982 | +36 |
| 18 Sept 2026, 21:20 | 2,946 | +35 |
| 14 Sept 2026, 21:00 | 2,911 | +122 |
| 13 Sept 2026, 00:46 | 2,789 | no change |
| 11 Sept 2026, 09:37 | 2,789 | +340 |
| 6 Sept 2026, 23:16 | 2,449 | +30 |
| 2 Sept 2026, 10:42 | 2,419 | +58 |
| 30 Aug 2026, 11:13 | 2,361 | +308 |
| 27 Aug 2026, 00:58 | 2,053 | +148 |
| 24 Aug 2026, 01:36 | 1,905 | 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.
@academysafari · 28,135
Telegram ranks this channel #43 of 50 here — alongside 49 others — read 8 September 2026
@farshidpakzat_nlp · 21,649
Telegram ranks this channel #62 of 64 here — alongside 63 others — read 21 September 2026
@moazamica · 20,827
Telegram ranks this channel #79 of 83 here — alongside 82 others — read 25 September 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“Mohammadbahrami_music” (@mohammadbahrami_music), 3,497 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/mohammadbahrami_music.
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.