5 measurements spanning 7 days, net -62. 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 8,052–8,132 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Aug 2026, 19:44
8,061
-26
11 Aug 2026, 02:56
8,087
-31
8 Aug 2026, 08:51
8,118
-5
7 Aug 2026, 14:01
8,123
no change
7 Aug 2026, 13:57
8,123
first reading
Engagement
20 posts held, back to 7 June 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 10 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
12.4%
avg views ÷ 8,061 subscribers
Avg views / post
997
12 posts measured
Reaction rate
2.21%
reactions ÷ views · ER floor
Posts in window
12
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 10 August 2026
Posts held
20 (7 June 2026 – 10 August 2026)
Views total
11,964
Reactions total
265
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 16: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.
Reaction mix
403 reactions across 20 posts, in 13 distinct kinds. The most used accounts for 28.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
114
28.3%
👍
80
19.9%
❤🔥
56
13.9%
🫡
52
12.9%
👀
27
6.70%
😢
26
6.45%
🎉
16
3.97%
🔥
13
3.23%
💔
7
1.74%
🤬
5
1.24%
🤯
4
0.993%
💩
2
0.496%
🤔
1
0.248%
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 20 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 403reactions 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 June 2026 to 10 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.
🏆 Результаты второго дня плей-офф стадии MSC 2026:
🇲🇾 Team Vamos 🎮🎮 💥 Team Spirit
🇹🇷 Aurora Gaming 🎮🎮 🇮🇩 ONIC
🗓 Расписание на 31.07 (матчи bo5):
13:00 — 🇵🇭 Team Falcons PH vs 🇲🇲 Yangon Galacticos
15:30 — 💥 Team Spirit vs 🇮🇩 ONIC
🔺 Ссылки на трансляцию:
▶️ Twitch
🔹 YouTube
🟧 Syberia | Турниры и новости MLBB
🏆 Результаты первого дня плей-офф стадии MSC 2026:
🇲🇲 Yangon Galacticos 🎮🎮 🇰🇭 PRO Esports
🇮🇩 Team Vitality 🎮🎮 🇵🇭 Team Falcons PH
🗓 Расписание на 30.07 (матчи bo5):
13:00 — 🇲🇾 Team Vamos vs 💥 Team Spirit
15:30 — 🇹🇷 Aurora Gaming vs 🇮🇩 ONIC
🔺 Ссылки на трансляцию:
▶️ Twitch
🔹 YouTube
🟧 Syberia | Турниры и новости MLBB
🏆 Результаты финального дня группового этапа MSC 2026:
💥 Team Spirit 🎮🎮 🇨🇳 Guangzhou Gaming
🇰🇭 PRO Esports 🎮🎮 🇵🇪 Entity7
🇮🇩 ONIC 🎮🎮 🇲🇾 Selangor Red Giants
🇵🇭 Team Falcons PH 🎮🎮 🇸🇦 Team Falcons MENA
🗓 Плей-офф начинается 29.07, матчи bo5:
🇲🇾 Team Vamos vs 💥 Team Spirit
🇲🇲 Yangon Galacticos vs 🇰🇭 PRO Esports
🇮🇩 Team Vitality vs 🇵🇭 Team Falcons PH
🇹🇷 Aurora Gaming vs 🇮🇩 ONIC
🟧 Syberia | Турниры и новости MLBB
🏆 Результаты четвертого дня группового этапа MSC 2026:
🇪🇬 Geekay Esports 🎮🎮 🇲🇾 Selangor Red Giants
🇲🇲 Yangon Galacticos 🎮🎮 🇰🇭 PRO Esports
🇮🇩 ONIC 🎮🎮 🇹🇷 Aurora Gaming
🇵🇪 Entity7 🎮🎮 🇵🇭 Team Liquid PH
🗓 Расписание на 26.07 (матчи bo3):
12:00 — 💥 Team Spirit vs 🇨🇳 Guangzhou Gaming
13:30 — 🇰🇭 PRO Esports vs 🇵🇪 Entity7
15:00 — 🇮🇩 ONIC vs 🇲🇾 Selangor Red Giants
16:30 — 🇵🇭 Team Falcons PH vs 🇸🇦 Team Falcons MENA
🔺 Ссылки н…
🏆 Результаты третьего дня группового этапа MSC 2026:
🇮🇳 True Rippers 🎮🎮 🇨🇳 Guangzhou Gaming
🇲🇾 Team Vamos 🎮🎮 💥 Team Spirit
🇮🇩 Team Vitality 🎮🎮 🇵🇭 Team Falcons PH
🇸🇦 Team Falcons MENA 🎮🎮 🇸🇬 IGNITE Gaming
🗓 Расписание на 25.07 (группа B, матчи bo3):
12:00 — 🇪🇬 Geekay Esports vs 🇲🇾 Selangor Red Giants
13:30 — 🇲🇲 Yangon Galacticos vs 🇰🇭 PRO Esports
15:00 — 🇮🇩 ONIC vs 🇹🇷 Aurora Gaming
16:30 — 🇵🇪 Entity7 vs 🇵🇭 Team Liquid…
🏆 Результаты второго дня группового этапа MSC 2026:
🇲🇾 Selangor Red Giants 🎮🎮 🇰🇭 PRO Esports
🇵🇭 Team Liquid PH 🎮🎮 🇹🇷 Aurora Gaming
🇮🇩 ONIC 🎮🎮 🇵🇪Entity7
🇲🇲 Yangon Galacticos 🎮🎮 🇪🇬 Geekay Esports
🗓 Расписание на 24.07 (группа А, матчи bo3):
12:00 — 🇮🇳 True Rippers vs 🇨🇳 Guangzhou Gaming
13:30 — 🇲🇾 Team Vamos vs 💥 Team Spirit
15:00 — 🇮🇩 Team Vitality vs 🇵🇭 Team Falcons PH
16:30 — 🇸🇦 Team Falcons MENA vs 🇸🇬 IGNITE Gamin…
🏆 Результаты первого дня группового этапа MSC 2026:
🇲🇾 Team Vamos 🎮🎮 🇸🇦 Team Falcons MENA
🇵🇭 Team Falcons PH 🎮🎮 🇨🇳 Guangzhou Gaming
🇮🇩 Team Vitality 🎮🎮 🇮🇳True Rippers
💥 Team Spirit 🎮🎮 🇸🇬 IGNITE Gaming
🗓 Расписание на 23.07 (группа B, матчи bo3):
12:00 — 🇲🇾 Selangor Red Giants vs 🇰🇭 PRO Esports
13:30 — 🇵🇭 Team Liquid PH vs 🇹🇷 Aurora Gaming
15:00 — 🇮🇩 ONIC vs 🇵🇪Entity7
16:30 — 🇲🇲 Yangon Galacticos vs 🇪🇬 Geekay E…
💥 CyberHero представили новый состав — под тэг организации перешли игроки ex-FORZE:
⚔️ Maniak — exp
🌲 Repa — jungle
🧙♀️ Reaper — mid
🥇 Avilio — gold
🎭 ShowMe — roam
🎮 Dolsha — аналитик
🎮 Zefirka — менеджер
🟧 Syberia | Турниры и новости MLBB
👍7👀5🔥2❤🔥1
Showing the 12 most recent of 20 posts we hold for @syberia_mlbb. 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.
Mentions
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Киберспорт | Mobile Legends: Bang Bang @mlbbesports · 308,003 Telegram ranks this channel #27 of 79 here — alongside 78 others — read 10 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“Syberia Gaming | MLBB” (@syberia_mlbb), 8,061 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/syberia_mlbb.
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.