Telegram RegisterThe public register of Telegram
Telegram profile photo for Красное Радио mp3

Channel

Красное Радио mp3

@krasnoemp3

On this record: Topic · Growth · Engagement · Cite this entry

1,449subscribers

+32 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001563270087
TypeChannel
Username@krasnoemp3
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 September 2026
Last confirmed live18 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/krasnoemp3

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 29 September 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 the other topics.

Growth

1,4171,4491,4336 August 2026 — 1,417 subscribers10 August 2026 — 1,418 subscribers16 August 2026 — 1,420 subscribers19 August 2026 — 1,421 subscribers23 August 2026 — 1,422 subscribers26 August 2026 — 1,423 subscribers29 August 2026 — 1,424 subscribers1 September 2026 — 1,422 subscribers5 September 2026 — 1,423 subscribers10 September 2026 — 1,424 subscribers28 September 2026 — 1,433 subscribers29 September 2026 — 1,433 subscribers6 October 2026 — 1,431 subscribers12 October 2026 — 1,432 subscribers18 October 2026 — 1,431 subscribers21 October 2026 — 1,430 subscribers24 October 2026 — 1,432 subscribers27 October 2026 — 1,434 subscribers2 November 2026 — 1,438 subscribers5 November 2026 — 1,443 subscribers9 November 2026 — 1,445 subscribers13 November 2026 — 1,447 subscribers18 November 2026 — 1,449 subscribers6 August 202618 November 2026
23 measurements spanning 104 days, net +32. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,412–1,454 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)SubscribersChange
18 Nov 2026, 11:561,449+2
13 Nov 2026, 12:461,447+2
9 Nov 2026, 01:001,445+2
5 Nov 2026, 11:181,443+5
2 Nov 2026, 19:271,438+4
27 Oct 2026, 15:591,434+2
24 Oct 2026, 17:101,432+2
21 Oct 2026, 18:471,430-1
18 Oct 2026, 20:461,431-1
12 Oct 2026, 16:191,432+1
6 Oct 2026, 02:591,431-2
29 Sept 2026, 03:311,433no change
28 Sept 2026, 13:351,433+9
10 Sept 2026, 15:391,424+1
5 Sept 2026, 12:211,423+1
1 Sept 2026, 04:181,422-2
29 Aug 2026, 07:451,424+1
26 Aug 2026, 07:531,423+1
23 Aug 2026, 01:271,422+1
19 Aug 2026, 10:141,421first 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.

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 November 2026 — this entry's latest reading, not the date you are reading this.

“Красное Радио mp3” (@krasnoemp3), 1,449 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/krasnoemp3.

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.