Telegram RegisterThe public register of Telegram
Telegram profile photo for Music bandari

Channel

Music bandari

@muzicbhnd

On this record: Topic · Growth · Engagement · Citations · Telegram's recommendations · Cite this entry

1,231subscribers

+26 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001053857664
TypeChannel
Username@muzicbhnd
DescriptionMusic bandari اهنگ های استان بوشهر {محلی}،اهنگهای لری،بستکی،و شیرازی و آمبولانسی و چپونی و...... . . https://t.me/boost/muzicbhnd
CreatedBetween 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 October 2026
Last confirmed live4 October 2026
Measurements held15
On Telegramt.me/muzicbhnd

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 3 October 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

1,2051,2311,2186 August 2026 — 1,205 subscribers9 August 2026 — 1,206 subscribers12 August 2026 — 1,207 subscribers15 August 2026 — 1,209 subscribers18 August 2026 — 1,211 subscribers21 August 2026 — 1,213 subscribers24 August 2026 — 1,216 subscribers27 August 2026 — 1,213 subscribers31 August 2026 — 1,216 subscribers3 September 2026 — 1,213 subscribers8 September 2026 — 1,214 subscribers12 September 2026 — 1,219 subscribers17 September 2026 — 1,226 subscribers25 September 2026 — 1,231 subscribers3 October 2026 — 1,231 subscribers6 August 20263 October 2026
15 measurements spanning 58 days, net +26. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,201–1,235 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 17:351,231no change
25 Sept 2026, 05:371,231+5
17 Sept 2026, 01:381,226+7
12 Sept 2026, 18:171,219+5
8 Sept 2026, 17:561,214+1
3 Sept 2026, 20:561,213-3
31 Aug 2026, 04:571,216+3
27 Aug 2026, 22:271,213-3
24 Aug 2026, 23:451,216+3
21 Aug 2026, 06:521,213+2
18 Aug 2026, 14:051,211+2
15 Aug 2026, 20:061,209+2
12 Aug 2026, 17:571,207+1
9 Aug 2026, 08:511,206+1
6 Aug 2026, 12:491,205first 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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.

Malorani Studio
@malorani · 29,246
Telegram ranks this channel #14 of 64 here — alongside 63 others — read 18 September 2026
کانال رسمی هومن پناهی
@homan_muaic · 36,430
Telegram ranks this channel #18 of 69 here — alongside 68 others — read 2 September 2026
سایت بزرگ خلیج موزیک 🌴🎧
@khalijmusic_info · 30,874
Telegram ranks this channel #35 of 81 here — alongside 80 others — read 7 September 2026
📗آرشیو ریاضی کلاس سومی ها
@arshivriazi3 · 18,893
Telegram ranks this channel #65 of 79 here — alongside 78 others — read 5 October 2026
کلاس اولی ها(جهان تیغ)
@classavaleha · 20,358
Telegram ranks this channel #69 of 72 here — alongside 71 others — read 27 September 2026

This channel appears in 5 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 3 October 2026 — this entry's latest reading, not the date you are reading this.

“Music bandari” (@muzicbhnd), 1,231 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/muzicbhnd.

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.