Telegram RegisterThe public register of Telegram

Channel

Maru Entertainment | MLBB

@maru_mlbb

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry

3,052subscribers

-10 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001731979077
TypeChannel
Username@maru_mlbb
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/maru_mlbb

Growth

3,0523,0623,0577 August 2026 — 3,062 subscribers7 August 2026 — 3,062 subscribers8 August 2026 — 3,059 subscribers11 August 2026 — 3,052 subscribers7 August 202611 August 2026
4 measurements spanning 4 days, net -10. 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 3,051–3,064 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 15:533,052-7
8 Aug 2026, 08:313,059-3
7 Aug 2026, 13:313,062no change
7 Aug 2026, 12:393,062first reading

Engagement

22 posts held, back to 31 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
111.2%
avg views ÷ 3,052 subscribers
Avg views / post
3,390
22 posts measured
Reaction rate
2.54%
reactions ÷ views · ER floor
Posts in window
22
of 22 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 7 August 2026
Posts held22 (31 July 20267 August 2026)
Views total74,673
Reactions total1,895
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 00:00 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

Video runtime
58s
Average length
29s

Measured directly from 2 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.

Reaction mix

1,895 reactions across 22 posts, in 15 distinct kinds. The most used accounts for 35.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
67435.6%
custom 545438695298174803533917.9%
🔥25213.3%
😁1638.60%
😭1186.23%
🥰995.22%
🤯683.59%
🏆623.27%
🤣452.37%
😢251.32%
🤔180.95%
🐳160.844%
😐70.369%
🤮70.369%
👻20.106%

Custom emoji. One 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 count beside it isTelegram’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 22 of the 22 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 1,895reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

Recent posts

7 Aug 2026, 19:08 UTC673 views15 reactionsread 8 August 2026
Video

🏆 редакция reporter.kg взяли мини-интервью у Пагу из Авроры 🐹 (Спросите некст раз за сколько турецких лир мне сигну сделают, я фанат 🤩)

custom 545438695298174803511🐳4

7 Aug 2026, 14:32 UTC≈1,010 views31 reactionsread 8 August 2026

Ля какой же матч ахуенный был гг аврора 🤤🤤

23custom 54543869529817480355🔥3

6 Aug 2026, 11:37 UTC≈1,420 views42 reactionsread 8 August 2026

А эм 🤔

😢25🤯8custom 54543869529817480357😐2

5 Aug 2026, 14:34 UTC≈1,600 views61 reactionsread 8 August 2026
Photo

🤤🏆

custom 545438695298174803539🔥13🥰53🤮1

4 Aug 2026, 09:42 UTC≈2,200 views41 reactionsread 8 August 2026

Как же хорош ерорр на фанни 🥲

custom 54543869529817480352711👻2🔥1

4 Aug 2026, 07:07 UTC≈2,250 views76 reactionsread 8 August 2026
Photo

Убирайте пиво в холодильник, сегодня с фальконами не деремся

custom 545438695298174803547🤔18🐳101

3 Aug 2026, 16:17 UTC≈2,150 views84 reactionsread 8 August 2026
Photo

Ааа...

🤯6012custom 54543869529817480357😐5

2 Aug 2026, 07:52 UTC≈2,510 views48 reactionsread 8 August 2026

Extremely спал вчера видос сегодня https://youtu.be/gbpWd38e0qg?si=cAW4rzkAbrSk-xGV

custom 54543869529817480352816🔥4

1 Aug 2026, 16:35 UTC≈2,670 views145 reactionsread 8 August 2026
Photo

А что за компашка собралась?

😁89🤣4511

1 Aug 2026, 16:10 UTC≈20,600 views202 reactionsread 8 August 2026
Photo

Саво в Париже скачать обои

161🥰31🔥9🤮1

1 Aug 2026, 16:05 UTC≈3,250 views176 reactionsread 8 August 2026
Photo

Ваш face когда шли 8 лет и finally win

125😁42🔥9

1 Aug 2026, 15:58 UTC≈3,070 views139 reactionsread 8 August 2026
Photo

Photo, posted without a caption

95🥰29🔥10😭5

Showing the 12 most recent of 22 posts we hold for @maru_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.

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 · 304,007
Telegram ranks this channel #9 of 79 here — alongside 78 others — read 10 August 2026
Mobile Legends: Bang Bang
@mlbbcis · 635,997
Telegram ranks this channel #28 of 84 here — alongside 83 others — read 10 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists 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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“Maru Entertainment | MLBB” (@maru_mlbb), 3,052 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/maru_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.