Telegram RegisterThe public register of Telegram
Telegram profile photo for MMRL App

Channel

MMRL App

@MMRLApp

On this record: Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

1,613subscribers

+44 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-1002284356437
TypeChannel
Username@MMRLApp
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/MMRLApp

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

1,5691,6131,5917 August 2026 — 1,569 subscribers8 August 2026 — 1,573 subscribers11 August 2026 — 1,583 subscribers15 August 2026 — 1,587 subscribers17 August 2026 — 1,595 subscribers20 August 2026 — 1,601 subscribers24 August 2026 — 1,597 subscribers27 August 2026 — 1,605 subscribers30 August 2026 — 1,613 subscribers7 August 202630 August 2026
9 measurements spanning 22 days, net +44. 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 1,562–1,620 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 00:031,613+8
27 Aug 2026, 08:351,605+8
24 Aug 2026, 03:351,597-4
20 Aug 2026, 15:161,601+6
17 Aug 2026, 20:331,595+8
15 Aug 2026, 02:371,587+4
11 Aug 2026, 11:061,583+10
8 Aug 2026, 20:151,573+4
7 Aug 2026, 22:161,569first reading

Engagement

19 posts held, back to 12 April 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
11.2%
avg views ÷ 1,613 subscribers
Avg views / post
180
1 post measured
Reaction rate
0.556%
reactions ÷ views · ER floor
Posts in window
1
of 19 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 4 August 2026
Posts held19 (12 April 20264 August 2026)
Views total180
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 22:16 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
46s
Average length
46s

Measured directly from 1 video 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

67 reactions across 17 posts, in 7 distinct kinds. The most used accounts for 53.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3653.7%
👍1522.4%
👌710.4%
🔥57.46%
🤣22.99%
11.49%
😱11.49%

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

Measured over the 19 most recent posts we hold, published 12 April 2026 to 4 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 19 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @MMRLApp. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 19 most recent posts we hold for this entry, published 12 April 2026 to 4 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

4 Aug 2026, 11:24 UTC180 views1 reactionsread 7 August 2026
Forwarded from @MMRLCIFile

JavaScript API has been added to create the WebUI Shortcut directly within the WebUI. The legacy API from the WX engine is included for compatibility. With this release, beta testing is commencing.

1

12 Jul 2026, 16:25 UTC752 views3 reactionsread 7 August 2026

Not finished yet https://docs.mmrl.dev/modules/MX_Engine.html

2🔥1

12 Jul 2026, 13:24 UTC711 views2 reactionsread 7 August 2026
Forwarded from @MMRLCIFile

Additions and Improvements: - Meta Modules will now be designated with an [M] prefix preceding their name. - Module card customization has been restored. - The shortcut button has been reinstated on the module card. - A theme selector has been added to the module configuration page. - The KowSU file API has been integrated into the MX Engine. - Handling for empty icons has been corrected. - DevTools will now attempt

1👍1

7 Jul 2026, 14:48 UTC778 viewsread 7 August 2026

Hello! What WebUI X features do you want? What bugs have you encountered?

4 Jul 2026, 22:07 UTC820 views3 reactionsread 7 August 2026
Forwarded from @MMRLCIFile

- Fixed an issue where user were unable to start WerbUI's - When opening the shortcut creation screen it uses now the defined title from the config.json This update introduces also a new way to interact with the files in non-root mode. You can now add it to Material Files or any other file manager app

3

4 Jul 2026, 19:09 UTC747 views2 reactionsread 7 August 2026
Forwarded from @MMRLCIFile

- Improved the DevTools by replacing them with the Chrome DevTools Protocol. - Removed the console interceptor as it is no longer needed. - A new "Sources" tab has been added to the DevTools, which lets you preview the sources requested by the WebUI. - Fixed an issue where users were unable to edit files in the file explorer. In future versions of the MX Engine, the option to use Eruda as the debugging console might

2

27 Jun 2026, 19:44 UTC779 views5 reactionsread 7 August 2026
Forwarded from @MMRLCIFile

- Added snippets to the DevTools - Added the ability to resize the DevTools - Added back the option to create a module shortcut (Gear icon on the module card > Create Shortcut) - Restored the App Theme page as it will now used for the app accent color and the WebUI theme Known issues: - Sometimes console entries are empty in the MX Engine With this release we're exposing the entire module specs to JavaScript. You c

🤣211😱1

27 Jun 2026, 12:19 UTC709 views3 reactionsread 7 August 2026
Forwarded from @MMRLCIFile

What's fixed: - Fixed that a wrong CSP have been used and the application icons have been blocked. The rule is now added by default. - Fixed a issue where new added path handler via Lua doesn't get added due to a anonymous class. - Fixed the text color of the console.log(...) when the console interceptor is active. - Fixed a issue where the package manager would use the "only launchable" option to load application, w

3

22 Jun 2026, 06:29 UTC849 views6 reactionsread 7 August 2026

The MMRL app is currently experiencing issues with the HiddenPackageManager class on Android 16-17. This due to the signature of the binder have been changed. A proper update is hopefully following these days. ✌️

👍6

21 Jun 2026, 16:32 UTC810 views7 reactionsread 7 August 2026
Forwarded from @MMRLCIFile

- Fixed broken path handler, used a wrong order - Added support for the KernelSU PackageManager API in the MX Engine. Known issues in this build: - Sometimes console entries are empty or to dark to read in the MX Engine Google Play builds are limited in the PackageManager API to only launchable apps. We're also update the https://www.npmjs.com/package/webuix package to support the new event system. No changes need

👍52

20 Jun 2026, 11:49 UTC806 views0 reactionsread 7 August 2026
Forwarded from @MMRLCIFile

- Refactored the config screen to the new design system - Extracted the module file explorer into a own activity which makes it much more easier to test and edit module files

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

“MMRL App” (@MMRLApp), 1,613 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/MMRLApp.

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.