это я в 🐀 ела пиццу, пила пиво и праздновала др с девочками
custom 54205626896613450085custom 54228940451542539732custom 54227887153762891331custom 54247295810325786211

Channel
@diary_lilac
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
96subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002495640372 |
|---|---|
| Type | Channel |
| Username | @diary_lilac |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/diary_lilac |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 23:08 | 96 | +2 |
| 9 Aug 2026, 13:01 | 94 | no change |
| 7 Aug 2026, 17:06 | 94 | first reading |
15 posts held, back to 7 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 15 (7 July 2026 – 7 August 2026) |
| Views total | 688 |
| Reactions total | 74 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 13:01 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
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.
158 reactions across 15 posts, in 8 distinct kinds. The most used accounts for 26.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5422894045154253973 | 42 | 26.6% | |
| custom 5420562689661345008 | 39 | 24.7% | |
| custom 5424729581032578621 | 19 | 12.0% | |
| custom 5422341901338552439 | 18 | 11.4% | |
| custom 5422620223809266252 | 18 | 11.4% | |
| custom 5422467189829543120 | 15 | 9.49% | |
| custom 5422788715376289133 | 5 | 3.16% | |
| custom 5422433770689013946 | 2 | 1.27% |
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 areTelegram’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 15 of the 15 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 158reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 7 July 2026 to 7 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @diary_lilac. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 15 most recent posts we hold for this entry, published 7 July 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
это я в 🐀 ела пиццу, пила пиво и праздновала др с девочками
custom 54205626896613450085custom 54228940451542539732custom 54227887153762891331custom 54247295810325786211
душно так
custom 54226202238092662525
Как я хочу в Питер 😭
custom 54223419013385524394custom 54228940451542539733
сегодня у меня случилась остановка сердца 🤣 но там оказалось приглашение от девочек на девичник 🐱🥱🎉 а это я маме писала от испуга 🤣
custom 54228940451542539738custom 54205626896613450085
🥱
custom 54228940451542539738custom 54205626896613450084custom 54223419013385524392
Video message, posted without a caption
custom 54223419013385524396custom 54228940451542539736
Photo, posted without a caption
custom 542472958103257862110
погодка как кислый червяк
custom 54224671898295431204
сегодня был поход на рынок 1900р на фото ягодная кома у живота ✅
custom 54228940451542539738custom 54205626896613450085custom 54226202238092662525
Photo, posted without a caption
custom 54247295810325786215custom 54224671898295431204custom 54227887153762891334
официальное заявление! я не могу просто так пройти мимо своей собаки и не потискав его! лучший пес! всем спасибо!
custom 54224671898295431207custom 54226202238092662523
📸
custom 54205626896613450089custom 54226202238092662525
Showing the 12 most recent of 15 posts we hold for @diary_lilac. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Лиловый дневник ✨” (@diary_lilac), 96 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/diary_lilac.
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.