Channel
DailyTunes
@DailyTunes
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,159subscribers
-1 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 | -1001088379976 |
|---|---|
| Type | Channel |
| Username | @DailyTunes |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 October 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/DailyTunes |
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 5 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 04:00 | 1,159 | -4 |
| 5 Oct 2026, 15:57 | 1,163 | -1 |
| 5 Oct 2026, 04:12 | 1,164 | no change |
| 27 Sept 2026, 17:20 | 1,164 | +1 |
| 16 Sept 2026, 00:00 | 1,163 | -3 |
| 12 Sept 2026, 09:00 | 1,166 | +1 |
| 8 Sept 2026, 11:36 | 1,165 | +4 |
| 22 Aug 2026, 14:44 | 1,161 | +4 |
| 18 Aug 2026, 20:34 | 1,157 | -2 |
| 16 Aug 2026, 03:47 | 1,159 | -1 |
| 12 Aug 2026, 16:04 | 1,160 | -1 |
| 9 Aug 2026, 16:04 | 1,161 | +2 |
| 6 Aug 2026, 09:00 | 1,159 | -1 |
| 6 Aug 2026, 00:32 | 1,160 | 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.
@DownloadKoinoniaSermons · 21,532
Telegram ranks this channel #45 of 71 here — alongside 70 others — read 23 September 2026
@shinYoga · 42,710
Telegram ranks this channel #68 of 71 here — alongside 70 others — read 29 August 2026
@irfalodeh · 98,331
Telegram ranks this channel #68 of 72 here — alongside 71 others — read 18 August 2026
@mosighiasilvaclasiic · 49,686
Telegram ranks this channel #71 of 79 here — alongside 78 others — read 25 August 2026
@flowwithmusic · 21,598
Telegram ranks this channel #89 of 93 here — alongside 92 others — read 23 September 2026
@SoundSilence · 115,333
Telegram ranks this channel #90 of 95 here — alongside 94 others — read 14 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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“DailyTunes” (@DailyTunes), 1,159 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/DailyTunes.
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.