Channel
ODIN Music
@odin_muzic
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,378subscribers
-281 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001075176344 |
|---|---|
| Type | Channel |
| Username | @odin_muzic |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/odin_muzic |
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 87% 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, 11:19 | 3,378 | -9 |
| 4 Nov 2026, 09:08 | 3,387 | -14 |
| 1 Nov 2026, 04:27 | 3,401 | -12 |
| 29 Oct 2026, 02:10 | 3,413 | -13 |
| 25 Oct 2026, 14:27 | 3,426 | -15 |
| 22 Oct 2026, 23:26 | 3,441 | -8 |
| 20 Oct 2026, 00:41 | 3,449 | -14 |
| 16 Oct 2026, 16:06 | 3,463 | -3 |
| 13 Oct 2026, 19:28 | 3,466 | -32 |
| 7 Oct 2026, 20:56 | 3,498 | -15 |
| 1 Oct 2026, 10:37 | 3,513 | -50 |
| 15 Sept 2026, 23:00 | 3,563 | -4 |
| 12 Sept 2026, 02:38 | 3,567 | +1 |
| 7 Sept 2026, 23:10 | 3,566 | no change |
| 7 Sept 2026, 10:41 | 3,566 | -19 |
| 2 Sept 2026, 19:29 | 3,585 | -17 |
| 30 Aug 2026, 07:28 | 3,602 | -2 |
| 27 Aug 2026, 07:03 | 3,604 | -14 |
| 24 Aug 2026, 03:16 | 3,618 | -13 |
| 20 Aug 2026, 11:04 | 3,631 | 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.
@NABiXxX · 122,407
Telegram ranks this channel #2 of 67 here — alongside 66 others — read 13 August 2026
@shivana_music · 20,397
Telegram ranks this channel #12 of 75 here — alongside 74 others — read 26 September 2026
@westbet2025 · 36,075
Telegram ranks this channel #13 of 25 here — alongside 24 others — read 13 September 2026
@VipPodcastMusic · 21,968
Telegram ranks this channel #64 of 72 here — alongside 71 others — read 23 September 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.
“ODIN Music” (@odin_muzic), 3,378 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/odin_muzic.
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.