Android app
The official APK is downloaded from the casino site; Google Play does not carry it.
- Version
- 55.2.0
- Size
- 48.65 MB
- Requires
- Android 7.0
Three ways to play from a phone, and only one of them is a real installation. The phone in your hand decides which of the three suits you.
Android takes an APK from the casino mobile page; an iPhone pins the site instead. Five steps to install the APK.
The Android download is a file, and the file comes from the casino. The mobile page of the official site hands out the APK, and Google Play has no listing for it, which puts the whole business of checking the file on you. The card below carries the build the casino currently publishes.
On iPhone there is no APK to download, because iOS does not install them. The route the casino documents on its own mobile page is the web app: you open the site in Safari and add it to the home screen, and it opens from an icon like anything else. The lobby does show an Apple icon beside the Android one, and where that icon leads I could not confirm.
The third shape installs nothing. The mobile site opens in whatever browser is already on the phone, carries the same login, the same cashier and the same 9,000 slots, and it survives a phone with no free storage. For a lot of people that is the whole answer.
Android app
The official APK is downloaded from the casino site; Google Play does not carry it.
iPhone and iPad
A native iOS app is not confirmed by every source. The working path is the web version added to the home screen.
Mobile version
The site opens in any mobile browser straight from the address bar; the account and cashier are the same.
The long part is the permission dialogue, and it happens once per browser.
Two answers, depending on whose page you read. Cardmates and Casinos Online Colombia state flatly that the app is Android only. Webopedia and Cryptogambler describe an iOS route that turns out, on inspection, to be a web app. The casino settles the practical question itself: its mobile page walks iPhone owners through installing the PWA in 4 steps, and that is the path this guide prints.
A pinned web app behaves close enough to an installed one for a casino: full screen, its own icon, the session kept between visits. What it lacks is a push notification about a tournament, and I have yet to meet the player who mourned that.

It changes the wrapper. One account, one balance, one cashier: a deposit made in the browser shows in the app as soon as you switch, a bonus taken in the app shows in the browser the same way, and the authenticator code is the same code in both. Nothing is stored twice, so nothing can fall out of step.
What it does change is the friction. The icon skips the address bar, the session holds longer, and the games load from a local shell, which spares you a fresh page every time. On a phone you play from daily that adds up; on a phone you touch once a month it does not.
Updates move the other way. The app never appears in Google Play, so nothing reminds you a new build exists: you go back to the same casino page and take the file again. The browser has no such homework.
You need an account before any of this matters. Open an account before installing and the app has something to sign into; the cashier and its limits by method behaves identically whichever wrapper you opened it from.


Four situations, and none of them is exotic. A phone with no free storage. A borrowed or work handset where you install nothing. An iPhone, where the web route is the route. And an Android older than the app allows, which the mobile site serves without complaint.
There is a fifth, quieter case: an app on the home screen is an app somebody can see. The browser keeps the casino inside a tab like every other site.
Everything that genuinely differs fits in the table below, and none of it touches the money. Deposits, withdrawals, bonuses and wagering all run on the casino side and behave the same in either wrapper.
| What is at stake | Android app | Mobile site | Our view |
|---|---|---|---|
| Space on the phone | The install plus every update you keep | Nothing at all | On a full phone this settles the argument by itself. |
| Updates | By hand, from the casino page | Automatic: the site is always the current site | With no Google Play listing, nothing prompts you when a build changes. |
| iPhone | No APK exists for iOS | Opens in Safari and pins to the home screen | The documented Apple route, and the one the casino explains itself. |
| Account, balance, cashier | The same one | The same one | A deposit made in one shows up in the other inside the same session. |
The format is fine. An APK is the ordinary Android package, and every app on the phone arrived as one. The shop is what goes missing: Google Play runs a scan and keeps a version history, and a file taken from a web page has neither. Whoever hosts that file decides what is inside it.
Which reduces the whole safety question to one habit. Take the file from the casino page you reached through a link you trust, and check that page before you download from it: the footer names the company Orakum N.V., the registration number 141651 and the licence OGL/2024/586/0786 from the Curaçao Gaming Authority. A page that names nobody has no business handing you an executable.
Third-party APK catalogues are the common mistake here. They are convenient, they usually work, and they keep whatever build they happened to grab: you end up installing an old version from a host with no obligation to you. If a catalogue is where you found the file, close it and go back to the casino.
One habit after the install that almost nobody bothers with: go back into the Android settings and switch the install permission for that browser off again. It takes a few taps and it closes the door behind you.
From the mobile page of the casino site. The file is handed out there and nowhere else: the app has no Google Play listing, so a download from a third-party catalogue carries a build of unknown age. The button on this page opens the casino through our link.
Android 7.0 or newer, by the version data on Uptodown. An older phone opens the mobile site in its browser with the same account, the same cashier and the same catalogue behind it.
The sources disagree and the casino itself sends iPhone owners down the web route: its mobile page walks through installing the PWA, the web app that lives on the home screen, in 4 steps. Reviewers split between describing a store app and describing a browser shortcut, so the route printed here is the one that works on every iPhone; the rest stays unsettled.
Yes. One account, one balance, one cashier. A deposit made in the browser shows in the app, a bonus taken in the app shows in the browser, and the Google Authenticator code is the same code in both.
The bonus rules index of the casino lists 100 free spins for installing the Android app and signing in. What that index does not print is the wagering on them or the deadline, so treat the number as the headline and read the offer inside the account before you count on it. The offers with published conditions are on the bonuses page.
The APK weighs 48.65 MB at version 55.2.0. The installed app takes more than the file does, as every app does; the mobile site takes nothing.