Channel
винамп
@winampmp3
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,545subscribers
-74 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 | -1001502596964 |
|---|---|
| Type | Channel |
| Username | @winampmp3 |
| Created | Between 1 February 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/winampmp3 |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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, 03:29 | 3,545 | -1 |
| 2 Nov 2026, 13:36 | 3,546 | -4 |
| 26 Oct 2026, 20:08 | 3,550 | -6 |
| 24 Oct 2026, 01:31 | 3,556 | -2 |
| 21 Oct 2026, 06:20 | 3,558 | -3 |
| 17 Oct 2026, 22:55 | 3,561 | -3 |
| 15 Oct 2026, 04:17 | 3,564 | -2 |
| 12 Oct 2026, 01:57 | 3,566 | -5 |
| 5 Oct 2026, 12:38 | 3,571 | -10 |
| 27 Sept 2026, 15:55 | 3,581 | -8 |
| 18 Sept 2026, 03:55 | 3,589 | -5 |
| 13 Sept 2026, 18:15 | 3,594 | -4 |
| 10 Sept 2026, 03:55 | 3,598 | -3 |
| 7 Sept 2026, 20:50 | 3,601 | no change |
| 4 Sept 2026, 23:02 | 3,601 | -1 |
| 1 Sept 2026, 03:43 | 3,602 | -2 |
| 29 Aug 2026, 13:43 | 3,604 | -2 |
| 26 Aug 2026, 21:15 | 3,606 | -5 |
| 24 Aug 2026, 00:17 | 3,611 | -2 |
| 20 Aug 2026, 08:52 | 3,613 | 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.
@bestdjchannel · 39,852
Telegram ranks this channel #21 of 78 here — alongside 77 others — read 29 August 2026
@warhol · 27,438
Telegram ranks this channel #65 of 78 here — alongside 77 others — read 11 September 2026
@thequietplace · 51,200
Telegram ranks this channel #67 of 81 here — alongside 80 others — read 25 August 2026
@trap_critics · 29,726
Telegram ranks this channel #69 of 80 here — alongside 79 others — read 8 September 2026
@brokendance · 79,770
Telegram ranks this channel #84 of 84 here — alongside 83 others — read 18 August 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.
“винамп” (@winampmp3), 3,545 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/winampmp3.
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.