Channel
LOVEMUSIC0181
@lovemusic0181
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,332subscribers
-133 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002002904465 |
|---|---|
| Type | Channel |
| Username | @lovemusic0181 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/lovemusic0181 |
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 88% 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 |
|---|---|---|
| 7 Nov 2026, 22:56 | 3,332 | -7 |
| 4 Nov 2026, 11:36 | 3,339 | -3 |
| 1 Nov 2026, 18:27 | 3,342 | +1 |
| 26 Oct 2026, 20:46 | 3,341 | -7 |
| 23 Oct 2026, 23:09 | 3,348 | -2 |
| 21 Oct 2026, 09:17 | 3,350 | -2 |
| 18 Oct 2026, 10:59 | 3,352 | -3 |
| 15 Oct 2026, 08:31 | 3,355 | -8 |
| 12 Oct 2026, 08:16 | 3,363 | -15 |
| 5 Oct 2026, 08:56 | 3,378 | -17 |
| 27 Sept 2026, 04:58 | 3,395 | -13 |
| 17 Sept 2026, 12:39 | 3,408 | -4 |
| 13 Sept 2026, 06:01 | 3,412 | -6 |
| 9 Sept 2026, 07:59 | 3,418 | -2 |
| 8 Sept 2026, 21:22 | 3,420 | no change |
| 4 Sept 2026, 02:42 | 3,420 | -3 |
| 31 Aug 2026, 08:53 | 3,423 | -4 |
| 28 Aug 2026, 14:37 | 3,427 | -7 |
| 25 Aug 2026, 04:34 | 3,434 | -7 |
| 21 Aug 2026, 21:07 | 3,441 | 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.
@Pen_Musix · 266,263
Telegram ranks this channel #12 of 84 here — alongside 83 others — read 10 August 2026
@NotHappy_Remix · 119,944
Telegram ranks this channel #20 of 65 here — alongside 64 others — read 13 August 2026
@TurkMusicTranslate · 47,699
Telegram ranks this channel #46 of 62 here — alongside 61 others — read 26 August 2026
@zheluofen1 · 81,547
Telegram ranks this channel #46 of 89 here — alongside 88 others — read 18 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“LOVEMUSIC0181” (@lovemusic0181), 3,332 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/lovemusic0181.
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.