Channel
@Vikaa_zhukova
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
400subscribers
+0 since we began measuring on 2 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002956588731 |
|---|---|
| Type | Channel |
| Username | @Vikaa_zhukova |
| Description | Простые рецепты на каждый день Для мам и малышей Быстро • вкусно • без заморочек Связь со мной: @Zhukova_Vikaa |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 October 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Vikaa_zhukova |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Oct 2026, 03:22 | 400 | no change |
| 2 Oct 2026, 02:47 | 400 | first reading |
7 posts held, back to 29 September 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.
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 1 October 2026 |
|---|---|
| Posts held | 7 (29 September 2026 – 1 October 2026) |
| Views total | 524 |
| Reactions total | 275 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Oct 2026, 03:22 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 2 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
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.
275 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 32.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 88 | 32.0% | |
| 🔥 | 81 | 29.5% | |
| custom 5357413854227742399 | 57 | 20.7% | |
| custom 5357428667569948200 | 41 | 14.9% | |
| 🥰 | 8 | 2.91% |
Custom emoji. 2 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 7 of the 7 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 275 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 29 September 2026 to 1 October 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.
Обзор с Чижика 1️⃣Посуда класс, по качеству хороша Прям Икеа подъехала 2️⃣Сыр Чечил Очень люблю, цена отличная 3️⃣Селёдочка именно такая обожаю 4️⃣Этой фабрики люблю конфеты 5️⃣Мягкие вафельки Съедаются за раз 6️⃣Чачжан мен Любим иногда 7️⃣Мягкие вафли в другой вариации Пока я выбираю вафельницу тестирую покупные😅 8️⃣Арахисовая паста брала такую не плохая #обзоры
❤25🔥18custom 535742866756994820013custom 53574138542277423991
День добрый) Мне ж не отдыхается как проводила Стефани Кстати сегодня не плакала, нормально И вчера вечером снова придумывала всякие игры с участием сада 😅 Снимаю новый рецепт, я на сегодня все ухайдокалась Теперь бы убрать все
custom 535741385422774239919custom 535742866756994820015🔥5
Video message, posted without a caption
❤9🥰7custom 53574286675699482005🔥3
5 рецептов, которые помогают добавить овощи в детское меню без уговоров и «съешь ещё ложечку». ➖Шпинатные оладушки ➖Омлето - пицца с брокколи ➖Шпинатные блинчики ➖Блинчик с брокколи ➖Вафли из брокколи Наши любимчики повторяем часто, у Стефани фаворит блинчик с брокколи 🤤 Ваши детки хорошо кушают овощи и зелень или добавляете в блюда готовые? Сохраняй подборку и отправляй маме, которая уже не знает, куда спрятать б…
🔥20❤15custom 535741385422774239913
Всем привет ) Вот такая хмурная Стефа в 7 утра, только ближе к садику начинает говорить😊😅 Но сегодня молодец не плакала Погодка хороша сегодня, солнышко У меня зацветает женское счастье 👍 Все цветы совсем плохи, этот отвозила к свекрови в деревню она рассадила в обычную землю и все вуаля Разрослись цветут и радуются Взяла один обратно, посмотрим сколько проживет 😅 Как ваше утро?
❤17custom 53574138542277423999custom 53574286675699482008
Video message, posted without a caption
🔥12🥰1
На завтрак сегодня: ➖омлет со шпинатом, бутерброд с авокадо ➖йогурт + клубника + миндаль ➖кофе. Мы сегодня пошли в сад. Эх, тяжело что-то мне… Хотя и Стефа упиралась: «Не пойду, не хочу». Ну, посмотрим. И такой холод сегодня и туман у нас Что у вас на завтрак?🤍 #сервировка
🔥23❤22custom 535741385422774239915
Showing the 7 most recent of 7 posts we hold for @Vikaa_zhukova. 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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“Завтрак у Стефани | простые рецепты” (@Vikaa_zhukova), 400 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/Vikaa_zhukova.
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.