Неделю назад были в ресторане, а 3 часа назад там произошел взрыв, погибло 3 человека, 20 ранены… Грустное напоминание на ночь, что все «проблемы», о которых мы переживаем – ничтожны, цените сегодняшний день 💔
💔5😭3

Channel
@ivicheva
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
209subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002350237097 |
|---|---|
| Type | Channel |
| Username | @ivicheva |
| Description | для связи в тг: @vladaivicheva |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ivicheva |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 11:03 | 209 | no change |
| 7 Aug 2026, 15:34 | 209 | first reading |
9 posts held, back to 8 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. It is computed over the 5 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 1 August 2026 |
|---|---|
| Posts held | 9 (8 July 2026 – 1 August 2026) |
| Views total | 976 |
| Reactions total | 68 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 11:03 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.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 4 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.
99 reactions across 8 posts, in 17 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 33 | 33.3% | |
| 🔥 | 24 | 24.2% | |
| 👎 | 7 | 7.07% | |
| 💔 | 5 | 5.05% | |
| 🥰 | 5 | 5.05% | |
| 👌 | 4 | 4.04% | |
| 👍 | 3 | 3.03% | |
| 💊 | 3 | 3.03% | |
| 😁 | 3 | 3.03% | |
| 😍 | 3 | 3.03% | |
| 😭 | 3 | 3.03% | |
| custom 5370860795536098088 | 1 | 1.01% | |
| 👏 | 1 | 1.01% | |
| 😇 | 1 | 1.01% | |
| 😢 | 1 | 1.01% | |
| 🤔 | 1 | 1.01% | |
| 🤯 | 1 | 1.01% |
Custom emoji. One 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 count beside it isTelegram’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 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 99reactions 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 8 July 2026 to 1 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.
Неделю назад были в ресторане, а 3 часа назад там произошел взрыв, погибло 3 человека, 20 ранены… Грустное напоминание на ночь, что все «проблемы», о которых мы переживаем – ничтожны, цените сегодняшний день 💔
💔5😭3
Video message, posted without a caption
А прямо сейчас в 00:00 у него вышел трек… внимание… с IOWA 😍💔 https://band.link/__lovlu
❤4👎2custom 53708607955360980881
Я вам не рассказывала, но эта песня и хит «Тону тону я в глазах твоих тону» – песни Влада – мужа моего продюсера Даши @daibogproduction, который помогал мне в создании песни «Се ля ви» Вот кусочек видео процесса, которым нигде не делилась) Для вас в канале, как всегда, эклюзивный эклюзив)) И знаете, это такое классное чувство, видеть, как ребята, которых ты знаешь 7 лет, и наблюдал весь путь, пришли к успеху 😍 Ког…
❤6👍3🔥3👎1👏1
Video message, posted without a caption
❤5😁3😍3👎1🤔1
Готовлю сейчас рассказ о себе и своем пути для хайлайтс в Инстаграме, роюсь в архивах, и чуть не плачу… Посмотрите, какая малышка 🥹💔
❤10🔥9🥰5👎1😇1
Вернулась в инстаграм 🌺 instagram.com/ivicheva
❤8👌4🔥2👎1
Video message, posted without a caption
🔥9👎1
Я разбила телефон и заболела в самой середине отпуска: ужасно болит горло, заложен нос и жар (учитывая, что здесь всегда выше 30 градусов… грешу на кондей) shit happens 💩
💊3🔥1🤯1😢1
Showing the 9 most recent of 9 posts we hold for @ivicheva. 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.
Citation-graph rank — 325,950 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Владлена MAGDALENA” (@ivicheva), 209 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/ivicheva.
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.