Bets.io: the one record here with a revoked licence

A revoked licence means the authority that issued it has withdrawn it. The practical consequence is the one that matters: the complaint route that a licence normally provides is not there any more, whatever the site continues to display.

It does not by itself mean an operator is dishonest, that it has stopped paying, or that anything about the games has changed. It means the external forum has gone, and everything after that is between the account holder and the company.

This site keeps the brand in the table rather than deleting it, because removing the record would delete exactly the evidence a reader most needs to see.

Twelve coins are published: ADA, BCH, BNB, BTC, DOGE, ETH, LTC, SOL, TRX, USDC, USDT and XRP. A maximum withdrawal of 10,000 per transaction is published — a per-transaction cap rather than a periodic one, which limits the size of a single payout without limiting the total.

No studio list is published, no verification threshold is attached to the verification wording, and no founding year is stated.

On weights alone that record would place Bets.io mid-table. The ordering overrides the arithmetic here, and this page exists so the reason is legible rather than mysterious.

Across the thirty records, twenty-seven name a licensing authority and twenty-seven carry a licence number. Twenty-four return a status line from a register. Bets.io is not missing from any of those groups: it names the Curaçao Gaming Authority, carries OGL/2024/1178/0479, and the status comes back revoked. That status is the only revoked line anywhere in the register, among the twenty-four that show one. So the record is well populated in the licence fields, but the one fact those fields return is enough to move it below every live entry.

Sixteen records carry a coin list. Bets.io's twelve coins put it fifth among those sixteen, so its cashier is somewhere in the middle rather than at either end. Fifteen records publish a studio list; Bets.io leaves studios blank, which removes it from that comparison entirely. Six records state a founding year, and Bets.io leaves that blank as well. The pattern is uneven: the record is specific about the cashier and a payment cap, but silent on company age and game suppliers.

Eight records set a withdrawal cap, and Bets.io is one of them. So the populated fields describe a twelve-coin cashier and a 10,000 USD per-transaction limit. The empty fields leave the operator's history and the entire supplier list undefined. A reader looking only at the coin rank and the cap might expect a mid-table position; the table's ordering is the correction, because the revoked status outweighs every count that would otherwise lift it.

Bets.io's licence number is not shared with any other brand in this register. That is not a mark of quality; it only means no companion site appears among the thirty records. The register shows what a shared number looks like elsewhere: ALSI-202508056-FI2 is carried by both Bitkingz and Winz.io, and OGL/2024/1267/0760 is carried by CryptoLeo and Nine Casino. A licence is issued to a company, and a company can operate several storefronts under one number, so the number identifies a holder rather than a website. Bets.io's holder appears only under this one sign here.

The line proves two things and nothing more. It proves the operator chose to display an authority, Curaçao Gaming Authority, and a number, OGL/2024/1178/0479. It also proves that the authority's register returns that number as revoked. What the wider register adds is the count: with a status available on twenty-four records, Bets.io is the only one whose status is revoked. That is the fact the licence line ultimately carries.

Three brands in the register name no licensing authority at all: BetPlays, Crashino and Nitrobetting. Bets.io is not among them. So its gap is not the absence of a name; it is the presence of a name attached to a withdrawn number. A name without a live status can mislead because it looks complete. The shared-number pattern elsewhere is the reminder that even a genuine-looking number can belong to a company that operates several signs, and only the register status tells the reader which of those signs still has a licence behind it.

The promotional capture was read from a server in the Netherlands on 28 August 2026. It returned a headline: 'Casino Welcome Bonus 225% + 225 FS UP TO 1 BTC — Bonus code BETSFTD'. Next to that headline there was no published wagering figure and no published bonus cap. A percentage with a top amount but no wagering requirement leaves the real conditions undefined; the reader knows the headline, not what stands between that headline and any usable balance.

Across all thirty capture attempts, thirteen pages could be read, nine were blocked by a bot wall, six were geo-blocked from the Dutch server, and two failed for another reason. Of the thirteen that were read, ten carried a headline offer. Only two of those thirteen published a wagering figure, and only one published a bonus cap. Bets.io sits in the larger group: a promotional page that gave the headline but did not publish the arithmetic beneath it.

The Bets.io capture also did not show yen in any currency list, and no Japanese interface was seen. Of the thirteen read pages, only one named yen and only two showed a Japanese interface, so Bets.io is not unusual on that point. The capture server location carries no information about Japan; it records only what that server received. The yen and interface absences are observations about the page as captured, not a statement about where the operator may or may not be available.

Four fields are blank in this record: established, studios, studio count, and verification figure. The founding year would have told a reader how long the company behind Bets.io has existed, and therefore how much operating history sits behind the revoked number. Without it, a reader cannot tell a long-running company with a newly revoked licence from a shorter-lived one; the record only says the year is not published.

The studios field would have named the game suppliers the operator says it works with. That list is one of the few ways to verify any claim about the origin or breadth of the games, and it would allow comparison with the fifteen records in the register that do publish one. studio count would summarise that list. Bets.io leaves both empty, so the supplier side of the record cannot be checked against the rest of the register.

The verification figure is the blank that sits next to a long published clause. The clause describes the KYC process: identity documents, source-of-funds checks, and a general 30-day deadline once documents are requested. A figure would have told the reader the monetary level at which verification is likely to be asked for. Without it, the reader knows the operator can ask, but not at what amount the process typically starts. That is the difference between a policy and a threshold.

These blank fields do not change the central finding about the revoked licence, but they limit what a single record can say. The populated fields give a twelve-coin cashier and a per-transaction cap; the empty fields leave company age, supplier composition, and the verification trigger undefined. A reader who needs those details must go to the operator's own documents, and this register cannot supply what the operator has not published.