лебединое озеро
custom 531904466510467862018custom 53865769914052244069custom 53458414857554645307

Channel
@lizaeveryday
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
192subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001299838112 |
|---|---|
| Type | Channel |
| Username | @lizaeveryday |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 8 September 2026 |
| On Telegram | t.me/lizaeveryday |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 00:27 | 192 | +1 |
| 14 Aug 2026, 22:18 | 191 | -1 |
| 8 Aug 2026, 11:50 | 192 | no change |
| 7 Aug 2026, 10:39 | 192 | first reading |
6 posts held, back to 21 June 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 6 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
179 reactions across 6 posts, in 7 distinct kinds. The most used accounts for 26.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5258264813372455622 | 47 | 26.3% | |
| custom 5319044665104678620 | 43 | 24.0% | |
| custom 5345841485755464530 | 30 | 16.8% | |
| custom 5426847090103825668 | 30 | 16.8% | |
| custom 5386427831486000700 | 16 | 8.94% | |
| custom 5386576991405224406 | 9 | 5.03% | |
| custom 5251570071754520010 | 4 | 2.23% |
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 6 of the 6 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 179 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 21 June 2026 to 4 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 531904466510467862018custom 53865769914052244069custom 53458414857554645307
хочу жить в домике на отшибе леса
custom 525826481337245562212custom 54268470901038256688custom 53458414857554645307custom 53190446651046786201
He makes me lie down in green pastures, he leads me beside quiet waters. — Psalm 23:2
custom 534584148575546453016custom 525826481337245562213custom 542684709010382566810
Урааааа я подцепила клеща 😎 summer vibe activity
custom 53864278314860007007custom 52515700717545200104custom 54268470901038256684
in the world’s pink era
custom 525826481337245562222
С каждым днём ощущение своей беспомощности перед обстоятельствами всё больше напоминает полноценный завтрак, обед и ужин, когда ты уже сыт и переполнен тревогой настолько, что голод отсутствует вовсе, остается только переваривать энтропию. Скучаю каждый день по самой себе, не помня, как снова оказалась в этой яме самоотторжения и непринятия.
custom 531904466510467862024custom 53864278314860007009custom 54268470901038256688
Showing the 6 most recent of 6 posts we hold for @lizaeveryday. 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“fleur de Liza” (@lizaeveryday), 192 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/lizaeveryday.
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.