Channel
@lvnvrfls
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
189subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003239490100 |
|---|---|
| Type | Channel |
| Username | @lvnvrfls |
| Created | Between 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 3 times, most recently 19 September 2026 |
| On Telegram | t.me/lvnvrfls |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 16:37 | 189 | -3 |
| 16 Aug 2026, 19:55 | 192 | +1 |
| 9 Aug 2026, 07:12 | 191 | +1 |
| 8 Aug 2026, 12:02 | 190 | no change |
| 8 Aug 2026, 10:17 | 190 | first reading |
16 posts held, back to 19 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 16 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 11 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
483 reactions across 16 posts, in 15 distinct kinds. The most used accounts for 31.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5307861648302695920 | 153 | 31.7% | |
| custom 5240385298310898930 | 75 | 15.5% | |
| custom 5357497576025258236 | 56 | 11.6% | |
| custom 5366137396662384013 | 45 | 9.32% | |
| custom 5444930216680004815 | 35 | 7.25% | |
| custom 5258424955523057561 | 34 | 7.04% | |
| custom 5408856305324556262 | 28 | 5.80% | |
| custom 5289505804188145487 | 15 | 3.11% | |
| custom 5447348991937229569 | 13 | 2.69% | |
| custom 5206287892250377287 | 9 | 1.86% | |
| custom 5371017441583320452 | 6 | 1.24% | |
| custom 5258387460458560375 | 5 | 1.04% | |
| custom 5445295138576310045 | 4 | 0.828% | |
| custom 5299020879030666687 | 3 | 0.621% | |
| custom 5445355160744273424 | 2 | 0.414% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 16 of the 16 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 483 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 19 July 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
МИТЧ. Вы врали мне, Бланш. БЛАНШ. Бросьте... не врала! МИТЧ. Все было ложью, ложь на лжи, и на словах и в мыслях – одно вранье! БЛАНШ. Неправда! В сердце своем я не солгала вам ни разу...
custom 528950580418814548715custom 53710174415833204526custom 52583874604585603755custom 52990208790306666871
эта красивейшая женщина и грандиознейшая артистка только что закрыла свой театральный сезон. поклон и спасибо Ей за эти 11 месяцев театрального счастья. да будет отдых! хотя бы от театра) до луны и обратно 🌕🤍
custom 535749757602525823623custom 53661373966623840138custom 52403852983108989305custom 53078616483026959203
😇
custom 535749757602525823616custom 530786164830269592010custom 52403852983108989305
Иногда мечты исполняются. И тогда на них смотрят именно так 🥰😻
custom 530786164830269592031custom 53574975760252582367custom 54449302166800048155custom 54452951385763100454custom 53661373966623840131
И ради тебя на все я готов. Ты любовь моя, я без тебя никто... 🤍
custom 544493021668000481530custom 53661373966623840137custom 53078616483026959205custom 54088563053245562622custom 54453551607442734242custom 52584249555230575611
что-то на цветочном 💐
custom 530786164830269592017custom 53661373966623840135custom 52403852983108989304
Новости культуры. Сюжет о вечере, посвященном Микаэлю Таривердиеву в рамках фестиваля «Вдохновение»
custom 530786164830269592014custom 52403852983108989306custom 53661373966623840134
Ты — это я. Меж мной и мной не существует расстоянья. 💓🪶
custom 530786164830269592020custom 53661373966623840135custom 53574975760252582364custom 52062878922503772871custom 52403852983108989301
– Спасибо вам большое, что вы выдержали, что не ушли, что были с нами! Мы очень хотели вам рассказать эту историю про нашего замечательного и любимого композитора Микаэля Леоновича Таривердиева. ну любовь! ❤️
custom 524038529831089893018custom 53078616483026959208custom 53574975760252582365
Микаэл Таривердиев. Семнадцать мгновений судьбы 🎹🎶
custom 530786164830269592014custom 52990208790306666872custom 53574975760252582361
фотосет от мужа
custom 530786164830269592018custom 53661373966623840134custom 54473489919372295693custom 52584249555230575611
у меня инфаркт.
custom 544734899193722956910
Showing the 12 most recent of 16 posts we hold for @lvnvrfls. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“Любовь никогда не перестает” (@lvnvrfls), 189 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/lvnvrfls.
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.