Channel
@puzikova479
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
135subscribers
+2 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001637304475 |
|---|---|
| Type | Channel |
| Username | @puzikova479 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/puzikova479 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 02:17 | 135 | +1 |
| 2 Sept 2026, 00:27 | 134 | +1 |
| 25 Aug 2026, 03:36 | 133 | -1 |
| 17 Aug 2026, 10:25 | 134 | +1 |
| 9 Aug 2026, 08:15 | 133 | no change |
| 9 Aug 2026, 08:03 | 133 | first reading |
8 posts held, back to 23 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
61 reactions across 8 posts, in 7 distinct kinds. The most used accounts for 34.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 21 | 34.4% | |
| ❤ | 19 | 31.1% | |
| custom 5330353898110592104 | 11 | 18.0% | |
| custom 5332572377568018267 | 4 | 6.56% | |
| custom 5431840354657649314 | 4 | 6.56% | |
| 👍 | 1 | 1.64% | |
| 🤯 | 1 | 1.64% |
Custom emoji. 3 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 61 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 23 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.
Нууу подведем итоги за этот сезон: Жим ногами 130кг (думала что уже все и больше не будем работать на ноги) Прокачка большой широчайшей мышцы спины 70кг с подстраховкой 60 самостоятельно Бег пока есть время буду прокачивать Было много побед и неудач, но это не значит что нужно уходить со своего пути) так что идем дальше #judo
custom 53303538981105921045🔥2
Просто бег… К сожалению у меня не получилось подойти к тому результату который хотела, и когда к нему приближалась, то потом снова появились лишние минуты( Буду работать🥲
🔥6
Так первое это у нас 03.08 бегать в жару ужасно, по этому очень плохое время (так же я часы не вовремя включила 😅) 04.08 просто бег по времени, вечером бежалось хорошо 05.08 вчера на тренировке бегать по лесу не пустили по этому просто бегали в зале: потом и поборолись
🔥2custom 53303538981105921041custom 54318403546576493141
Сегодня было тяжело 😩 Побегали, потом работа в зале: Проверили нашу вестибюлярку Планки Рывки Подтягивания Комплекс на ноги как в зале так и в тренажерке В понедельник едем на карьеры на тренировку, будет дроп🙂↕️ #мыустали
❤6custom 53303538981105921045🔥2
Вчера была хорошая тренировка: Бегали в зале 25мин и каждые 5мин смена направления Броски, наконец-то началась работа для борьбы И в конце по классике Тренажерка: Жим на ноги(просто делали 4 подхода вышли на 106кг, подтягивания и работа на широчайше мышцы спины я вышла на 70кг) Как то так прошла вчера тренировка #judo #тренировки
custom 53325723775680182673🔥2❤1
Сегодня с Варей круто потренировались. Устали, но двигаемся дальше 🏆 #брянск #тренировки
🔥5custom 54318403546576493143custom 53325723775680182671
Сегодня просто бег тк тренировку отменили 😭 Сначала пришла домой и думала что буду спать, но потом резко что от поменялось 🙂
❤7
Так вчера была немного грустная тренировка тк мы провожали нашу Полину( На самой тренировке сначала бегали, потом играли в забытую всеми игру пояски😎 ну а потом по классике пошли в тренажерку, но на этом мы не остановились: потом работали на пресс и на хват #нашпрайм #полининини(
❤5🔥2👍1🤯1
Showing the 8 most recent of 8 posts we hold for @puzikova479. 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Puzikova” (@puzikova479), 135 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/puzikova479.
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.