MMY 2.2.5 recorded Get the file

MMY download: check the file against the record

Two files were measured on 10 November 2026. The button on this page serves the first one. Compare the file you received against the record before you install it.

Download MMY

The file this page serves

channel file, served when gz is set
filemmy.2rwkt.apk
bytes20,954,528
sha256b699d1480b19ec1fb28974c90df518bc7ff989e0900ec9fcc4beef7c353e6421
packagecom.mmyuionn.opp02
versionName2.2.5
versionCode225
minSdk24 (Android 7.0)
abiarm64-v8a only
engineCocos 3.8.2

Three checks settle whether you have this file, and they cost nothing beyond the download itself. The byte count comes first, because a file manager shows it without any extra tool. The version code comes second, because Android uses it rather than the version name when it decides whether a file may replace an installed copy. The hash comes last, because it is the only check that covers every byte and the only one that survives a renamed file.

The three checks, in order

  1. Size. The channel file is exactly 20,954,528 bytes, which reads as 19.98 MB in a file manager that rounds to two decimals. A download that finishes on a round number was cut off. How to read the byte count on each system.
  2. Version code. The label is 2.2.5 and the code is 225. Android compares the code, so a file with a higher label and an equal or lower code will not install over this one. Why the label and the code disagree.
  3. Hash. SHA-256 b699d1480b19ec1fb28974c90df518bc7ff989e0900ec9fcc4beef7c353e6421. A match means the bytes are the measured bytes. It does not describe what the app does once it runs. How to compute it.

When a mismatch matters

A shorter file is a failed download, and re-downloading fixes it. A file of any other size was not measured here, so this record cannot speak for it. The one exception is the second file on the same host, which is measured and has its own record below.

A hash that fails on a file of the right size means the bytes changed in transit or the file was edited. Either way it is not the recorded file, and installing it anyway throws away the only check you have.

The second file, measured the same day

second file, same host, no channel token
filemmy.apk
bytes21,049,457
sha25696c4f39099f1846cfc7eef4edf19d66f9302f9e17795d055908418217a189177
packagecom.Mymuqiueb.ineb
versionName2.2.5
versionCode225

Same version label, same version code, different package name, and 94,929 bytes larger. The difference is a channel marker packed inside the first file, not a newer build. Android treats the two package names as two apps, so installing both gives two icons named MMY. The button on this site serves the channel file only. What installing both looks like.

What the listing artwork shows

MMY icon: three spade cards over a red M, with a CASH ribbon
Listing icon: J, Q and K of spades, a red M, a CASH ribbon.
Coin pusher cabinet artwork with a Super Winner lamp and rupee tiles
Listing artwork: a coin pusher cabinet, a Super Winner lamp, rupee tiles. Artwork, not a payout table.
Close view of coin pusher artwork with a Super Win lamp and rupee tiles
Listing artwork: closer view of the same cabinet and its rupee tiles.

The install listing pairs the file with coin pusher artwork. The cabinets carry lamps reading WIN BIG PRIZE, Welcome to the Coin Pusher, and SUPER WINNER, plus tiles marked with the rupee sign and multipliers. Those figures are printed on the art. They are not a published offer and not a measured result, so none of them is quoted here. A third image on the same listing shows a hand holding a phone over a payout record panel with named players and rupee amounts; same rule, none of those amounts is repeated on this site.

The developer's own site names six games it builds: Aviator Pro, Dragon Tiger, 7Up 7Down, Andar Bahar, Teen Patti and 3 Patti. The install listing groups its catalogue under seven labels: Aviator, Live Casino, Slot, Card Games, Sports, Fishing and Multi-player. Those are labels, not a counted inventory, so this site does not state how many titles sit behind each one. The game scripts inside the APK are an encrypted index.jsc, so neither list can be confirmed from the file. A hash match proves the file travelled intact. It does not prove what those scripts do.

What this record will not tell you

Who the record is for

You downloaded an MMY file, or you are about to, and you want to know whether it is the one measured here. The answer is a comparison, not a verdict. Read the byte count off your copy and set it against 20,954,528. If it matches, compute the hash and set it against the value in the card above. Two matches and you hold the recorded file. One failure and you do not, and the pages linked from each check say what the failure usually means.

The same comparison works in reverse. If a page tells you the MMY file is a different version or a different size, download the file that page offers and measure it. The file settles the argument. The page cannot.

Figures published elsewhere

Other MMY pages on the web quote version 1.2.4 and file sizes from 32 MB up to 42 MB. Neither figure matches either file measured here. A number typed into a page and a number read off a file are different kinds of claim, and only the second one can be checked against the download in front of you. How to settle the disagreement yourself.

Questions about the record

What does a matching SHA-256 prove?

It proves the file you hold is byte for byte the file measured on 10 November 2026. It proves nothing about behaviour after launch, because the game scripts ship as an encrypted index.jsc and cannot be read back out of the package. A hash is not a malware scan, and this site does not claim one.

Why are there two MMY files with the same version?

The channel file carries an AppsFlyer source marker in a small channel file packed inside the APK, which repeats the app id and the version. That marker accounts for the roughly 95 KB gap between the two files. Both report version name 2.2.5 and version code 225, under different package names, so Android installs them side by side rather than one over the other.

What if the size does not match 20,954,528 bytes?

Shorter means the download was cut off, and a truncated APK fails to parse. Any other size was not measured here, apart from the second file at 21,049,457 bytes, which has its own hash on the second file page.