UK-Licensed Casino Operators

How to read an operator row

The brand is the consumer-facing name. The registered entity is the legal account holder named in the source, and the licence number identifies that account on the Gambling Commission register. The status records the relationship between the domain and the licence on the snapshot date. Keeping those fields separate prevents a familiar trading name from being mistaken for the company that holds the permission.

A repeated number can therefore be meaningful rather than an error. Ladbrokes and Coral appear as separate brands, but both rows name LC International Limited and carry the same licence number. The two rows show that one registered account holder can trade through more than one consumer-facing name. The shared number is what connects those records.

A White Label row reflects another arrangement: the domain trades under a licence held by a different company. That is why the entity shown beside a brand may be unfamiliar even when the brand itself is well known. Reading the brand, entity, number and status together preserves the structure recorded in the source instead of compressing it into a single "licensed" label.

What the three domain statuses record

The domain file uses Active, Inactive and White Label. In the dated file, Active records that a domain was tied to a licence in force. Inactive records that it was not, without giving the reason for that position. White Label records that the domain operated under another entity's licence. The words describe register relationships; they are not summaries of customer experience or business conduct.

That narrow meaning matters when two records look similar. A brand can share a licence number with another brand because both belong to one account holder, while a White Label domain can show a company name that differs from the trading name. Neither arrangement can be understood from the brand alone. The legal entity and number supply the account context that the status needs.

The domain status field contains no payment limits, withdrawal times, complaint history or enforcement narrative. Those subjects require different evidence. This page therefore confines each row to what the source actually records and does not turn a register label into a broader assessment of the operator.

Why the snapshot must be read as one dated record

The date shown with the list belongs to the register files used for the check. It is not a live timestamp and does not move forward when the page is opened. A domain, entity or licence relationship may change after that date, so anything that depends on the current position needs a fresh reading of the Commission's register.

The entity, licence number and status in each row stay on the same dated footing. Updating only one field from a later reading could combine facts that were never true at the same time. A clean recheck starts with the legal entity and licence number on the account record, then matches the domain status from the same edition. If a later edition differs, the two readings describe different dates rather than a score moving up or down.

The nine rows also remain in the supplied source-sheet order. They are the complete set referenced elsewhere on this site, not a directory of every UK licensee. The sequence has not been recalculated from status, company structure or any performance measure, and every entry receives the same fields and link treatment. That preserves the source without adding a ranking, rating or endorsement.

Rechecking a row uses two register files

The public register separates domains from licences. The domain file answers whether a specific web address was recorded against a licence account and supplies one of the three domain statuses. The licence file identifies the account holder and the permissions held on that account. A check based only on the trading name skips the relationship between those two records, which is precisely where a brand name can differ from the legal entity.

The two files also use different status vocabularies. Active, Inactive and White Label belong to the domain record; the licence file has a wider set of values for the licence itself. A domain status should therefore not be copied across and described as the licence's status. The account number is the bridge: it connects the domain entry to the legal holder and licence record without assuming that similarly worded fields mean the same thing.

A domain search can return more than one row because the file records address-and-account pairs. Where that happens, the records form a set rather than alternatives from which the checker may pick a preferred result. Each account relationship needs to be read on its own terms. The operator list keeps one sourced entity, number and status beside each supplied brand; it does not use the display order to resolve a multiple-row register result.

Exact addresses matter as well. The domain file records hosts, not a broad brand family, so a nearby spelling or a different country domain cannot stand in for the address being checked. The fuller register-check page handles the address normalisation and returns every matching row. This list has the narrower job of showing the dated fields already established for the nine brands referenced on the site.

How the source sheet and register divide the evidence

Two inputs do different jobs here. The source sheet supplies the nine consumer brands and their sequence. The register snapshot supplies the registered entity, licence number and domain status shown beside each brand. Treating those inputs separately makes the limits of the page visible: the source sheet explains why an operator appears, while the register explains the legal-account fields attached to it on the stated date.

That division also prevents one source from being asked to answer a question it does not contain. The source sequence cannot update a licence status, and the register does not say which brands this reference should cover. A maintenance pass needs to preserve the supplied set and order unless the source sheet itself changes, while a new register reading needs to refresh the entity, number and status as one dated group.

Completeness is therefore local rather than market-wide. These are all nine operators referenced by the method pages in the current source, but they are not presented as every licence account or every casino domain in Great Britain. The distinction matters when a brand is absent: it means the brand is outside this site's supplied set, not that the register has returned a negative result for it. Register absence can only be assessed through an exact-domain check against a stated edition.

The same boundary applies to changes over time. A later snapshot may alter a row without changing the source-sheet sequence, or a later source sheet may alter the covered brands without changing a register fact. Recording which input changed keeps an editorial update from being mistaken for a regulatory event. On this page, the source order and the register date remain visible so those two kinds of change can be told apart.

What an outbound operator link changes

The link label uses the consumer brand because that is the destination a reader will recognise. The disclosure in the same row preserves the registered entity, licence number and dated status. Together they identify both the third-party destination and the legal account context behind the source record. Pocket Vegas does not receive deposits, create player accounts or process withdrawals.

A referral relationship can affect the commercial context of a link, which is why that possibility is disclosed before the link is followed. It cannot supply or alter a register field. Operator terms remain the source for account procedures and cashier settings, while the current Commission register remains the source for any status check that needs to be newer than this snapshot.