Channel
ππππ πππππ πππ
@tala_music68
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
3,125subscribers
+13 since we began measuring on 12 August 2026
Risers and fallers across the register Β· movement among entries of 1,000β3,162.
Register entry
| Telegram ID | -1001926530980 |
|---|---|
| Type | Channel |
| Username | @tala_music68 |
| Created | Between 1 April 2023 and 31 October 2023 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/tala_music68 |
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 99% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 04:41 | 3,125 | +7 |
| 13 Sept 2026, 12:58 | 3,118 | +4 |
| 10 Sept 2026, 21:33 | 3,114 | no change |
| 10 Sept 2026, 03:59 | 3,114 | +17 |
| 4 Sept 2026, 22:19 | 3,097 | +2 |
| 1 Sept 2026, 06:46 | 3,095 | -4 |
| 29 Aug 2026, 13:35 | 3,099 | +2 |
| 26 Aug 2026, 22:07 | 3,097 | -2 |
| 23 Aug 2026, 13:14 | 3,099 | -1 |
| 19 Aug 2026, 14:36 | 3,100 | -6 |
| 16 Aug 2026, 20:54 | 3,106 | -6 |
| 12 Aug 2026, 22:30 | 3,112 | 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.
@alihashemifx Β· 32,381
Telegram ranks this channel #6 of 50 here β alongside 49 others β read 4 September 2026
@Remix_loving Β· 25,503
Telegram ranks this channel #10 of 72 here β alongside 71 others β read 14 September 2026
@RemixK1 Β· 211,647
Telegram ranks this channel #11 of 76 here β alongside 75 others β read 12 August 2026
@shomall_music_orginal Β· 56,746
Telegram ranks this channel #20 of 78 here β alongside 77 others β read 24 August 2026
@deejemix Β· 28,198
Telegram ranks this channel #29 of 58 here β alongside 57 others β read 9 September 2026
@mix_clip_nabi Β· 78,185
Telegram ranks this channel #44 of 85 here β alongside 84 others β read 19 August 2026
This channel appears in 6 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 17 September 2026 β this entry's latest reading, not the date you are reading this.
βππππ πππππ πππβ (@tala_music68), 3,125 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/tala_music68.
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.