Channel
🌈⃤ 🅼🆄🅢🅸🅲ʀᴀɪɴⒹʀᴏᴘꜱ
@musicraindrops
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,322subscribers
+269 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 | -1001520356185 |
|---|---|
| Type | Channel |
| Username | @musicraindrops |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/musicraindrops |
Topic
Other / unclassifiable — 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 98% 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 |
|---|---|---|
| 18 Sept 2026, 14:02 | 5,322 | -18 |
| 14 Sept 2026, 07:56 | 5,340 | -8 |
| 10 Sept 2026, 15:39 | 5,348 | +296 |
| 5 Sept 2026, 11:14 | 5,052 | +8 |
| 2 Sept 2026, 00:24 | 5,044 | -10 |
| 1 Sept 2026, 12:36 | 5,054 | no change |
| 27 Aug 2026, 15:07 | 5,054 | -1 |
| 24 Aug 2026, 19:28 | 5,055 | -3 |
| 21 Aug 2026, 07:44 | 5,058 | +7 |
| 17 Aug 2026, 22:43 | 5,051 | -7 |
| 14 Aug 2026, 20:15 | 5,058 | +6 |
| 11 Aug 2026, 01:11 | 5,052 | -2 |
| 8 Aug 2026, 04:03 | 5,054 | +1 |
| 7 Aug 2026, 09:49 | 5,053 | 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.
@Purrask · 41,613
Telegram ranks this channel #11 of 55 here — alongside 54 others — read 29 August 2026
@club27rock · 95,996
Telegram ranks this channel #35 of 78 here — alongside 77 others — read 21 August 2026
@MetalWorld · 26,138
Telegram ranks this channel #40 of 73 here — alongside 72 others — read 13 September 2026
@radiometal_channel · 24,270
Telegram ranks this channel #45 of 68 here — alongside 67 others — read 16 September 2026
@makhfigah_channel · 63,252
Telegram ranks this channel #49 of 92 here — alongside 91 others — read 21 August 2026
@Bikalam_Nava · 27,692
Telegram ranks this channel #52 of 74 here — alongside 73 others — read 10 September 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“🌈⃤ 🅼🆄🅢🅸🅲ʀᴀɪɴⒹʀᴏᴘꜱ” (@musicraindrops), 5,322 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/musicraindrops.
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.