Channel
dj 🪐RaMMM🫧🫧
@djRaMMM
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,172subscribers
-16 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001024105347 |
|---|---|
| Type | Channel |
| Username | @djRaMMM |
| Created | Between 1 January 2016 and 31 March 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 October 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 5 October 2026 |
| On Telegram | t.me/djRaMMM |
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 5 October 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 5 Oct 2026, 19:40 | 1,172 | -2 |
| 5 Oct 2026, 03:23 | 1,174 | no change |
| 28 Sept 2026, 18:57 | 1,174 | +1 |
| 15 Sept 2026, 06:15 | 1,173 | -3 |
| 11 Sept 2026, 18:40 | 1,176 | +2 |
| 2 Sept 2026, 18:44 | 1,174 | -3 |
| 30 Aug 2026, 09:39 | 1,177 | -1 |
| 27 Aug 2026, 11:55 | 1,178 | -3 |
| 24 Aug 2026, 13:11 | 1,181 | -1 |
| 20 Aug 2026, 15:48 | 1,182 | -1 |
| 17 Aug 2026, 22:32 | 1,183 | -1 |
| 14 Aug 2026, 23:48 | 1,184 | -2 |
| 9 Aug 2026, 07:11 | 1,186 | -2 |
| 5 Aug 2026, 22:20 | 1,188 | 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.
@Hoolex1 · 19,567
Telegram ranks this channel #34 of 48 here — alongside 47 others — read 1 October 2026
@DJRasheTMusiC · 42,731
Telegram ranks this channel #45 of 47 here — alongside 46 others — read 28 August 2026
@DJPhellix · 31,683
Telegram ranks this channel #56 of 63 here — alongside 62 others — read 7 September 2026
@dj_soushi_music · 126,913
Telegram ranks this channel #57 of 87 here — alongside 86 others — read 13 August 2026
@Vocalistxxx · 21,330
Telegram ranks this channel #60 of 68 here — alongside 67 others — read 24 September 2026
@MrRAP_Org · 28,636
Telegram ranks this channel #60 of 71 here — alongside 70 others — read 9 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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“dj 🪐RaMMM🫧🫧” (@djRaMMM), 1,172 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/djRaMMM.
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.