Channel
@rocket10agency
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,178subscribers
+5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001685052665 |
|---|---|
| Type | Channel |
| Username | @rocket10agency |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/rocket10agency |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 19:17 | 1,178 | +6 |
| 7 Aug 2026, 23:32 | 1,172 | no change |
| 7 Aug 2026, 20:28 | 1,172 | -1 |
| 7 Aug 2026, 17:17 | 1,173 | first reading |
15 posts held, back to 22 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 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 7 August 2026 |
|---|---|
| Posts held | 15 (22 July 2026 – 7 August 2026) |
| Views total | 4,732 |
| Reactions total | 214 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:32 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.
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.
214 reactions across 15 posts, in 9 distinct kinds. The most used accounts for 25.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5255891912660909538 | 54 | 25.2% | |
| custom 5255888008535637898 | 48 | 22.4% | |
| custom 5256089425321948761 | 26 | 12.1% | |
| custom 5256166399725827637 | 23 | 10.7% | |
| custom 5255710115285207339 | 19 | 8.88% | |
| custom 5255809938915098449 | 17 | 7.94% | |
| custom 5256211634321392232 | 12 | 5.61% | |
| custom 5255778147567174786 | 11 | 5.14% | |
| custom 5255999351267818681 | 4 | 1.87% |
Custom emoji. Every row above is a 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 areTelegram’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 15 of the 15 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 214reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 22 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.
Коллеги, рилсы ждать не будут! Закрываем ноуты и хороших выходных 🍹 #friday_humor
custom 52557781475671747865custom 52558919126609095384custom 52557101152852073393custom 52561663997258276371
Возвращаемся с правильным ответом к первой задачке рубрики «А/Б-тест». Выбор оказался непростым: в голосовании оба креатива шли почти вровень. С минимальным отрывом большинство выбрало вариант № 2, однако экспертный ответ — № 1. По опыту тестирования похожих баннеров именно такой креатив должен показать лучший результат. Почему первый вариант сработает лучше, объясняет в карточке Анна, Motion Design Lead Rocket10. …
custom 52557101152852073395custom 52558880085356378985custom 52558919126609095385custom 52559993512678186811custom 52561663997258276371
2026 год станет для мобильного маркетинга периодом адаптации Рынок привыкает к новым требованиям, медиаинфляции и более жёстким KPI. Рекламодатели внимательнее считают вложения и выбирают инструменты, которые позволяют быстро оценить результат. «Мы склонны придерживаться умеренно оптимистичного прогноза и ожидаем постепенного оживления рынка ближе к началу 2027 года», — отмечает коммерческий директор Rocket10 Тимур…
custom 52558880085356378986custom 52557101152852073394custom 52558919126609095384custom 52561663997258276372custom 52558099389150984491custom 52562116343213922321
Posted without readable text
custom 52558099389150984492custom 52558919126609095381custom 52560894253219487611
🆕 Новая рубрика: «А/Б-тест» Начинаем разбирать креативы не в теории, а на практике. Берём два варианта баннера с одним и тем же предложением — и просим вас угадать, какой сработает лучше. Сегодня на тест — два креатива с одинаковой скидкой до 50% на первый заказ, но с разной подачей: 🐚 №1 — крупный план продукта 🐚 №2 — акцент на разнообразии блюд и скорости доставки Как думаете, какой из них даст больше кликов и …
custom 52558880085356378985custom 52558919126609095384custom 52560894253219487614custom 52558099389150984491custom 52559993512678186811custom 52562116343213922321
Ювелирный маркетинг работает по своим правилам: украшение выбирают неделями, частые касания утомляют аудиторию, а скидка может размыть ценность бренда. Здесь важно не просто привести клиента в приложение, а увидеть весь его путь до покупки. В новом выпуске «Маркетологов в мобайле» поговорили со Станиславом Колосковым, директором по маркетингу «585 Золотой», о том, как выстраивать мобильный маркетинг в категории с дл…
custom 52557101152852073395custom 52560894253219487615custom 52561663997258276374custom 52558099389150984491custom 52562116343213922321
Whispers of the East — как это было В начале июля мы вместе с Mi Ads собрали клиентов и партнёров, чтобы совместить полезные инсайты с хорошим летним вечером в атмосфере восточной эстетики. Доклады и живые обсуждения, игра в го, чайная церемония, мастер-классы, приятный нетворкинг — словом, всё то, за что мы любим такие встречи ❤️ Делимся с вами видео, чтобы ещё раз окунуться в эту атмосферу. И спасибо за вечер, …
custom 52561663997258276376custom 52558919126609095385custom 52562116343213922325custom 52558880085356378982
Video message, posted without a caption
custom 52558919126609095384custom 52557781475671747862custom 52558099389150984492custom 52558880085356378981
Можно ли считать высокий MAU успехом приложения? В ювелирке — не всегда. Уже на следующей неделе в «Маркетологах в мобайле» — интервью со Станиславом Колосковым, директором по маркетингу «585 Золотой». Поговорили о том, почему нельзя оценивать все каналы по последнему клику, как приложение помогает видеть путь клиента из онлайна в магазин и почему скидки могут дорого стоить бренду. Также обсудили статичные креативы…
custom 52558919126609095382custom 52560894253219487612
Video message, posted without a caption
custom 52558880085356378989custom 52558919126609095386custom 52560894253219487614custom 52557781475671747862custom 52561663997258276372custom 52562116343213922321
Summer Digital Fest уже совсем скоро 🌞 30 и 31 июля руководитель группы по развитию бизнеса Rocket10 Диана Фарсян будет ждать всех, кто любит обсуждать рекламу не только со сцены, но и в кулуарах. Если тоже планируете заглянуть на конференцию от IZMENI SOZNANIE и на Digital Elka — обязательно ловите Диану. Хорошие знакомства не бывают случайными 🫶🫶 #events
custom 52558880085356378983custom 52557101152852073392custom 52560894253219487612custom 52558919126609095381custom 52561663997258276371
При запуске кампаний многие медиабайеры в первую очередь смотрят на привычные верхнеуровневые метрики — например, CTR. Если креатив собирает хорошие клики, кажется, что алгоритм сам начнёт масштабировать показы. Однако в Unity всё работает немного иначе. Помимо классических метрик платформа уделяет большое внимание IPM (Installs per Mille) — количеству установок на 1000 показов. Именно этот показатель помогает алгор…
custom 52558919126609095383custom 52558880085356378982custom 52560894253219487612custom 52559993512678186811custom 52561663997258276371custom 52562116343213922321
Showing the 12 most recent of 15 posts we hold for @rocket10agency. 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 — 105,248 of 1,183,361entries 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.
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 2 registered channels — 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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Rocket10 — AdTech Агентство Мобильного Маркетинга” (@rocket10agency), 1,178 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/rocket10agency.
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.