Telegram RegisterThe public register of Telegram

Channel

Беляев бежит

@belyaevrun

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

142subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002860250270
TypeChannel
Username@belyaevrun
DescriptionЯ, Беляев Сергей, Исполнительный директор Datainsight, партнер и ex. CEO группы компаний Webit. Работал COO РА МедиаНация, был вице-президентом IAB Russian. Пишу про то, как сочетать занятие триатлоном, управление бизнесом и семью
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/belyaevrun

Growth

1427 Aug 2026, 16:35 — 142 subscribers8 Aug 2026, 21:47 — 142 subscribers7 Aug 2026, 16:358 Aug 2026, 21:47
2 measurements spanning 1 day. 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 141–143 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 21:47142no change
7 Aug 2026, 16:35142first reading

Engagement

18 posts held, back to 18 May 2026the 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 · 30 days
38.7%
avg views ÷ 142 subscribers
Avg views / post
55.0
2 posts measured
Reaction rate
5.45%
reactions ÷ views · ER floor
Posts in window
2
of 18 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
WindowRolling 30 days · latest post in window 20 July 2026
Posts held18 (18 May 202620 July 2026)
Views total110
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 21:47 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.

What this channel posts

Photos
70
Links
80

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.

Reaction mix

54 reactions across 14 posts, in 6 distinct kinds. The most used accounts for 38.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2138.9%
👍1731.5%
1222.2%
🥰23.70%
😱11.85%
🙏11.85%

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 14 of the 18 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 54reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 18 May 2026 to 20 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.

Recent posts

20 Jul 2026, 06:56 UTC55 views1 reactionsread 8 August 2026

Продолжаю наращивать экспертизу в консультациях

👍1

20 Jul 2026, 06:56 UTC55 views5 reactionsread 8 August 2026
Photo

Отзыв Дмитрия Бабича, основателя компании ok-digital.pro

4🔥1

11 Jul 2026, 06:21 UTC65 viewsread 8 August 2026

Друзья, на следующей неделе выступаю на конференции fashiondive. Мы в Data Insight подготовили два отчета по рынку Fashion, Масмаркет и Premium, основными цифрами 2025 и трендами 2026 года из этих отчетов я и поделюсь на конференции Кто работает с этой отраслью, приходите

11 Jul 2026, 06:21 UTC83 views3 reactionsread 8 August 2026
Forwarded from @DataInsightPhoto

16 июля в Москве на конференции Fashion Dive выступит исполнительный директор Data Insight Сергей Беляев. Он представит аналитику онлайн-продаж модного рынка и раскроет: – Результаты 2025 года: размер рынка, доля онлайн-продаж, динамика – Ключевые проблемы рынка и что влияет на деньги и устойчивость компаний? – Тренды и прогнозы на 2026, а также стратегии развития на 2026-2027 годы Также в рамках сессии аналитику п

1👍1🔥1

2 Jul 2026, 06:12 UTC124 views7 reactionsread 8 August 2026
Photo

Как же быстро летит время. Ещё вчера я вернулся под впечатлениями из Магнитогорска, а уже пора готовиться к новой поездке на EcomWeekend в Сочи 13-16 августа У меня это уже 15-я поездка, я гордо ношу звание самого частого участника конференции При этом я очень практичный и каждый раз думаю: зачем мне ехать, зачем тратить время и деньги? Безусловно, основная ценность поездки — это комьюнити. Это интересные люди, ко

🔥4🥰21

26 Jun 2026, 06:30 UTC100 views7 reactionsread 8 August 2026
Photo

144 года стройки — хороший пример долгосрочного бизнес-планирования Рынок меняется. Новые технологии, внешние ограничения, внутренние кризисы. То, что работало в прошлом квартале, уже не дает результат. Постоянная адаптация выматывает В такие моменты полезно посмотреть на проекты, которые не подчиняются квартальной отчетности Один из таких проектов — Саграда Фамилия. Это одно из моих любимых мест в Барселоне. Я бы

🔥6😱1

24 Jun 2026, 10:31 UTC648 views5 reactionsread 8 August 2026

Новая карта рынка. И она больше, чем просто карта Мы, Data Insight, — выпустили новую версию «Экосистему электронной торговли России 2026» Это ежегодный продукт, который показывает, кто есть кто на рынке услуг для eCommerce. И в этом году он стал ещё больше и детальнее Что нового: — На карте теперь больше 1500 логотипов. Более тысячи уникальных игроков, и около 50 из них — новички — Самый активный рост — в логист

👍3🔥2

22 Jun 2026, 15:25 UTC100 views3 reactionsread 8 August 2026
Photo

Здесь рыбы нет… 🎣 На выходных посетил нестандартное мероприятие — Недиджитал рыбалку, которую организовала 365 Media Group совместно с Partners Club AGIMA Это очень прикольный формат: представители агентского бизнеса выезжают на природу, на берег водохранилища и совмещают активный отдых (рыбалка) с обсуждением насущных проблем, обменом опытом и тому подобным Меня второй год приглашают на это мероприятие в качестве

👍3

15 Jun 2026, 07:47 UTC108 views2 reactionsread 8 August 2026
Forwarded from @DataInsightPhoto

💡Агентства на распутье: закрываться или меняться Высокая ключевая ставка, рост налоговой нагрузки, медиаинфляция, сокращение маркетинговых бюджетов и развитие AI-инструментов одновременно меняют рынок маркетинговых услуг. В этих условиях агентства сталкиваются с падением маржинальности, более длинными циклами продаж, ростом дебиторской задолженности и всё более высокими требованиями клиентов к результату. Исполнит

👍1🔥1

9 Jun 2026, 06:03 UTC117 views1 reactionsread 8 August 2026

Снова на речке. Без галстуков, зато с удочкой 365 Media Group + Partners’ Club AGIMA второй год собирают представителей IT-агентств и digital-студий. Не ради отчетов и презентаций, а ради живого общения, утренних пробежек и честных разговоров у костра Кому сюда точно надо: — собственникам и CEO, которые устали от воды на конференциях — тем, кто хочет обсудить реальные проблемы отрасли с теми, кто в такой же лодке —

👍1

Showing the 12 most recent of 18 posts we hold for @belyaevrun. 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 — 287,168 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.

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Беляев бежит” (@belyaevrun), 142 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/belyaevrun.

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.