Telegram RegisterThe public register of Telegram
Telegram profile photo for Mercurio Group

Channel

Mercurio Group

@mercurio_group

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

228subscribers

+14 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003735383826
TypeChannel
Username@mercurio_group
CreatedBetween 1 February 2026 and 6 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/mercurio_group

Growth

2142282216 August 2026 — 214 subscribers7 August 2026 — 214 subscribers14 August 2026 — 228 subscribers6 August 202614 August 2026
3 measurements spanning 8 days, net +14. 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 212–230 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 19:37228+14
7 Aug 2026, 03:32214no change
6 Aug 2026, 11:24214first reading

Engagement

10 posts held, back to 6 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
58.6%
avg views ÷ 228 subscribers
Avg views / post
134
2 posts measured
Reaction rate
11.2%
reactions ÷ views · ER floor
Posts in window
2
of 10 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 5 August 2026
Posts held10 (6 May 20265 August 2026)
Views total267
Reactions total30
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 03: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.

Reaction mix

282 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 29.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52515775664724725908429.8%
custom 52513230595954156958028.4%
custom 52513006398661305706924.5%
custom 52513926981951549004917.4%

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

Measured over the 10 most recent posts we hold, published 6 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.

Recent posts

5 Aug 2026, 14:57 UTC134 views19 reactionsread 7 August 2026

📢 Как строить баинг, когда рынок нестабилен Прямо сейчас наш Head of Buying участвует в Voice Chat от INSIDE. Вместе с представителями других команд обсуждаем, как выстраивать работу баинга, проходить кризисы и расти. ⚡️ Подключайтесь к эфиру в канале — и задавайте вопросы спикерам в прямом эфире. Всем спасибо за войс. Позже опубликуем запись 🥳

custom 525157756647247259010custom 52513926981951549005custom 52513230595954156954

5 Aug 2026, 14:57 UTC133 views11 reactionsread 7 August 2026

📢

custom 52513230595954156955custom 52513926981951549003custom 52513006398661305702custom 52515775664724725901

16 Jul 2026, 10:29 UTC722 views30 reactionsread 7 August 2026
Photo

🦋 Как устроена аналитика в Mercurio Метрики в баинге знают все. Никакого секретного набора цифр не существует — вопрос в том, за сколько ты до них добираешься, сколько считаешь руками и видишь ли всю картину или пару удобных срезов. В карточках — база нашей сквозной аналитики: какие срезы крутим, что видим в воронке, как докапываемся до причины и почему регулярно перечитываем старые тесты. 📢 Сохрани — пригодится,

custom 525139269819515490013custom 52515775664724725909custom 52513006398661305706custom 52513230595954156952

30 Jun 2026, 11:29 UTC906 views35 reactionsread 7 August 2026
Forwarded from @g_gate_mediaPhoto

🚀 Почему рынку пора переходить на KPI-driven подход: опыт Mercurio Group Как перейти от интуитивных решений к системному управлению результатами? KPI-driven подход помогает выстраивать процессы вокруг данных: оценивать эффективность, находить точки роста и масштабировать рабочие стратегии. Вместе с Alexandr Heizinga из Mercurio Group разобрались, как прицельная работа с цифрами меняет взгляд на бизнес и его эффект

custom 525157756647247259014custom 525130063986613057010custom 52513230595954156958custom 52513926981951549003

19 Jun 2026, 16:09 UTC985 views36 reactionsread 7 August 2026
Photo

📢 Вырастить нельзя купить. Весь вопрос — где поставить запятую Хантить готового или растить своего — спор древний, как сам рынок. Перекупить дорого. Вырастить долго. И в 2026-м у этого спора так и не появилось однозначного ответа. Цена выбора видна на конкретных примерах. Баер без единого сильного кейса в резюме за пару месяцев выходит на стабильный профит. А тот, кто приходит с кейсами на сотни тысяч, месяцами не

custom 525130063986613057014custom 525132305959541569511custom 52515775664724725908custom 52513926981951549003

4 Jun 2026, 16:23 UTC≈1,110 views39 reactionsread 7 August 2026
Photo

📢 Вакансия Media Buyer под FB / TT Ищем людей, которые умеют работать под нагрузкой, держать темп тестов и отвечать за результат не словами, а цифрами. С нас — инфраструктура, командная работа и понятная система: фарм, дизайн, iOS / Android dev, PWA, автоаналитика и постоянная поддержка от тимлидов. Для специалистов — регулярные внутренние школы, чтобы прокачивать своё направление. Для тимлидов и тех, кто хочет в

custom 525132305959541569518custom 525130063986613057010custom 52513926981951549009custom 52515775664724725902

20 May 2026, 13:07 UTC≈1,390 views35 reactionsread 7 August 2026
Photo

📢 Mercurio Group летит на MAC 2026 Активно растём и масштабируемся, поэтому всегда открыты к сильным знакомствам, партнёрствам и обмену экспертизой. Ценим не поверхностный нетворкинг, а сильные связи и диалог, из которого обе стороны могут вынести реальную ценность. ⚡️ Если будете на MAC, в Ереване — пишите. Обсудим рынок, трафик, подходы и то, куда стоит двигаться в индустрии сейчас. 🥳

custom 525132305959541569513custom 525130063986613057010custom 52515775664724725908custom 52513926981951549004

7 May 2026, 11:03 UTC989 views9 reactionsread 7 August 2026

📢

custom 52513926981951549007custom 52513230595954156951custom 52515775664724725901

7 May 2026, 11:03 UTC≈1,260 views36 reactionsread 7 August 2026
Forwarded from @limitedclubcpaPhoto

Гемблинг кейс: $185 700 за январь в Tier-1 Зайти в новое GEO — это половина задачи. Вторая — быстро находить рост и не терять темп при масштабировании. Mercurio Group поделились кейсом по работе с Tier-1 GEO на приватном оффере от The Limited Club. Внутри: 🟩как заходили в новое GEO и быстро масштабировались в нем; 🟩как prepay позволил не стопать залив в точках роста; 🟩как оперативная передача аналитики позволяла

custom 525157756647247259018custom 52513006398661305709custom 52513230595954156959

6 May 2026, 13:24 UTC919 views32 reactionsread 7 August 2026
Forwarded from @hardcoreaffiliateclubPhoto

Знаете, как тяжело искать героев нашей постоянной рубрики «С детства за трафик»? Про молодых самородков, которые начали выносить аукционы раньше, чем получили паспорт? В этот раз мы поговорили с Фёдором — MediaBuyer Mercurio 🔥 🔴 в сфере трафика с 14 лет, активно работает с 15 🔴 начинал со $120 тестового бюджета от старшего брата 🔴 сейчас заливает Tier-1 (PWA и iOS), делает рекордные профиты в $55,6k за месяц с ROI

custom 525157756647247259013custom 52513230595954156959custom 52513006398661305708custom 52513926981951549002

Showing the 10 most recent of 10 posts we hold for @mercurio_group. 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 — 371,032 of 1,481,217entries 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 3 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.

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.

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

“Mercurio Group” (@mercurio_group), 228 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/mercurio_group.

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.