Channel
ماە زیور✨🌙
@bashgahi_mos
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,678subscribers
-346 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001318120461 |
|---|---|
| Type | Channel |
| Username | @bashgahi_mos |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/bashgahi_mos |
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 19 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, 21:30 | 1,678 | -19 |
| 2 Nov 2026, 14:09 | 1,697 | -22 |
| 30 Oct 2026, 15:36 | 1,719 | -40 |
| 27 Oct 2026, 09:06 | 1,759 | -33 |
| 24 Oct 2026, 11:35 | 1,792 | -14 |
| 21 Oct 2026, 17:29 | 1,806 | -18 |
| 18 Oct 2026, 08:18 | 1,824 | -16 |
| 15 Oct 2026, 18:19 | 1,840 | -15 |
| 12 Oct 2026, 11:37 | 1,855 | -82 |
| 5 Oct 2026, 09:40 | 1,937 | -195 |
| 26 Sept 2026, 21:01 | 2,132 | +25 |
| 19 Sept 2026, 22:52 | 2,107 | no change |
| 17 Sept 2026, 08:18 | 2,107 | +26 |
| 13 Sept 2026, 07:40 | 2,081 | +10 |
| 9 Sept 2026, 09:58 | 2,071 | +3 |
| 3 Sept 2026, 16:37 | 2,068 | +13 |
| 31 Aug 2026, 10:44 | 2,055 | +8 |
| 28 Aug 2026, 18:54 | 2,047 | +5 |
| 26 Aug 2026, 03:53 | 2,042 | +14 |
| 23 Aug 2026, 08:18 | 2,028 | 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.
@rjmiix · 38,062
Telegram ranks this channel #4 of 56 here — alongside 55 others — read 31 August 2026
@remixdx · 56,879
Telegram ranks this channel #14 of 60 here — alongside 59 others — read 22 August 2026
@nikvestx · 29,429
Telegram ranks this channel #20 of 71 here — alongside 70 others — read 5 September 2026
@bikalam_moozik · 23,523
Telegram ranks this channel #29 of 64 here — alongside 63 others — read 17 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.
“ماە زیور✨🌙” (@bashgahi_mos), 1,678 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/bashgahi_mos.
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.