All 14 Yono-style apps listed on this site are signed with the same certificate (holder "lamislot") and declare identical permissions and app structure. They come from one build source under 14 brand names. That does not identify who operates each platform's accounts or payments.
Checked 5 October 2026 by the AllYonoEarn Editorial Team.
This site lists 14 platforms that people find when searching for “Yono games”: rummy, slots, and bingo apps with different names, logos, and colours. Each has its own page here, with its own APK file. We read the 14 APK files themselves to see what they say about who built them. They all carry the same digital signature.
What we checked
An Android APK file contains a manifest, which names the app’s package, version, and permissions, and a signing block, which holds the certificate of whoever signed it. Android will only install an update to an app if it is signed with the same key as the version already installed, so the signing certificate is the closest thing an APK has to a fingerprint of its publisher.
We took the 14 APK files offered on this site’s platform pages and read both parts directly from each file. Nothing was installed or run. Every file matched the SHA-256 fingerprint already published on its page.
One certificate signs all 14 apps
All 14 files are signed with the same certificate:
- Certificate SHA-256:
5CBB225FFF2AB9DB2CE018BCBADBD378151F7ED8FCBD3EC9DBEAE6CC1CA8EEEA - Holder: “lamislot” (the organisation, unit, and common name fields all read “lamislot”)
- Valid: 27 April 2020 to 21 April 2045
- Country field: “65”, which is not a valid country code. The certificate was generated without real publisher details.
Only someone holding the private key behind that certificate can sign these apps or ship updates to them. Fourteen different brands sharing one key means one source builds and signs all of them.
The apps are built from the same framework
The similarity goes beyond the signature. All 14 APKs declare:
- the same 9 Android permissions, in the same order
- the same number of components (2 activities, 7 services, 3 broadcast receivers)
- the same resource ID for the app’s name
- the same minimum Android version (5.0) and target version (Android 15)
Only the package name, version number, and branding differ:
| Platform | Package name | Version |
|---|---|---|
| 101z | com.lol.seize.games |
1.1.3 |
| Bingo101 | com.bingo.slots.game |
1.1.4 |
| Jaiho777 | com.jaiho.sss.in |
1.0.9 |
| Jaiho91 | com.jaiho.no.games |
1.0.4 |
| Jaihorummy | com.jo.rummy.apps |
1.1.3 |
| Joyrummy | com.joy.rummy.games |
1.0.2 |
| Rumble Rummy | com.rumble.rmy.games |
1.0.6 |
| Rummy77 | com.rummyss.games.joy |
1.0.7 |
| Slotswinner | com.slot.winner.games |
1.1.3 |
| Spin101 | com.spin.sozo.games |
1.1.2 |
| Spin777 | com.spin.sev.games |
1.1.7 |
| Spingold | com.spin.glg.games |
1.1.3 |
| Toprummy | com.tops.slots.games |
1.1.1 |
| Yonovip | com.vips.games.yy |
1.1.3 |
Some package names don’t match the brand. Top Rummy is com.tops.slots.games and Bingo101 is com.bingo.slots.game, which suggests packages are reused or assigned in bulk rather than chosen for each game.
What this shows, and what it doesn’t
It shows that the 14 apps come from the same build and signing source. Picking “a different Yono game” from this list gets you the same underlying app under another name. A “new” Yono game may be the same software with a new brand.
It doesn’t show who runs each platform’s accounts, deposits, or withdrawals. A white-label developer can build and sign apps for several operators. The certificate gives no company name, address, or country, so it can’t tell you who is accountable if something goes wrong.
Earlier versions of our platform pages said that similar names alone are not evidence of shared ownership. That is still true of names. The signing key is a different kind of evidence, and we have updated those pages to show it.
What to do with this
- Don’t treat the brands as independent choices. If one of these apps has caused you a problem, switching to another name on this list doesn’t mean switching to a different developer.
- Check the signer of any copy you install. Run
apksigner verify --print-certs file.apk(Android SDK build tools) orkeytool -printcert -jarfile file.apk(Java). If the fingerprint differs from the one above, your copy was signed by someone else and is not the same file we checked. - Compare the permissions Android shows you with the 9 listed on each platform page. A copy asking for SMS, contacts, or accessibility access is not the same app.
- Remember the legal position. Since 1 May 2026, India’s Online Gaming Act bans online money games whether based on skill or chance. See our page on online gaming law in India.
For step-by-step instructions on checking a file’s fingerprint, see how to check an APK’s SHA-256 fingerprint, and before installing anything, the APK safety checklist.
allyonoearnYONO GAMES / FIELD GUIDE
Explore Games →
⌕