Channel
TunesWay
@tunes_way
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,821subscribers
-28 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001008420569 |
|---|---|
| Type | Channel |
| Username | @tunes_way |
| Created | Between 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/tunes_way |
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 89% 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 |
|---|---|---|
| 5 Nov 2026, 00:59 | 3,821 | -1 |
| 1 Nov 2026, 17:55 | 3,822 | -1 |
| 29 Oct 2026, 18:39 | 3,823 | +1 |
| 26 Oct 2026, 16:37 | 3,822 | -1 |
| 23 Oct 2026, 23:19 | 3,823 | -3 |
| 20 Oct 2026, 20:01 | 3,826 | -4 |
| 18 Oct 2026, 02:09 | 3,830 | -3 |
| 15 Oct 2026, 09:21 | 3,833 | -1 |
| 12 Oct 2026, 11:10 | 3,834 | -3 |
| 5 Oct 2026, 22:19 | 3,837 | +6 |
| 28 Sept 2026, 12:37 | 3,831 | -10 |
| 15 Sept 2026, 13:58 | 3,841 | +1 |
| 11 Sept 2026, 22:16 | 3,840 | -3 |
| 7 Sept 2026, 12:57 | 3,843 | -2 |
| 6 Sept 2026, 13:07 | 3,845 | no change |
| 2 Sept 2026, 19:26 | 3,845 | -1 |
| 31 Aug 2026, 02:23 | 3,846 | -4 |
| 28 Aug 2026, 12:04 | 3,850 | +1 |
| 25 Aug 2026, 02:09 | 3,849 | +2 |
| 22 Aug 2026, 00:27 | 3,847 | 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.
@payamabasii · 24,577
Telegram ranks this channel #52 of 54 here — alongside 53 others — read 26 September 2026
@Listenwitharad · 34,210
Telegram ranks this channel #67 of 72 here — alongside 71 others — read 2 September 2026
@Armangarshasbiofficial · 49,635
Telegram ranks this channel #73 of 90 here — alongside 89 others — read 27 August 2026
@mohsenchavoshi · 235,334
Telegram ranks this channel #82 of 91 here — alongside 90 others — read 14 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“TunesWay” (@tunes_way), 3,821 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/tunes_way.
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.