Telegram RegisterThe public register of Telegram
Telegram profile photo for Memphis 66.6 / Phonk Community

Channel

Memphis 66.6 / Phonk Community

@memphisradio

Has discussion group

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

1,720subscribers

-6 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-1001401911780
TypeChannel
Username@memphisradio
CreatedBetween 1 April 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded24 September 2026
Last confirmed live16 November 2026
Measurements held21
Confirmed unchanged2 times, most recently 16 November 2026
On Telegramt.me/memphisradio

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 24 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,7091,7261,717.56 August 2026 — 1,726 subscribers7 August 2026 — 1,725 subscribers10 August 2026 — 1,724 subscribers12 August 2026 — 1,722 subscribers16 August 2026 — 1,723 subscribers23 August 2026 — 1,717 subscribers26 August 2026 — 1,715 subscribers29 August 2026 — 1,712 subscribers10 September 2026 — 1,711 subscribers19 September 2026 — 1,709 subscribers24 September 2026 — 1,709 subscribers29 September 2026 — 1,714 subscribers6 October 2026 — 1,712 subscribers12 October 2026 — 1,715 subscribers16 October 2026 — 1,717 subscribers19 October 2026 — 1,719 subscribers22 October 2026 — 1,721 subscribers25 October 2026 — 1,722 subscribers28 October 2026 — 1,720 subscribers3 November 2026 — 1,721 subscribers11 November 2026 — 1,720 subscribers1,7206 August 202611 November 2026
21 measurements spanning 97 days, net -6. 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,706–1,729 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
11 Nov 2026, 07:161,720-1
3 Nov 2026, 22:291,721+1
28 Oct 2026, 13:361,720-2
25 Oct 2026, 22:171,722+1
22 Oct 2026, 17:071,721+2
19 Oct 2026, 08:361,719+2
16 Oct 2026, 01:561,717+2
12 Oct 2026, 21:211,715+3
6 Oct 2026, 07:541,712-2
29 Sept 2026, 13:551,714+5
24 Sept 2026, 16:191,709no change
19 Sept 2026, 05:161,709-2
10 Sept 2026, 23:371,711-1
29 Aug 2026, 03:241,712-3
26 Aug 2026, 14:041,715-2
23 Aug 2026, 13:181,717-6
16 Aug 2026, 06:381,723+1
12 Aug 2026, 21:581,722-2
10 Aug 2026, 03:111,724-1
7 Aug 2026, 07:001,725first 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 11 November 2026 — this entry's latest reading, not the date you are reading this.

“Memphis 66.6 / Phonk Community” (@memphisradio), 1,720 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/memphisradio.

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.