Telegram RegisterThe public register of Telegram

Channel

@lyrics of life🎼🎼

@lilyrics11

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

248subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001490676517
TypeChannel
Username@lilyrics11
CreatedBetween 1 May 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/lilyrics11

Growth

2486 Aug 2026, 20:33 — 248 subscribers7 Aug 2026, 02:30 — 248 subscribers6 Aug 2026, 20:337 Aug 2026, 02:30
2 measurements taken within a single day. 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 247–249 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 02:30248no change
6 Aug 2026, 20:33248first reading

Engagement

15 posts held, back to 8 October 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 15 posts for this entry, the most recent from 1 December 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
3,960
Videos
508
Links
71

Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

1 Dec 2024, 13:10 UTC156 viewsread 7 August 2026

https://t.me/offical_dark_feelings

Signed ℝ.𝕐 ✞ 🕊

18 Jul 2023, 09:03 UTC515 viewsread 7 August 2026

https://t.me/offical_dark_feelings

Signed ℝ𝕠𝕓𝕖l.𝕐 ✞ 🕊

Showing the 12 most recent of 15 posts we hold for @lilyrics11. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Mentions

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.

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

“@lyrics of life🎼🎼” (@lilyrics11), 248 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/lilyrics11.

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.