Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝗹𝗼𝘃𝗮𝗹𝘆𝗿𝗶𝗰

Channel

𝗹𝗼𝘃𝗮𝗹𝘆𝗿𝗶𝗰

@lovalyric

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

6,990subscribers

+3,281 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-1002252386841
TypeChannel
Username@lovalyric
CreatedBetween 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live17 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/lovalyric

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 12 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

3,7096,9905,349.510 August 2026 — 3,709 subscribers11 August 2026 — 3,720 subscribers14 August 2026 — 3,907 subscribers17 August 2026 — 4,203 subscribers20 August 2026 — 4,289 subscribers23 August 2026 — 4,457 subscribers26 August 2026 — 5,722 subscribers29 August 2026 — 6,175 subscribers29 August 2026 — 6,175 subscribers1 September 2026 — 6,411 subscribers4 September 2026 — 6,664 subscribers9 September 2026 — 6,849 subscribers13 September 2026 — 6,903 subscribers17 September 2026 — 6,990 subscribers10 August 202617 September 2026
14 measurements spanning 38 days, net +3,281. 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 3,217–7,482 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 03:006,990+87
13 Sept 2026, 06:166,903+54
9 Sept 2026, 18:206,849+185
4 Sept 2026, 20:426,664+253
1 Sept 2026, 05:436,411+236
29 Aug 2026, 11:276,175no change
29 Aug 2026, 03:536,175+453
26 Aug 2026, 10:245,722+1,265
23 Aug 2026, 21:074,457+168
20 Aug 2026, 10:064,289+86
17 Aug 2026, 09:464,203+296
14 Aug 2026, 03:373,907+187
11 Aug 2026, 00:373,720+11
10 Aug 2026, 14:013,709first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“𝗹𝗼𝘃𝗮𝗹𝘆𝗿𝗶𝗰” (@lovalyric), 6,990 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/lovalyric.

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.