Channel
@kukusikKolet
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
412subscribers
-2 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001819626609 |
|---|---|
| Type | Channel |
| Username | @kukusikKolet |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/kukusikKolet |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 20:01 | 412 | -1 |
| 2 Sept 2026, 12:34 | 413 | +3 |
| 19 Aug 2026, 01:07 | 410 | -4 |
| 10 Aug 2026, 09:45 | 414 | no change |
| 10 Aug 2026, 09:31 | 414 | first reading |
5 posts held, back to 28 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 5 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
65 reactions across 5 posts, in 12 distinct kinds. The most used accounts for 20.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💘 | 13 | 20.0% | |
| ❤ | 9 | 13.8% | |
| custom 5348307660271788404 | 8 | 12.3% | |
| custom 5467743218940529803 | 8 | 12.3% | |
| custom 5470076494283818173 | 8 | 12.3% | |
| custom 5456145415671924632 | 4 | 6.15% | |
| custom 5465252142203820036 | 4 | 6.15% | |
| custom 5429409776830283609 | 3 | 4.62% | |
| custom 5465202565396318938 | 3 | 4.62% | |
| custom 5190403307893456939 | 2 | 3.08% | |
| custom 5470139479979215451 | 2 | 3.08% | |
| custom 5190863200106608096 | 1 | 1.54% |
Custom emoji. 10 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 5 of the 5 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 65 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 28 July 2026 to 9 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.
#такойвоттюнинг Сегодня набила циферки🤩🤩 Референс взяли с пинтерест🤩 #заживашки Крестик, набивали в августе 2025 год🤩 Контакты мастера:Контакты мастера: Тг: @Kukusiikkolet Тт: http://tiktok.com/@vika.salo Вк:https://vk.ru/vikasalol
custom 54294097768302836093💘2custom 51904033078934569392custom 54701394799792154512custom 51908632001066080961custom 53483076602717884041custom 54652521422038200361
#такойвоттюнинг ⭐️ ⭐️ ⭐️⭐️ ⭐️ ⭐️⭐️ Продолжаем забиваться. Вотс наш черни проектик, осталось не так уж и много хпхпп Отрисовала эскизик и начали забивать ⭐️⭐️⭐️⭐️ Черним жестк, послушали музыку и проболтали. На сегодня мои силы всё 💗💗💗 💗💗💗 Контакты мастера: Тг: @Kukusiikkolet Тт: http://tiktok.com/@vika.salo Вк:https://vk.ru/vikasalol
❤5custom 53483076602717884045custom 54652025653963189383💘1
#такойвоттюнинг Вчера жестко вайбила🪽 Две татушки за один день❤️ Одна по сертификату (оригинальный дизайн на подарок) Не знали приблизительно чего хотим, выбирали уже на месте⭐️ Пили чай, разговаривали. Отрисовывали эскизик, добавляли теней, цвет🤩 Уехали все уставшие, но с татушками🙈 #заживашки (мечи, подкорректировали один моментик) 🎀🎀🎀🎀 Контакты мастера: Тг: @Kukusiikkolet Тт: http://tiktok.com/@vika.salo Вк:htt…
custom 54677432189405298036custom 54700764942838181736💘3custom 54652521422038200363
Уже завтра выложу две крутые работки. Сегодня был очень продуктивный и сложный день🌟🤩
💘5❤4custom 54561454156719246323
#такойвоттюнинг 🤩🌟 Начали нежный-розовый проектик. Будем дорабатывать ещё. Попробовали новый розовый цвет. Вбивается отличн, будем ждать полного заживления 🤩 #заживашки Откорректировала татку, которую била год +-назад. Модель. °Добавила четкости, цвета, яркости, теней и блтков, прошлась по контуру 🤍 🥀🥀🤩🤩🤩 🥀🥀 🥀🥀 Контакты мастера: Тг: @Kukusiikkolet Тт: http://tiktok.com/@vika.salo Вк:https://vk.ru/vikasalol
💘2custom 53483076602717884042custom 54677432189405298032custom 54700764942838181732custom 54561454156719246321
Showing the 5 most recent of 5 posts we hold for @kukusikKolet. 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“KukusikKolet Ярославль” (@kukusikKolet), 412 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/kukusikKolet.
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.