ещё походу и аллергия началась
custom 545182011302192085726custom 52986350621184701707custom 53415288146042760075

Channel
@zlayazlt
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
2,430subscribers
-59 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002035848597 |
|---|---|
| Type | Channel |
| Username | @zlayazlt |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/zlayazlt |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 05:12 | 2,430 | -6 |
| 27 Aug 2026, 14:59 | 2,436 | -3 |
| 24 Aug 2026, 11:49 | 2,439 | -11 |
| 20 Aug 2026, 20:22 | 2,450 | -14 |
| 17 Aug 2026, 18:52 | 2,464 | -9 |
| 14 Aug 2026, 17:57 | 2,473 | -10 |
| 11 Aug 2026, 13:56 | 2,483 | -5 |
| 8 Aug 2026, 05:25 | 2,488 | -1 |
| 7 Aug 2026, 20:17 | 2,489 | no change |
| 7 Aug 2026, 19:40 | 2,489 | first reading |
9 posts held, back to 13 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 9 posts for this entry, the most recent from 30 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
241 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 51.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5451820113021920857 | 123 | 51.0% | |
| custom 5312395686363285532 | 55 | 22.8% | |
| custom 5341528814604276007 | 42 | 17.4% | |
| custom 5298635062118470170 | 21 | 8.71% |
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 9 of the 9 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 241 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 13 July 2026 to 30 July 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 545182011302192085726custom 52986350621184701707custom 53415288146042760075
🧐
custom 534152881460427600715custom 52986350621184701708custom 54518201130219208575
Photo, posted without a caption
custom 545182011302192085713custom 53415288146042760077custom 53123956863632855324
ДОМОООЙ НАХ
custom 53123956863632855329custom 54518201130219208575custom 53415288146042760072
неделю назад в милане, вчера в словении, сегодня в хорватии. такого насыщенного лета у меня не было 🌟
custom 545182011302192085722custom 53123956863632855328custom 52986350621184701705
надеюсь будет много новых фоток разных
custom 545182011302192085714
Video message, posted without a caption
custom 54518201130219208579custom 53123956863632855324custom 53415288146042760074custom 52986350621184701701
хехе
custom 531239568636328553230custom 545182011302192085713custom 53415288146042760079
Video message, posted without a caption
custom 545182011302192085716
Showing the 9 most recent of 9 posts we hold for @zlayazlt. 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“злаязлата” (@zlayazlt), 2,430 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/zlayazlt.
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.