Operator Evidence Tracker — Release 03: Three Domain-Level Checks

Release 03 of the BETTIMES Operator and Licence Evidence Tracker is a fixed, 59-row snapshot as of 24 September 2026. No brand was added or removed from Release 02. Three records changed because a domain-specific Curaçao Gaming Authority certificate was located for Duelbits, mBit Casino and MyStake. Each moves from “Conflicting source records” to “Registry matched” for the specific domain and licence described below. This is a change in documented evidence, not a claim that the regulator issued a new licence on the release date.

Download the immutable Release 03 CSV and compare it with the retained Release 02 CSV. The live tracker can change after this publication; the two dated files preserve what each release said. The evidence and freshness ledger carries the parallel source-count and check-date view.

Release identity and reproducible files

The release identifier is 2026-09-24-r03; the fixed as-of date is 24 September 2026. The unit is one consumer-facing operator profile per row. Each CSV row retains brand, legal entity, registration jurisdiction, products, markets, licence evidence, evidence status, source count, source types, last-check date, source URLs and the BETTIMES profile path. It is a research index, not a global census of operators or a determination of whether a website may lawfully serve a particular customer.

The Release 03 manifest lists the snapshot files and creation timestamp. The Release 02 manifest remains accessible. We did not overwrite the earlier CSV. A reader can reproduce the change count by joining the two files on the Brand column and comparing each field. The facts below come from that field-level comparison and the linked regulator certificates checked on 24 September 2026.

The summary columns paraphrase the source record; they are not a substitute for the certificate itself. The new certificate is an additional source on each row, so each of the three source counts rises by one. We did not turn a missing market permission into a positive finding.

Duelbits: domain evidence closes one gap, not both contours

In Release 02, the Duelbits profile kept an Anjouan record for duelbits.io under Elevated Entertainment Ltd separate from a Curaçao licence entry for Liquid Entertainment N.V. The older Curaçao row did not show a covered domain in the evidence reviewed by BETTIMES. The tracked public address was duelbits.com, so that omission mattered: a matching company and licence number alone did not prove that the .com domain was on the permission.

The Curaçao authority's B2C certificate, checked 24 September 2026, names Liquid Entertainment N.V., company no. 153298, licence OGL/2024/1507/0838 and approved domains duelbits.com, duelbits.net and sportsbits.com. That directly fills the .com domain gap. It does not merge the separate Anjouan register entry for duelbits.io into the Curaçao permission or imply one regulator oversees both entities. The updated CSV therefore preserves both licence references with domain labels.

mBit Casino: a current domain certificate resolves the legal-form discrepancy for this record

The older mBit Casino profile compared company terms naming Scores55 Tech B.V. with a previous regulator view that used N.V., although the company number and licence number aligned. The current Curaçao certificate for mbitcasino.io, checked 24 September 2026, identifies Scores55 Tech B.V., company no. 162990, licence OGL/2024/1307/0748, the mbitcasino.io domain and Active status.

The Release 03 legal-entity field now uses B.V. for mBit. The historical N.V. reading remains described in the profile rather than being erased from the research trail. This finding is specific to mbitcasino.io. Two other BETTIMES profiles, 7Bit Casino and Katsubet, have related but separately documented entity-form questions. Their flags are not automatically cleared by a certificate for mBit's domain.

MyStake: later certificate, dated status

The Release 02 MyStake profile had a status conflict: its own page described compliance, while the register snapshot reviewed in August showed assessment in progress. The authority certificate for mystake.com, checked 24 September 2026, names GTW B.V., company no. 165433, licence OGL/2024/250/0115 and displays Active status.

That supports a current domain-and-licence match. It does not tell us the date on which the assessment status changed or whether every historic operator statement was accurate. The profile notes the earlier view and the later certificate so a reader can see the chronology instead of receiving a timeless “licensed” badge.

What the release-level counts mean

The same 59 brands appear in both files. Release 02 had 30 Registry matched, 9 Conflicting source records, 11 Review required, 6 No licence record found and 3 Operator-stated rows. After the three documented changes, Release 03 has 33 Registry matched, 6 Conflicting source records, 11 Review required, 6 No licence record found and 3 Operator-stated rows. These are counts of BETTIMES evidence labels within its coverage set, not market shares or assessments of operators' legal compliance.

No other row received a new check date in this release. The 24 September as-of date applies to the snapshot, not to every underlying external source. A row with an older “Last checked” value remains older; that is visible rather than silently refreshed. The research note on why licence status needs a date explains the difference between a recent dataset publication and recent source verification.

Methodology, limits and citation

BETTIMES compares the retained Release 02 CSV against Release 03 by brand key, then checks the changed evidence against the linked primary certificate. A registry match requires the tracked domain, legal entity and licence number to align in the authority evidence for the stated date. Company terms and directory entries can supply context, but cannot by themselves upgrade a record to regulator-matched. We keep company registration separate from gaming authorisation and retain unresolved conflicts on other domains.

The snapshot cannot establish approval in every target market, the exact date a regulator changed a status, ownership beyond the named certificate entity, or the continuing validity of a page after the check date. Curaçao's portal may change. The dataset is curated, and there may be brands or records BETTIMES has not reviewed. If a certificate changes, the next release should preserve this CSV and publish a new check date and source-level change, not retroactively alter Release 03.

Suggested citation: BETTIMES Research Desk, “Operator and Licence Evidence Tracker, Release 03 (2026-09-24-r03),” 24 September 2026, fixed CSV. Cite the authority certificate and individual company profile as well when making a company-specific claim.

Frequently asked questions

Did the three companies receive new licences on 24 September 2026?

That is not what the release says. BETTIMES located or rechecked domain-specific regulator certificates on that date. The certificates show licence identifiers and status, but the release date is a research check date, not the grant date or the date of a regulatory change.

Does “Registry matched” mean a site is legal in my country?

No. It means the named entity, licence and tracked domain were connected by the cited regulator evidence at the stated check date. Market access, product scope, local blocking rules and customer location require separate jurisdiction-specific checks.

Why does Duelbits still have two legal entities in the CSV?

The sources describe different domain and regulatory contours: Liquid Entertainment N.V. under the Curaçao .com certificate and Elevated Entertainment Ltd in the Anjouan .io record. Keeping both avoids projecting one certificate onto an unrelated domain or silently discarding a documented historical record.

Why are 7Bit and Katsubet still marked conflicting if mBit is cleared?

The new certificate identifies mbitcasino.io specifically. Shared company or licence numbers do not automatically resolve another brand's terms, legacy disclosures or domain coverage. Those profiles require their own source-level review.

Can I reproduce the 30-to-33 change?

Yes. Download both fixed CSVs, join on Brand, compare Evidence status and list changed rows. There are 59 rows in each file; the only changed brands are Duelbits, mBit Casino and MyStake. The release manifest preserves file names and creation metadata.

Bottom line

Release 03 is deliberately narrow. Three direct domain certificates improve three records; 56 operator rows do not change. That boundary is the point of a versioned evidence tracker: a reader can see what was newly verified, what remains unresolved and precisely which source supports each status.