Пока детей нет - наношу психологические травмы Йоше))
custom 520897357395526443811❤🔥7🔥3

Channel
@kelizaitseva
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
182subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001706632939 |
|---|---|
| Type | Channel |
| Username | @kelizaitseva |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/kelizaitseva |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 09:38 | 182 | -1 |
| 29 Aug 2026, 10:14 | 183 | -1 |
| 22 Aug 2026, 18:23 | 184 | +1 |
| 8 Aug 2026, 12:45 | 183 | no change |
| 8 Aug 2026, 02:25 | 183 | +1 |
| 7 Aug 2026, 12:58 | 182 | first reading |
8 posts held, back to 26 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 8 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 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.
168 reactions across 8 posts, in 7 distinct kinds. The most used accounts for 31.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 53 | 31.5% | |
| custom 5253638042672979953 | 38 | 22.6% | |
| 🔥 | 21 | 12.5% | |
| custom 5426975878993168718 | 18 | 10.7% | |
| custom 5208973573955264438 | 17 | 10.1% | |
| custom 5366600793568866294 | 13 | 7.74% | |
| 😢 | 8 | 4.76% |
Custom emoji. 4 of the rows above are 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 8 of the 8 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 168 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 26 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 520897357395526443811❤🔥7🔥3
Это самая большая ложь 😭💔
😢8custom 52536380426729799537custom 52089735739552644386
Никак не дошью это шикарное платье, а уже так хочется его выгулять 💔💔💔💔
❤🔥10custom 54269758789931687185custom 53666007935688662943
Рандом выходных дней 🍬🍼
custom 525363804267297995312custom 54269758789931687187🔥2❤🔥1
Забыла похвастаться юбкой, которую сама сшила 🪡 Очень нравится 😻
custom 525363804267297995315🔥8❤🔥4
Весь автопарк прошел ТО 🧵
custom 536660079356886629410❤🔥3🔥3
Ну каковы 💔💔💔 Скоро будут новости про мою закваску
❤🔥14🔥5custom 54269758789931687183
праздничный завтрак с тортом 🤩 Отмечаем первый маленький юбилей: Много совместных воспоминаний, еще больше планов на будущее 🙏🤩 Утром осознала, что у нас ни одного семейного альбома нет, а сколько все уже пережили вместе, наверное уже пора фотографии печатать? 26.07.2021 🤍
❤🔥14custom 52536380426729799534custom 54269758789931687183
Showing the 8 most recent of 8 posts we hold for @kelizaitseva. 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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“Мы не одинаковые 🧸💔” (@kelizaitseva), 182 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/kelizaitseva.
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.