Channel
Nacimmusic
@nacimmusic
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,491subscribers
-88 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001704203378 |
|---|---|
| Type | Channel |
| Username | @nacimmusic |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/nacimmusic |
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 84% 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 |
|---|---|---|
| 4 Nov 2026, 15:29 | 4,491 | +4 |
| 1 Nov 2026, 09:20 | 4,487 | -2 |
| 29 Oct 2026, 10:08 | 4,489 | +9 |
| 26 Oct 2026, 16:56 | 4,480 | -9 |
| 23 Oct 2026, 08:36 | 4,489 | -7 |
| 20 Oct 2026, 12:36 | 4,496 | +2 |
| 14 Oct 2026, 23:46 | 4,494 | -5 |
| 11 Oct 2026, 12:41 | 4,499 | -14 |
| 5 Oct 2026, 06:17 | 4,513 | -31 |
| 27 Sept 2026, 00:18 | 4,544 | -20 |
| 15 Sept 2026, 05:55 | 4,564 | -1 |
| 11 Sept 2026, 15:55 | 4,565 | +37 |
| 6 Sept 2026, 22:00 | 4,528 | -9 |
| 3 Sept 2026, 12:11 | 4,537 | no change |
| 2 Sept 2026, 06:28 | 4,537 | -7 |
| 30 Aug 2026, 02:05 | 4,544 | -8 |
| 26 Aug 2026, 15:43 | 4,552 | -3 |
| 23 Aug 2026, 23:25 | 4,555 | -2 |
| 20 Aug 2026, 07:52 | 4,557 | -8 |
| 17 Aug 2026, 13:05 | 4,565 | 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.
@roman4u · 24,580
Telegram ranks this channel #47 of 47 here — alongside 46 others — read 15 September 2026
@Chai_with_banafsheh · 21,576
Telegram ranks this channel #53 of 64 here — alongside 63 others — read 1 October 2026
@Twitter_twit · 158,143
Telegram ranks this channel #54 of 57 here — alongside 56 others — read 14 August 2026
@MusicGhadimic · 151,560
Telegram ranks this channel #75 of 82 here — alongside 81 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Nacimmusic” (@nacimmusic), 4,491 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/nacimmusic.
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.