Channel
Mellow and sleazy DIscography. 🌐
@mellowandsleazy
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,973subscribers
-132 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001615925729 |
|---|---|
| Type | Channel |
| Username | @mellowandsleazy |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/mellowandsleazy |
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 89% 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 |
|---|---|---|
| 5 Nov 2026, 02:27 | 3,973 | -14 |
| 1 Nov 2026, 15:45 | 3,987 | -8 |
| 30 Oct 2026, 00:11 | 3,995 | -14 |
| 24 Oct 2026, 01:50 | 4,009 | -8 |
| 21 Oct 2026, 07:18 | 4,017 | -6 |
| 18 Oct 2026, 15:31 | 4,023 | -16 |
| 15 Oct 2026, 18:57 | 4,039 | -16 |
| 12 Oct 2026, 19:07 | 4,055 | -14 |
| 5 Oct 2026, 22:58 | 4,069 | -14 |
| 28 Sept 2026, 21:20 | 4,083 | +2 |
| 18 Sept 2026, 17:01 | 4,081 | -6 |
| 14 Sept 2026, 00:40 | 4,087 | -1 |
| 10 Sept 2026, 08:18 | 4,088 | -4 |
| 5 Sept 2026, 12:58 | 4,092 | -9 |
| 4 Sept 2026, 23:39 | 4,101 | no change |
| 1 Sept 2026, 05:57 | 4,101 | -4 |
| 28 Aug 2026, 18:30 | 4,105 | 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.
@amapianophilosophysa · 18,879
Telegram ranks this channel #2 of 47 here — alongside 46 others — read 30 September 2026
@amapiano929 · 22,644
Telegram ranks this channel #13 of 58 here — alongside 57 others — read 18 September 2026
@Ehaamofficial · 30,953
Telegram ranks this channel #23 of 59 here — alongside 58 others — read 15 September 2026
@AMAPIANOszn · 94,106
Telegram ranks this channel #24 of 60 here — alongside 59 others — read 28 August 2026
@LeeMcKrazy_ScottsMaphuma · 31,180
Telegram ranks this channel #25 of 59 here — alongside 58 others — read 4 September 2026
This channel appears in 5 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 November 2026 — this entry's latest reading, not the date you are reading this.
“Mellow and sleazy DIscography. 🌐” (@mellowandsleazy), 3,973 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/mellowandsleazy.
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.