License Audit · Quarterly Refresh · CC-BY-4.0

Curaçao GCB License Status Tracker 2026 - Per-Operator Public Register Audit

Of the 9 Day 1 operators we audited against the Curaçao Gaming Control Board public register, license status falls into four categories. 6 of 9 show actively current Curaçao GCB licenses cross-referenced against public register + 6-month Wayback archive. 1 of 9 holds a lapsed pre-2023 Antillephone sub-license with no documented migration to the new GCB framework. 2 of 9 are licensed in different jurisdictions (Anjouan) rather than Curaçao. We re-audit every 90 days. Below: the per-operator table, the framework explained, anomaly categories, and the raw dataset for download.

Executive summary

Four findings from the Q2 audit

Each finding is a standalone citation-ready statement, anchored in the per-operator table that follows. Quarterly refresh cycle means these numbers may shift at next audit (1 Sep 2026).

  1. 6 of 9 operators hold actively current Curaçao GCB licenses cross-referenced against the public register, operator footer, and 6-month Wayback archive. Stake (OGL/2024/1451/0918), Cloudbet (OGL/2024/328/0599), BitStarz (OGL/2024/165/0185), Vavada (OGL/2024/252/0153), Roobet (OGL/2024/687/0427), and Shuffle (OGL/2024/1337/0628). All six issued under the post-2023 LOK framework refresh.
  2. 1 of 9 holds a lapsed pre-2023 Antillephone sub-license without documented GCB migration. 1Win footer shows 8048/JAZ2018-040, an old Antillephone master-sub-license issued well before the 2023 framework refresh. No public-register match on the current GCB lookup. No Wayback evidence of migration announcement to direct GCB licensing.
  3. 2 of 9 are licensed in a different jurisdiction. BC.Game moved to Anjouan in 2024 (ALSI-202410011-FI1, Twocent Technology Limited, Belize). FortuneJack on Anjouan + Costa Rica (ALSI-202411021-FI1, PlayWave SRL, Costa Rica CE-2024-206981). Neither claims Curaçao licensing in footer; both included in tracker for completeness so readers searching "is X licensed in Curaçao" get accurate cross-jurisdiction answer.
  4. 0 of 9 show silent-operator anomalies (license claim in footer with no number) or footer-register mismatch (number in footer not findable in current register) in this audit window. Improvement from 2025 baseline where industry-wide silent-operator anomaly rate sat at approximately 15% of audited operators.

Methodology

Three-source verification per operator

Status "actively current" requires all three sources to agree. Anything less is flagged in the per-operator table below with the specific divergence. Full protocol: how we test §7.

Audit protocol

  • Window: Q2 2026 audit. 1 April - 8 June 2026.
  • Source 1 - public Curaçao GCB register lookup: claimed license number queried against the GCB B2C register. Match required; partial match flagged.
  • Source 2 - operator footer audit: license number + issuing-authority text + link-target validation. Screenshot at audit time with ISO 8601 timestamp.
  • Source 3 - Wayback Machine archive: 6-month look-back via Wayback Machine. Footer claim must show uninterrupted display for prior 6 months. Gap in archive = noted, not flagged as definitive lapse.
  • Status categories (four): actively current (all 3 sources match) · transitioning (provisional or legacy code per framework refresh) · lapsed (number once verifiable but no longer in register) · other jurisdiction (operator now licensed outside Curaçao - Anjouan, Costa Rica, etc).
  • License number format validation: post-2023 GCB issues OGL/YYYY/NNN/NNNN alphanumeric codes. Pre-2023 sub-licensing used different code patterns (Antillephone 8048/JAZ2018-040, Cyberluck 1668/JAZ, etc).
  • What we did not verify: private operator-GCB agreements, internal compliance audits, beneficial-ownership disclosure beyond register entries. These are not public data sources.

Affiliate disclosure: multiple operators in this audit are commercial partners. Verification protocol identical regardless of commission tier. Vavada is an affiliate-partner operator - disclosed inline in the table below. Full policy: affiliate disclosure.

Per-operator data

License status across all 9 Day 1 operators

Each row = one operator audit at Q2 close. License # = footer claim. Status = verification outcome per three-source rule. Last Verified = ISO 8601 timestamp of register lookup.

Operator License # Issuing entity Verified Status Review
Stake OGL/2024/1451/0918 Medium Rare N.V. #145353 (Curaçao GCB direct) 2026-06-04 Current view
BC.Game ALSI-202410011-FI1 Twocent Technology Ltd, Belize #41939 (Anjouan, not Curaçao) 2026-06-04 Other juris. view
Shuffle OGL/2024/1337/0628 Natural Nine B.V. #160998 (Curaçao GCB direct) 2026-06-05 Current view
Cloudbet OGL/2024/328/0599 Halcyon Super Holdings B.V. #148526 (Curaçao GCB direct) 2026-06-05 Current view
BitStarz OGL/2024/165/0185 Gareton B.V. #160656, Dama N.V. group (Curaçao GCB direct) 2026-06-04 Current view
FortuneJack ALSI-202411021-FI1 PlayWave SRL, Costa Rica CE-2024-206981 (Anjouan, not Curaçao) 2026-06-05 Other juris. view
Vavada OGL/2024/252/0153 Vavada B.V. #143168 (Curaçao GCB direct) 2026-06-04 Current view
Roobet OGL/2024/687/0427 Raw Entertainment B.V. #157205 (Curaçao GCB direct) 2026-06-05 Current view
1Win 8048/JAZ2018-040 1win N.V. · Antillephone pre-2023 sub-license (not in current GCB register) 2026-06-05 Lapsed view

Framework context

Pre-2023 sub-licensing vs post-2023 GCB direct

Curaçao's gambling-licensing framework underwent the largest refresh in its history starting 2023. Without this context, the difference between a current GCB license and a lapsed Antillephone sub-license looks cosmetic. It's structural.

Pre-2023

Four-master sub-licensing model

Curaçao maintained four master license holders (Cyberluck, Antillephone, Curaçao eGaming, Gaming Curaçao) who issued sub-licenses to thousands of operators with minimal vetting and limited consumer-protection enforcement. The label "licensed in Curaçao" carried only weak verification value.

  • Sub-license code format example: 8048/JAZ2018-040 (Antillephone), 1668/JAZ (Cyberluck)
  • Operator vetting delegated to master licensors - inconsistent
  • Limited public-register transparency
  • Complaint-resolution channel through master licensor only
  • 1Win's 8048/JAZ2018-040 falls in this legacy class
Post-2023

LOK framework - GCB direct B2C licensing

The Landsverordening op de Kansspelen (LOK) framework refresh installed the Curaçao Gaming Control Board (GCB) as the direct licensor. New operators apply directly to the GCB. Existing sub-license holders given a provisional period to migrate or exit. Stricter complaint handling, mandatory dispute resolution, beneficial-ownership disclosure.

  • License code format: OGL/YYYY/NNN/NNNN alphanumeric (issued by GCB direct)
  • Direct AML/CFT obligations on the operator entity
  • Public-register transparency (license + entity look-up)
  • Six of nine Day 1 operators in our audit hold this new-format license
  • Code prefix OGL/2024/ means the license was issued or migrated in 2024 under LOK

Anomaly categories

Three categories of audit divergence

Across the Q2 audit, three categories of anomalies are possible. Two surfaced; one did not. Cross-reference: operator shutdown history for the connection between licensing anomalies and historical shutdown precedents.

Category 1 0 / 9

Silent operators

Operators whose footer claims "licensed and regulated" without providing a number. Zero operators in our Day 1 roster fall in this category. This is an improvement on the 2025 industry baseline of approximately 15% silent-operator rate. Consumer recourse limited when this anomaly surfaces; cannot verify via public register.

Category 2 1 / 9

Lapsed / pre-2023 footprint

1Win still displays the legacy Antillephone code 8048/JAZ2018-040. Not findable in current GCB register because Antillephone master sub-licensing exited the post-2023 framework. No documented migration announcement in Wayback archive over 6 months. Operator runs on pre-2023 footprint without LOK upgrade.

Category 3 0 / 9

Footer-register mismatch

License number in operator footer not findable in current public register. Zero operators in our Day 1 roster show this anomaly. Common explanations when surfaced elsewhere: outdated footer not refreshed after license-change event, true lapse not yet reflected in operator marketing, register-side data lag.

Why this matters

License status is a signal, not a guarantee

A current Curaçao GCB license under the LOK framework is a real consumer-protection floor. It is also one of the lower-cost obligations in regulated gambling. Both things matter for how you weigh it against other trust signals.

What a current GCB license actually does

  • Establishes a dispute-resolution channel. Complaints can be filed with the GCB directly; the operator is obligated to respond under the LOK framework.
  • Triggers AML/CFT obligations. The operator entity must implement anti-money-laundering monitoring + counter-financing-of-terrorism controls. This is the legal basis for the KYC behavior tracked at /testing/kyc-severity-index/.
  • Requires beneficial-ownership disclosure to the regulator (not necessarily public). Reduces opacity at the corporate-entity level.
  • Subject to GCB enforcement actions - revocation, fine, public censure. Real teeth in 6 documented cases since framework refresh per our shutdown history research.

What it does not do

  • Does not guarantee zero payout dispute. Disputes do go to the GCB, but resolution can take 30-90 days.
  • Does not guarantee zero shutdown risk. Operators can lose licenses; player funds can be at risk depending on segregation rules and bankruptcy proceedings.
  • Does not require full player-fund segregation in escrow at the level of higher-tier regulators (UKGC, MGA). Pooled player funds are common.
  • Does not certify game RNG independently. RNG certification is a separate dimension (iTech Labs, GLI, eCOGRA), tracked in per-operator reviews.

Risk framing: a lapsed or never-confirmed Curaçao license materially raises the risk of a payout dispute without recourse - the dispute-resolution channel does not exist. Factor this into your operator choice especially for deposits above your tolerance. Cross-reference: operator shutdown history + operator rankings.

Refresh cadence

Quarterly re-audit commitment

We re-audit every 90 days on a fixed calendar. Off-cycle updates triggered by operator-side license-change announcement, GCB register removal, or framework-refresh policy shift. Each refresh archives the previous quarter in the CSV with a change-log column.

2026-03-01 Q1 2026 audit - baseline establishment. 9 operators audited under pre-LOK methodology snapshot. Past
2026-06-08 Q2 2026 audit (current) - first LOK-aware audit. 6 GCB current / 1 lapsed / 2 other juris. Now
2026-09-01 Q3 2026 audit (next) - watch list: 1Win migration status, Anjouan-to-Curaçao reversal if any. Next
2026-12-01 Q4 2026 audit - annual roll-up + year-over-year status-change synthesis. Future

Off-cycle triggers: operator-side license-change announcement, GCB register removal, framework-refresh policy shift. We do not chase rumors. Change-log column in the CSV records each modification with ISO 8601 timestamp + source URL.

Limitations

Five limitations of this audit

Scholarly transparency: here's what this tracker does NOT capture and where to triangulate.

  1. Public-register lag. The GCB register may show 7-30 day lag between license issuance/revocation and public update. Status-as-of-audit-date is point-in-time; next quarter may differ.
  2. Private agreements. Operator-GCB agreements during framework transition are private. We cannot see expected resolution timelines for operators flagged transitioning at one audit and current at the next.
  3. Sub-license edge cases. Some pre-2023 sub-license arrangements remain in transitional limbo. Status may be "valid but unverifiable" from public lookup alone; we mark these as lapsed pending direct GCB confirmation.
  4. Wayback coverage gaps. Wayback Machine archives miss some operator footers; absence of archive does not equal evidence of non-display. We note the gap, do not flag definitively.
  5. Operator footer changes. Operators may update footer text faster than register updates; mismatch in any single audit window is noted, not flagged as definitive lapse until confirmed across two consecutive quarters.

Raw data

Download full audit dataset

Columns: operator, license_number, status, issuing_authority, footer_text, last_verified_iso8601, public_register_match_bool, wayback_6mo_bool, change_log, audit_quarter. CC-BY-4.0 licensed; use it for your own analysis, secondary research, or independent verification of our findings.

FAQ

Frequently asked questions

Is the Curaçao gambling license safe?

A current Curaçao GCB license is a real consumer-protection signal but not a guarantee.

It establishes a dispute-resolution channel, AML/CFT obligations, and beneficial-ownership disclosure to the regulator. It does not guarantee zero payout dispute, zero shutdown risk, or full player-fund segregation.

License status is one of several trust dimensions to weigh; track our quarterly re-audit for status changes.

Why do some operators not show their license number?

Three reasons documented:

(1) operator transitioned to a different jurisdiction (Anjouan, Antillephone) and footer still references generic "licensed and regulated" wording without the new number;

(2) operator mid-framework-transition with provisional code not yet public-register-verifiable;

(3) outdated footer not refreshed after license change.

None of these necessarily mean the operator is unlicensed; they mean public verification requires additional steps. See per-operator notes in our table above.

What is the Curaçao Gaming Control Board?

The Curaçao Gaming Control Board (GCB) is the gambling regulator of Curaçao, established under the Landsverordening op de Kansspelen (LOK) framework refresh that began in 2023.

The GCB issues direct B2C licenses to gambling operators, replaces the legacy four-master sub-licensing model, and enforces AML/CFT obligations + consumer-protection rules. Reference jurisdiction for the majority of offshore crypto casinos.

What is the new Curaçao gambling framework?

Starting 2023, Curaçao transitioned from a master sub-licensing model (where four master license holders issued sub-licenses to thousands of operators with minimal vetting) to direct-from-GCB B2C licensing under the LOK (Landsverordening op de Kansspelen) framework.

New operators apply directly to the GCB. Existing sub-license holders were given a provisional period to migrate. Stricter complaint-handling, mandatory dispute-resolution, and beneficial-ownership disclosure.

License code format changed from sub-license codes (e.g. 8048/JAZ2018-040) to GCB-direct OGL/YYYY/NNN/NNNN.

How was this data verified?

Three-source verification per operator:

(1) public Curaçao GCB register lookup for the claimed license number;

(2) operator footer audit with screenshot timestamp;

(3) Wayback Machine archive of the operator footer over the prior 6 months.

Status is "actively current" only when all three sources agree. Full audit log in CSV. Methodology: how we test §7.

How recent is this data?

Current audit: 8 June 2026 (Q2 publication).

Quarterly re-audit cadence with next refresh on 1 September 2026 (Q3). Off-cycle updates triggered by operator-side license-change announcements, GCB register removal, or framework-refresh policy shifts.

Each refresh archives the previous quarter's snapshot in the CSV with a change-log column.

Can I download the license data?

Yes. CSV and JSON download links in the §Raw Data Appendix above.

Licensed CC-BY-4.0. Cite as: Chen & Hartwell (2026), Curaçao GCB License Status Tracker 2026.

Use it for your own analysis, secondary research, or independent verification of our findings.

Citation + continuing audit

Formal citation + license + sibling research

Formal citation

Generated under ChainBankroll Testing Protocol v1.0. Full protocol: how we test.

Standards & Compliance

How we work - standards

Methodology Launch baseline Deposit fees KYC severity index Affiliate disclosure

Quarterly re-audit cadence. Each refresh archives the previous quarter in the CSV with change-log column. Vavada is an affiliate-partner operator (disclosed inline in the per-op table). Reader-reported errors corrected within 7 days with a dated note.