Channel
NamitoMusic
@namitomusic
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,136subscribers
+149 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001285298651 |
|---|---|
| Type | Channel |
| Username | @namitomusic |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/namitomusic |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 |
|---|---|---|
| 3 Nov 2026, 08:50 | 5,136 | -2 |
| 30 Oct 2026, 23:36 | 5,138 | +12 |
| 25 Oct 2026, 05:31 | 5,126 | +1 |
| 21 Oct 2026, 23:25 | 5,125 | +9 |
| 18 Oct 2026, 08:57 | 5,116 | -4 |
| 12 Oct 2026, 23:19 | 5,120 | -3 |
| 6 Oct 2026, 09:15 | 5,123 | +8 |
| 28 Sept 2026, 20:38 | 5,115 | +14 |
| 19 Sept 2026, 09:39 | 5,101 | +12 |
| 15 Sept 2026, 04:58 | 5,089 | -3 |
| 11 Sept 2026, 19:40 | 5,092 | +13 |
| 6 Sept 2026, 22:39 | 5,079 | +3 |
| 2 Sept 2026, 08:04 | 5,076 | +5 |
| 1 Sept 2026, 12:26 | 5,071 | no change |
| 30 Aug 2026, 00:38 | 5,071 | +8 |
| 27 Aug 2026, 09:12 | 5,063 | +18 |
| 24 Aug 2026, 01:33 | 5,045 | +18 |
| 19 Aug 2026, 23:22 | 5,027 | +10 |
| 16 Aug 2026, 18:43 | 5,017 | +12 |
| 13 Aug 2026, 15:27 | 5,005 | 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.
@DJPhellix · 31,969
Telegram ranks this channel #8 of 63 here — alongside 62 others — read 7 September 2026
@TehBeatz · 23,124
Telegram ranks this channel #49 of 66 here — alongside 65 others — read 18 September 2026
@ArashMohseni · 74,286
Telegram ranks this channel #67 of 86 here — alongside 85 others — read 22 August 2026
@deepdisco1 · 129,999
Telegram ranks this channel #76 of 88 here — alongside 87 others — read 13 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“NamitoMusic” (@namitomusic), 5,136 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/namitomusic.
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.