Telegram RegisterThe public register of Telegram
Telegram profile photo for LFM music ™

Channel

LFM music ™

@LFMMUSIC

Has discussion group

On this record: Topic · Growth · Engagement · Citations · Telegram's recommendations · Cite this entry

4,210subscribers

-116 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001101690313
TypeChannel
Username@LFMMUSIC
CreatedBetween 1 February 2017 and 28 February 2018 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 September 2026
Last confirmed live23 October 2026
Measurements held21
Confirmed unchanged1 time, most recently 23 October 2026
On Telegramt.me/LFMMUSIC

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 13 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 why it has no browse page of its own yet.

Growth

4,2104,3264,2686 August 2026 — 4,326 subscribers7 August 2026 — 4,324 subscribers10 August 2026 — 4,319 subscribers13 August 2026 — 4,311 subscribers16 August 2026 — 4,306 subscribers19 August 2026 — 4,304 subscribers23 August 2026 — 4,300 subscribers26 August 2026 — 4,298 subscribers30 August 2026 — 4,291 subscribers2 September 2026 — 4,288 subscribers4 September 2026 — 4,288 subscribers7 September 2026 — 4,284 subscribers11 September 2026 — 4,281 subscribers15 September 2026 — 4,274 subscribers26 September 2026 — 4,262 subscribers5 October 2026 — 4,246 subscribers10 October 2026 — 4,237 subscribers14 October 2026 — 4,230 subscribers17 October 2026 — 4,222 subscribers20 October 2026 — 4,215 subscribers23 October 2026 — 4,210 subscribers6 August 202623 October 2026
21 measurements spanning 78 days, net -116. 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 4,193–4,343 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
23 Oct 2026, 14:184,210-5
20 Oct 2026, 07:094,215-7
17 Oct 2026, 04:284,222-8
14 Oct 2026, 11:514,230-7
10 Oct 2026, 22:214,237-9
5 Oct 2026, 00:574,246-16
26 Sept 2026, 01:194,262-12
15 Sept 2026, 09:594,274-7
11 Sept 2026, 11:204,281-3
7 Sept 2026, 01:554,284-4
4 Sept 2026, 12:364,288no change
2 Sept 2026, 08:044,288-3
30 Aug 2026, 07:044,291-7
26 Aug 2026, 23:354,298-2
23 Aug 2026, 16:444,300-4
19 Aug 2026, 18:324,304-2
16 Aug 2026, 19:044,306-5
13 Aug 2026, 11:484,311-8
10 Aug 2026, 11:014,319-5
7 Aug 2026, 16:554,324first 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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.

DJ Phellix
@DJPhellix · 31,805
Telegram ranks this channel #53 of 63 here — alongside 62 others — read 7 September 2026
Turkish7en🌶️ | (شجاع)
@turkish7en · 21,443
Telegram ranks this channel #60 of 62 here — alongside 61 others — read 23 September 2026
کانال ویکی موزیک©
@iRwikimusic · 31,427
Telegram ranks this channel #62 of 62 here — alongside 61 others — read 5 September 2026

This channel appears in 3 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 23 October 2026 — this entry's latest reading, not the date you are reading this.

“LFM music ™” (@LFMMUSIC), 4,210 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/LFMMUSIC.

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.