Channel
@imkopilka
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
153subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001286216520 |
|---|---|
| Type | Channel |
| Username | @imkopilka |
| Description | Здесь автоматически публикуются ссылки на заинтересовавшие меня материалы. |
| Created | Between 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/imkopilka |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 19:16 | 153 | no change |
| 7 Aug 2026, 19:44 | 153 | first reading |
20 posts held, back to 8 March 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 July 2026. An engagement rate over an empty window would be a number about nothing.
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 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.
45 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 64.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 29 | 64.4% | |
| 👍 | 14 | 31.1% | |
| 🤔 | 2 | 4.44% |
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 20 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 45reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 8 March 2024 to 7 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.
Привет. Я опубликовал на LinkedIn пост о поиске работы и был бы признателен вам за его поддержку: комментарий, репост или хотя бы лайк. Первый час самый важный, надеюсь у вас найдётся минутка как можно скорее 🙏
Для этого выпуска мы позвали Костю Найчукова — маркетолога с большим опытом в SaaS и B2B, который отвечал за коммуникацию и контент в 3Commas. Мы хотели понять, зачем B2B-компании вообще нужен контент, если его нельзя нормально посчитать в деньгах, почему LinkedIn лучше работает от лица людей, а не компаний, как говорить с американским рынком и где брать доверие, если ты для клиента пока просто «какие-то ребята из ин…
🔥2
Как я делаю чтобы курсор не галлюцинировал и не писал ерунду (видео, 3м)
https://ahrefs.com/blog/my-complete-ai-content-process-for-ahrefs/
👍1
Привет. Я опубликовал на LinkedIn пост о поиске работы и был бы признателен вам за его поддержку: https://www.linkedin.com/posts/knaychukov_im-looking-for-a-new-role-in-adtechmartech-activity-7335636414094585859-IeAj?utm_source=share&utm_medium=member_desktop&rcm=ACoAABb5IjoB0yMqG7DSmmskLchXK5Wv0AjnFVc
Закончил работу в Elly Analytics. Это был насыщенный период. Много вызовов и быстрых разворотов, что прокачало меня и сделало сильнее во многих областях. Спасибо команде — особенно тем, кто помогал, доверял и был рядом. Сейчас хочу немного выдохнуть и прийти в себя. Через несколько недель я снова буду в строю — и открыт к предложениям. Если вы ищете человека, который хорошо понимает рекламу, маркетинг, перформанс,…
👍6🤔2
В последнее время интернет-маркетологи все чаще стали сталкиваться с проблемой отслеживания данных, что, в свою очередь, негативно сказывается на результатах рекламных кампаний 🔽 Из-за отказа большинства браузеров от сторонних файлов cookie (third-party), их блокировки, ограничения срока жизни основных файлов cookie (first-party), а также из-за использования пользователями блокировщиков рекламы, режима "Инкогнито", …
🔥3
Зовите в ваши подкасты рассказать про Elly, сквозную аналитику и мою работу! 😁
«Это внезапный удар по знакомой жопе» В гостях Костя Найчуков, создатель полезного и продающего контента в Elly Analytics. Костя больше 8 лет проработал евангелистом eLama (продана Яндексу). Сейчас в Elly Analytics отвечает за что и как компания рассказывает о себе рынку США, повышая доверие к бренду. У Кости больше 10 лет опыта в создании экспертного контента о перформанс-маркетинге и аналитике. Мы поговорили: → …
🔥4👍2
«Почему в компаниях делают аналитику неэффективно» | Илья Красинский 🔥 Андрон Алексанян https://www.youtube.com/watch?v=OkZ4WFAQwJc
🔥3
Build your AI Workforce https://ift.tt/JvWZt1F
AI Search Engine for Research https://consensus.app/
Showing the 12 most recent of 20 posts we hold for @imkopilka. 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.
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.
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.
“Копилка Найчукова” (@imkopilka), 153 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/imkopilka.
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.