4 measurements spanning 6 days, net +29. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 5,821–5,858 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 12:38
5,854
+6
9 Aug 2026, 14:13
5,848
+21
6 Aug 2026, 13:21
5,827
+2
6 Aug 2026, 03:36
5,825
first reading
Engagement
20 posts held, back to 7 May 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 9 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
41.9%
avg views ÷ 5,854 subscribers
Avg views / post
2,450
7 posts measured
Reaction rate
0.448%
reactions ÷ views · ER floor
Posts in window
7
of 20 held
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 5 August 2026
Posts held
20 (7 May 2026 – 5 August 2026)
Views total
17,180
Reactions total
77
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 03:48 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.
Reaction mix
369 reactions across 19 posts, in 13 distinct kinds. The most used accounts for 34.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
126
34.1%
👍
98
26.6%
🔥
86
23.3%
🤡
26
7.05%
🤔
6
1.63%
🤮
6
1.63%
👌
5
1.36%
😐
5
1.36%
❤🔥
4
1.08%
🤝
4
1.08%
🌭
1
0.271%
👎
1
0.271%
😁
1
0.271%
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 19 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 369reactions 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 7 May 2026 to 5 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.
Advertising
Ad load
5.00%
1 of 20 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
3,830
over 1 measured post
Median views · rest
3,340
over 19 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 20 most recent posts we hold, published 7 May 2026 to 5 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Самое лаконичное и элегантное описание стратегии скейлинга неожиданно нашел в подсказке дашборда AppLovin:
“If a campaign is performing at or above the desired outcome, gradually increase the budget on a daily basis until performance no longer meets your targets. Each increase should be meaningful; we recommend a minimum adjustment of the greater of $100 or 10% of the total budget.”
Лучше не скажешь.
Что запускать: картинки или видео?
Зависит от ниши. Обычно я прохожусь по конкурентам и смотрю, что запускают они - скорее всего, у меня будет такой же расклад.
На многих проектах картинки
1. Перформят лучше видео
Думаю это не потому, что картинки как формат сильнее, а скорее потому что я могу оттестить больше и быстрее чем видео.
2. Перформят лучше сделанных “вручную”.
Часто на проектах генерю креативы паралельно с…
АБ-тесты креативов в Metа
На стриме “META: запуск и scaling” было несколько вопросов про АБ-тестирование креативов. В Meta я креативы АБ-тестами не сравниваю. Почему так:
🧪 Что такое АБ-тест
Пользователей случайно делят на контрольную и тестовую группу, между группами отличается один элемент. Дальше проверяют нулевую гипотезу «разницы нет»: считают, на сколько варианты отличаются и какова вероятность получить такое …
СДВГ-кодинг
Я мало рассуждаю о вайб-кодинг в целом: ваша лента и без меня забита общими рассуждениями. Если не смотреть на сторонников и говорить только о критиках, я выделяю для себя две категории:
🧩 Категория 1: архитектура
Разработчик просит модель написать код. Модель пишет. Разработчик открывает результат, не узнаёт в нём свою архитектуру и пишет пост о том, что вайб-кодинг не работает.
🐞 Категория 2: баги
Код…
Как я работаю с нейросетями. Часть 3 из 4. Креативы
Каждый понедельник я заливаю все новые креативы по всем аккаунтам в тест. Раньше это значило:
• открыть папку
• вспомнить, что уже запускал
• вручную собрать кампанию в META.
• upload креативов
самый долгий этап, т к креативы иногда заливаются ужасно долго.
Сейчас этим занимается бот.
🤖 Что делает бот
Бот сканит папки креативов на Google Drive по каждому кабинету.…
Цена инсталла - не KPI
Кампании в Meta я оптимизирую либо на покупки, либо на триалы.
Оптимизация на инсталлы не работает, и на цену инстала при закупке я не смотрю.
Отступление: она важна например в Apple Search Ads. В Meta - нет
📈 Почему CPI растёт
Платящие пользователи стоят дороже, и цена инсталла растёт вместе с ними. Задача - покупать не дешёвый инсталл, а инсталл, у которого сходится ROAS.
Это в целом. Но е…
Как я работаю с нейросетями. Часть 2 из 4: предикты по понедельникам
Полное описание инфраструктуры в прошлом посте
Каждый понедельник утром все мои клиенты гарантированно получают предикт - предсказание будущего ROAS за прошлую неделю. Я трачу на это не больше 5 минут.
🎯 Зачем предикт
В любой момент времени мы можем оценить ROAS нулевого дня:
LTV (0 day) * Conversions #
———————————-
Spend
Но D0 ROAS почти ничего…
Напоминаю что стрим “META: запуск и scaling” состоится через час - в 18:00 (МСК).
От вас поступили интересные вопросы - будем их разбирать!
Также разберу вопросы которые вы зададите по ходу стрима.
Ссылка на стрим
Напоминаю что 1 июля (среда) состоится стрим “META: запуск и scaling”
Похожий разбор вопросов мы проводим в рамках моего курса.
Если у вас есть вопросы, которые вы хотите задать на стриме - можно заранее отправить их через форму вопросов. Присылайте свои любые вопросы и кейсы - я все их разберу.
Рассмотр вопросов анонимный - поэтому можно задавать вопросы о реальных кейсах.
Важно: осталось всего 17 мест из 100. У…
У друзей из Plurio.ai появилась вакансия, которую стоит посмотреть, даже если ты не ищешь работу: она классно показывает, как меняется роль перформанс-маркетолога с появлением AI. Делюсь.
Смотри, что агенты уже забирают на себя:
— раньше надо было самому часами разглядывать дэшборды → теперь Plurio делает глубокий анализ за минуты
— раньше надо было самому считать распределение бюджета в эксельках → теперь Plurio да…
1 июля состоится стрим “META: запуск и scaling”
Если у вас есть вопросы, которые вы хотите задать на стриме - можно заранее отправить их через форму вопросов.
Разберем запуск, оптимизацию и скейлинг рекламных кампаний в Meta.
• Стратегия
• Настройка
• Креативы
• Безопасность: аккаунты/баны
• Атрибуция и MMP
🗓1 июля 18:00 (МСК)
👉Форма регистрации
💡Задать вопрос
Как я работаю с нейросетями. Часть 1 из 4
Веду пять рекламных кабинетов клиентов. Предикты, креативы, ежедневные отчёты, решения по кампаниям - большую часть этой работы делает Claude Code.
Сам я 90% времени провожу в Телеграме - в нем я:
• получаю отчёты
• строю предикты / оцениваю перформанс
• запускаю кампании
• заливаю креативы в кабинет (сразу создаются кампании/адесеты)
• генерю новые креативы
• и брейнстормлю…
🔥24❤7👍1
Showing the 12 most recent of 20 posts we hold for @web2app_subscription. 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
Citation-graph rank — 94,315 of 1,160,990entries 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.
Forward network
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.
Mentions
Named by 7 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.
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.
Cite this entry
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 12 August 2026 — this
entry's latest reading, not the date you are reading this.
“Web2App: User Acquisition в iOS приложениях” (@web2app_subscription), 5,854 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/web2app_subscription.
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.