Telegram RegisterThe public register of Telegram
Telegram profile photo for πŸŽ§π™˜π™€π™˜π™’π™€π™¨_π™ͺπ™¨π™–πŸ·πŸŽ§

Channel

πŸŽ§π™˜π™€π™˜π™’π™€π™¨_π™ͺπ™¨π™–πŸ·πŸŽ§

@bass_mucik001001

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

84subscribers

-14 since we began measuring on 25 August 2026

Risers and fallers across the register Β· movement among entries of Under 1,000.

Register entry

Telegram ID-1002037366215
TypeChannel
Username@bass_mucik001001
CreatedBetween 1 November 2023 and 31 May 2024 β€” estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 October 2026
Last confirmed live8 November 2026
Measurements held9
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/bass_mucik001001

Topic

Music β€” a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 19 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 the other topics.

Growth

84989125 August 2026 β€” 98 subscribers1 September 2026 β€” 97 subscribers10 September 2026 β€” 95 subscribers3 October 2026 β€” 90 subscribers13 October 2026 β€” 89 subscribers19 October 2026 β€” 89 subscribers20 October 2026 β€” 87 subscribers26 October 2026 β€” 86 subscribers8 November 2026 β€” 84 subscribers25 August 20268 November 2026
9 measurements spanning 76 days, net -14. 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 82–100 and does not start at zero.
Measurement log β€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Nov 2026, 23:4084-2
26 Oct 2026, 22:5686-1
20 Oct 2026, 22:5687-2
19 Oct 2026, 18:1289no change
13 Oct 2026, 07:0489-1
3 Oct 2026, 00:1990-5
10 Sept 2026, 15:3995-2
1 Sept 2026, 12:2597-1
25 Aug 2026, 04:1598first 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.

MULTILEVEL ZONE
@Multilevel_zone Β· 215,660
Telegram ranks this channel #56 of 62 here β€” alongside 61 others β€” read 25 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 8 November 2026 β€” this entry's latest reading, not the date you are reading this.

β€œπŸŽ§π™˜π™€π™˜π™’π™€π™¨_π™ͺπ™¨π™–πŸ·πŸŽ§β€ (@bass_mucik001001), 84 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/bass_mucik001001.

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.