Data status & methodology
Dataset built 2026-07-02. Every fact in LobbyLens traces back to a specific capture of a specific operator lobby.
| Operator | Market | Lobby games | Matched | Confidence | Source | Last checked |
|---|---|---|---|---|---|---|
| 888 Casino | GB | 3,221 | 2,246 | api_seen | 888 Casino extract_888_browser.js | 2026-07-02 geo ✓ |
| PlayOJO | GB | 8,883 | 6,896 | api_seen | PlayOJO extract_playojo_api.js | 2026-07-02 geo ✓ |
| Pub Casino | GB | 2,996 | 2,328 | api_seen | Pub Casino extract_pubcasino.js | 2026-07-02 geo ✓ |
| All British Casino | GB | 3,275 | 2,599 | api_seen | All British Casino extract_allbritishcasino.js | 2026-07-02 geo ✓ |
| Midnite | GB | 2,968 | 2,500 | api_seen | Midnite extract_midnite.js | 2026-07-02 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
| Label | Meaning |
|---|---|
| api_seen | Game returned by the operator's own games API for this market. |
| lobby_seen | Game observed in the rendered lobby (reserved for operators without a usable API). |
| unknown | Not 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.