Casino App UK: The Column Our Cards Do Not Have

Wilhelmina Coote / Clause-by-clause editor

Our library holds a hundred operator cards with thirteen fields each, and not one of those fields describes a casino app UK in any form. There is no store listing, no operating system, no download size and no version number anywhere in the data. A casino app is simply not a thing this library measures. That is a blunt answer to a common question, and it is the honest one. What the cards do hold is the address the operator was read at, the licence entry behind that address, and the clauses that apply to an account regardless of the screen it is opened on. This page sets out which of those actually change when you pick up a phone.

What a casino app UK looks like in our data: nothing

Here is the full field list on a card, so nobody has to take our word for the gap. Each card carries an identifier, a display name, a domain, a founding year, a licence object, a coin list, a verification object, a limits object, a restricted-country list, the address that list was read from, a tag list, a note on whether the pages were read live or from an archived copy, and the date they were read. Thirty-three cards additionally carry a studio list. Three carry a note on location masking. One carries a payout object.

That is the whole schema. No field names a platform and no field names a casino app. A casino app UK question therefore cannot be answered from our data at all, and we would rather say so than fill the space with impressions. Anything we wrote about install size, store ratings or how a lobby feels on a small screen would be invention, and invention is the one thing this library exists to keep out.

The founding-year field shows how thin some columns are even where they exist. Eleven cards of a hundred name a year: Cloudbet and Nitrobetting 2013, FortuneJack 2014, Bitsler and Oshi Casino 2015, CoinPoker, Rocketpot, bspin and Sportbet.one 2018, Wild.io 2022, Rakebit 2024. Eighty-nine cards leave it empty. If a field as simple as a founding year is empty on eighty-nine cards, a platform field that no operator publishes in a checkable form was never going to be filled.

The address column is a domain, not a store listing

Every one of the hundred cards is keyed to a web domain: bitstarz.com, cloudbet.com, shuffle.com, duckdice.io, wild.io, rainbet.com, and so on. That is not an arbitrary choice of key. It is the only identifier the licence registers accept.

The Curacao certificate portal is indexed by operator domain, and a lookup returns a certificate naming the domain, the company operating it, that company’s registration number, the licence number, the grant date and the current status. For 7Bit Casino, the entry states that 7bitcasino.com is operated by Scores55 Tech B.V., company number 162990, under licence OGL/2024/1307/0748, granted 16 July 2024, status Active. The Anjouan register works the same way, returning a holder company and an issue date against a domain.

Nothing in either register is keyed to an application listing. So a domain can be checked by number, and an app cannot be checked at all by the same method. For a reader that turns the question around: instead of asking whether a casino app UK exists, ask which domain the account actually lives on, then take that domain to the register and read what comes back. A casino app inherits whatever licence sits behind that domain; it does not carry one of its own.

Sixty-eight of our hundred cards produce something when that is done. Thirty-seven name the Curacao Gaming Authority and twenty-five the Anjouan Gaming Board, with six more naming Antillephone N.V., Curacao eGaming, the Government of Curacao, the Government of the Autonomous Island of Anjouan or M.I.S.A. in single entries. Thirty-two cards produce nothing, because we found no authority on a page we could read. That is a third of the library with no register line to check, which is a far more consequential gap than any missing platform note.

Seven tags, and the tag that does not exist

Our cards carry a tag list, which is the closest thing in the data to a description of what a session looks like. Across the hundred cards, forty-seven are tagged for live dealer content, forty-three for a sportsbook, thirty-seven for a loyalty programme, twenty-one for provably fair mechanics, twenty for original in-house games, fourteen as crypto-only and twelve for instant withdrawal.

Seven tags, none of them about a platform. The vocabulary was built from the pages upward rather than decided in advance, which is why it covers formats and features and stops there. There is no mobile tag, no casino app tag and no download tag, because no operator page we read published anything of the sort in a form we were willing to record. A casino app UK tag would have to come from a page that states it, dated, and none did. The tag vocabulary came out of what the pages actually said.

Read as a set, the tags do tell you something useful about mobile sessions indirectly. Live dealer content is the most common tag on the list at forty-seven cards, which means dealt tables are a majority feature of the catalogues we read rather than a niche one. Original in-house games appear on twenty cards and provably fair mechanics on twenty-one. Those are catalogue facts, not performance claims: we did not measure how any of it behaves on a handset, and we are not going to imply that we did. How the two formats differ in their own terms is covered in how live tables and reels differ.

What a phone does not change: the clause numbers

Every figure our cards hold is written into a document that says nothing about devices. The clause applies to the account, and the account is the same account on any screen.

Fourteen cards state a withdrawal cap. Oshi Casino states 4,000 EUR per day in clause 12. Instant Casino states 4,000 EUR per day in clause 8.1. Wild.io states 100,000 USD per week in clause 9.6. CryptoLeo states 50,000 USDT per month in clause 7.9. Rocketpot states 5,000 USD per month in clause 11.5. Bets.io states 10,000 USD per transaction in clause 10. None of those clauses has a mobile variant, and none of them has a desktop variant either.

Five cards state a verification figure: 2,500 EUR at Bitcasino.io, Sportsbet.io and Livecasino.io, each in a clause 6.6, 2,500 USD at Rocketpot in clause 11.4 and 2,000 USDT at Empire.io in clause 5.4. Two cards state a deadline in days: Vave gives fourteen days in clause 8.7 and Bets.io says a player generally has thirty calendar days. Vave also states a three-day maximum for processing a withdrawal in clause 8.1, and instalments over up to thirty days for amounts above 50,000 USDT in clause 8.8, read on 25 August 2026.

Nineteen numbers in total across a hundred cards, and not one of them moves because of a handset. Anyone comparing a casino app UK against the same operator in a browser is comparing two front ends onto one set of clauses. A casino app and a browser window are two doors into the same ledger. The arithmetic those clauses support is worked through in dividing a balance by the stated cap.

The country list does not read your handset

Thirty-eight cards publish a restricted-country list as part of their terms, and twenty-nine of those thirty-eight name the United Kingdom among the countries the operator says it does not accept. Lengths run from a single entry at Stake, Coins.Game, Bitsler and Bitcasino.io to 224 entries at Oshi Casino, with Mirax at 220, Bitkingz at 218, PlayAmo at 217 and Slotum, Bitdreams and 7Bit Casino at 216 each.

That list is a clause about countries, not about devices, and it applies identically whether the account is opened in a browser or anywhere else. We do not publish ways around such a list on any page of this site, and three cards make the consequence explicit in their own words: Cloudbet records balance confiscation for play from a country it names as prohibited, Flush records a clause 3.4 prohibiting location masking outright, and Stake records clause 14.4 naming location masking a breach of its terms. Those are the sentences worth reading before any other part of the document.

The point for a mobile reader is narrow and worth stating plainly. A casino app UK download is not a different account, a different clause or a different country list. If the operator document names a country, the phone is irrelevant to it. All 38 lists are set side by side in how long each restricted-country list runs.

Where the licence line sits, and why it is not per-platform

A licence entry names a holder company and a domain, and that is the level at which it can be checked. Cloudbet holds OGL/2024/328/0599, holder Halcyon Super Holdings B.V., granted 23 May 2025, status Active. Stake holds OGL/2024/1451/0918, granted 9 June 2025, Active. DuckDice holds ALSI-202509013-FI1, holder Zentari Limitada, with an Anjouan register entry dated 16 September 2025. Vave holds OGL/2024/1676/0905, holder Latcas B.V., issued 19 May 2025, read on 2 September 2026.

Read against the registers on 26 August 2026, thirty-two of our entries came back Active, twenty-four came back valid, five came back Revoked and one had a term that ended on 2 September 2026 and has not been re-checked since. The five revoked entries are the reason our rating refuses to publish a number for those cards at all.

Six Curacao numbers are shared by more than one brand, which is worth knowing before treating two front ends as two businesses. OGL/2024/1307/0748 sits behind 7Bit Casino, Katsubet and Mirax. OGL/2024/1798/1048 sits behind Rolletto, Goldenbet and Velobet. On the Anjouan side, one holder, Novatrix SRL, appears behind five brands with the same entry date of 25 August 2025: Oshi Casino, PlayAmo, Slotum, Winz.io and Bitkingz.

None of that is platform-specific and none of it could be, which is why casino apps do not appear in a register anywhere. A register entry describes a company and a domain, so a reader who wants to know who is holding the money should look there rather than at a front end. Which domains were still answering when we last looked is a separate check, kept at which domains still answer.

The read date is the perishable part

Everything on this page carries a date, and the dates are the reason any of it can be argued with. Ninety-nine of the hundred cards were read on 26 August 2026 and one on 2 September 2026. Thirty-eight were read from live pages, forty-one from an archived copy of the same pages, and twenty-one could not be read at all. The register lookups behind the licence lines were run on 26 August 2026. The location-masking notes on three cards were checked on 27 August 2026. The Vave payout clauses were read on 25 August 2026.

Those dates matter more for a front end than for a document. A terms page is revised occasionally and a register entry changes hardly at all, but a lobby can be rebuilt in a week. That asymmetry is exactly why we record the slow-moving fields and leave the fast-moving ones alone: a claim about a casino app made in August is worth very little in September, whereas OGL/2024/328/0599 granted on 23 May 2025 still reads the same way whenever it is looked up.

There is one field where the date did real work. Vave payout clauses were held on four dozen sites across our network and were missing here until 4 September 2026, and in the gap two of our own pages claimed no operator publishes a processing window. That was wrong, it came from an empty cell being read as an absence, and the fix was to fill the cell rather than to soften the claim.

The general rule follows from that mistake. An empty cell is unread, not absent. A casino app UK question sits in the same category: our data has nothing to say about it, which is a statement about our reading and not a finding about any operator.

What we would need before rating a casino app UK

Three things would have to exist before this site could put a number on a casino app UK, and none of them does today.

The first is a published, dateable statement from the operator that a given casino app belongs to a given domain. Without it, a casino app is an unattributed piece of software, and our whole method, which is reading an operator’s own pages and recording the address and the date, has nothing to bite on.

The second is a register lookup that accepts something other than a domain. The Curacao portal is indexed by domain and the Anjouan register returns a holder against a domain. Until a listing can be resolved to a licence entry by number, a platform claim cannot be checked the way OGL/2024/328/0599 can be checked.

The third is a clause that differs by platform. We read a hundred documents and found none: the caps, the verification figures, the deadlines and the country lists are written once and apply to the account. If an operator ever writes a separate mobile clause, that is the day this page gains a number.

Until then, the useful habit is the boring kind. Check the domain, not the casino app. Take the domain to the register and read the number, the holder and the status. Then read the caps and the country list in the same document, on whichever screen is nearest. The operators we currently hold a readable card for are ranked among the UK crypto casinos on our front page, the clause-level reading order is set out in the clauses that apply on any screen, and the catalogue side of the same question is in who builds the games in the lobby.