Data status & methodology

Dataset built 2026-08-25. Every fact in LobbyLens traces back to a specific capture of a specific operator lobby.

OperatorMarketLobby gamesMatchedConfidenceSourceLast checked
888 Casino GB 2,964 2,034 api_seen 888 Casino extract_888_browser.js 2026-08-25 geo ✓
PlayOJO GB 9,134 7,148 api_seen PlayOJO extract_playojo_api.js 2026-08-25 geo ✓
Pub Casino GB 3,081 2,407 api_seen Pub Casino extract_pubcasino.js 2026-08-25 geo ✓
All British Casino GB 3,366 2,681 api_seen All British Casino extract_allbritishcasino.js 2026-08-25 geo ✓
Midnite GB 2,989 2,539 api_seen Midnite extract_midnite.js 2026-07-14 geo ✓
Ladbrokes GB 6,577 5,238 api_seen Ladbrokes extract_ladbrokes.js 2026-08-25 geo ✓
Coral GB 6,523 5,185 api_seen Coral extract_coral.js 2026-08-25 geo ✓
Luna Casino GB 9,134 0 api_seen Luna Casino extract_luna.js 2026-08-25 geo ✓

How captures work

We read each operator's own structured game data (the same APIs their lobby front-end uses), from an egress IP verified to be in the target market — because casino catalogues are geo- and licence-specific. Captures are timestamped; the last checked date is shown on every availability row.

Confidence labels

LabelMeaning
api_seenGame returned by the operator's own games API for this market.
lobby_seenGame observed in the rendered lobby (reserved for operators without a usable API).
unknownNot seen in any tracked lobby. Not a confirmed absence — the game may exist under an unmatched title, or the operator may not be tracked yet.

Match quality

Operator titles rarely match catalogue titles byte-for-byte. Each edge is labelled: exact strong fuzzy_provider_confirmed fuzzy_reviewed

What we don't claim: we never mark a game "unavailable" from silence, alternatives are recommendations (not facts), and stale rows keep their original last-checked date rather than pretending freshness.