Channel
πππ_ππππ
@muz_time13
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
3,065subscribers
-136 since we began measuring on 7 August 2026
Risers and fallers across the register Β· movement among entries of 1,000β3,162.
Register entry
| Telegram ID | -1001437345788 |
|---|---|
| Type | Channel |
| Username | @muz_time13 |
| Created | Between 1 April 2019 and 31 October 2021 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/muz_time13 |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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 |
|---|---|---|
| 7 Nov 2026, 23:56 | 3,065 | -7 |
| 5 Nov 2026, 02:39 | 3,072 | -2 |
| 2 Nov 2026, 06:59 | 3,074 | -1 |
| 30 Oct 2026, 09:16 | 3,075 | -6 |
| 27 Oct 2026, 09:31 | 3,081 | -8 |
| 24 Oct 2026, 03:14 | 3,089 | -5 |
| 21 Oct 2026, 09:45 | 3,094 | -4 |
| 18 Oct 2026, 09:20 | 3,098 | -4 |
| 15 Oct 2026, 02:31 | 3,102 | -2 |
| 12 Oct 2026, 07:17 | 3,104 | -4 |
| 5 Oct 2026, 13:18 | 3,108 | -16 |
| 27 Sept 2026, 08:35 | 3,124 | -14 |
| 15 Sept 2026, 09:20 | 3,138 | -6 |
| 11 Sept 2026, 13:21 | 3,144 | -13 |
| 10 Sept 2026, 13:48 | 3,157 | no change |
| 7 Sept 2026, 01:22 | 3,157 | -3 |
| 2 Sept 2026, 18:58 | 3,160 | -6 |
| 30 Aug 2026, 19:46 | 3,166 | -5 |
| 27 Aug 2026, 23:15 | 3,171 | -2 |
| 24 Aug 2026, 12:55 | 3,173 | 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.
@EA7MUSICORIGINAL Β· 19,335
Telegram ranks this channel #7 of 47 here β alongside 46 others β read 1 October 2026
@muzyka_new Β· 86,595
Telegram ranks this channel #31 of 52 here β alongside 51 others β read 16 August 2026
@soulblackx1 Β· 28,608
Telegram ranks this channel #32 of 46 here β alongside 45 others β read 8 September 2026
@manilamusics Β· 88,521
Telegram ranks this channel #42 of 52 here β alongside 51 others β read 16 August 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 7 November 2026 β this entry's latest reading, not the date you are reading this.
βπππ_ππππβ (@muz_time13), 3,065 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/muz_time13.
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.