Channel
@kukalyakinnotes
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
371subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001186116805 |
|---|---|
| Type | Channel |
| Username | @kukalyakinnotes |
| Description | Привет, я Данил Снитко. Выучился на юриста. Играл в КВН. Работаю в рекламе. Воспитываю двух дочерей. Стараюсь писать. Иногда получается. Моя книжка — http://book.danilsnitko.ru/ Сайт моего агентства — https://dvaslova.com/ |
| Created | 7 January 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/kukalyakinnotes |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 20:33 | 371 | no change |
| 6 Aug 2026, 12:46 | 371 | first reading |
11 posts held, back to 14 April 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.
| Window | Rolling 30 days · latest post in window 29 July 2026 |
|---|---|
| Posts held | 11 (14 April 2026 – 29 July 2026) |
| Views total | 732 |
| Reactions total | 55 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 20:33 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 6 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.
142 reactions across 11 posts, in 9 distinct kinds. The most used accounts for 28.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 40 | 28.2% | |
| 🔥 | 39 | 27.5% | |
| ❤🔥 | 21 | 14.8% | |
| 😁 | 14 | 9.86% | |
| 👍 | 12 | 8.45% | |
| 🤝 | 9 | 6.34% | |
| 👏 | 3 | 2.11% | |
| 💩 | 3 | 2.11% | |
| 💊 | 1 | 0.704% |
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 11 of the 11 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 142reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 14 April 2026 to 29 July 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.
Извините, посты про детей один за другим... Это, конечно, повторится. Нет, не извините! Вообще, когда я канал заводил, я думал, что буду писать в основном про разумное, доброе, вечное. Это будут, как на Пасху, ВЕЛИКИЕ ПОСТЫ. Ну, может, и не Великие, но прям продуманные, я к ним буду долго готовиться, переписывать раз на 200 каждый, сомневаться, выхаживать текст в голове предварительно, каждый дней этак по 10, не мен…
🤝9❤3🔥2❤🔥1
Достал с антресолей настолку, которую я сам придумал и нарисовал в 1998 году. Я в нее ни с кем не играл до этого. И вот впервые сыграл с дочерью!
🔥13❤🔥5
Прихожу домой, картина: на диване бешено прыгают и орут старшая дочь с подругой под песню «Потому что я русская девчонка», младшая сидит рядом и хохочет. После этого прозвучало «Алиса, включи песню со звуками пердежа!». Алиса, что интересно, нашла и включила. Дети — это счастье.
👍9
Примерно году этак в 2002-м мой пьяный товарищ, стоя со мной на крыльце горной базы и задумчиво попивая шмурдилово из водки и гранатового сока из полторашки, произнес: — Эх, подняться бы щас на гору, да трахнуть бы там бабу... Я аж поперхнулся. — А что, — говорю, — зачем на гору-то? — Да просто так уже заебало! — чуть помолчав, с чувством выдал он и устремил свой взгляд далеко в вершины. Мы оба были девственник…
😁9❤🔥4
#коллеги_с_пятницей Вдохновение часто находится за пределами работы. Поэтому в нашей пятничной рубрике коллеги делятся тем, что заряжает их в жизни. Сегодня своими рекомендациями делится Данил Снитко — член жюри блока «Креатив», владелец и креативный директор агентства «Два слова». ➡️ Листайте карточки — возможно, найдете что-то и для себя. 💜 Голос индустрии в регионах 🟣 Мы в MAX
❤5👍3💩1
Мы вон что придумали и сняли. Очень долгая и кропотливая работа.
❤🔥1🔥1
Для внутренней и международной рекламы туризма в Алтайском крае мы придумали и сняли ролик «„Бы“ не надо, надо „А“!». Ролик является продолжением прошлой рекламной кампании «А — это Алтайский край!» Ролик на RuTube — https://rutube.ru/video/d02cf2610fbf2f06ee60b5bc8c58bf4a/?r=wd Авторы сценария — Данил Снитко и Евгений Егоров Режиссер, монтажёр — Кочетков Евгений Продюсер — Тушев Никита Линейный продюсер — Юсупова …
❤🔥9❤6👏2💩2🔥2
Вспомнил, что мне напоминает дизайн Ferrari Luce — пластиковый iPhone 5C! У меня, кстати, такой был. Только желтый. Прикольный он был. Айфон, в смысле. Феррари у меня другая была.
❤6😁5🔥4
Расчехлил свой iPod Shuffle. С 2012, кажется, года тут залита рандомная музыка из всей моей 2тб-фонотеки. И я буквально не узнаю ни одного трека, рандом вышел что надо. Решил так и оставить — буду двигаться на максимально рандомных вайбах, так даже прикольнее! Гениальное, конечно, устройство…
🔥12❤5💊1
Мы в нашем синдикате Conspiracy.Work провернули настоящую махину — взяли и возродили легендарный рекламный фестиваль «Идея!», который ждал своего часа аж 10 лет. Мы готовились к этому 8 месяцев, мы строили планы и писали сценарии, скрупулезно делали сайт, не спали ночами, собирали самых лучших и невероятных членов жюри и спикеров по всей стране и даже за ее пределами, готовили площадку, смеялись и плакали, ругали и…
❤12🔥3
Коллега Николай съездил туда, где делают призы для нашего фестиваля «На уровне идеи!» и остался ими весьма доволен. Сам фестиваль, напоминаю, пройдет в Новосибирске 22 и 23 апреля (да, два дня!), программа мощнейшая, спикеры шокирующие, нетворкинг окрыляющий, билет копеечный! А еще до 17 числа мы сдвинули дедлайн подачи работ, так что еще можно залететь со своими работами в первый фестиваль сезона! Сам поеду и вам…
❤3🔥2❤🔥1👏1
Showing the 11 most recent of 11 posts we hold for @kukalyakinnotes. 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 — 774,675 of 1,169,250entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“Кукалякин пишет” (@kukalyakinnotes), 371 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/kukalyakinnotes.
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.