01 / Game identity
Know the game.
A stable code connects the format, market and schedule.
- code
- Stable identifier
- numbers
- Main and bonus numbers
- timezone
- Time zone of the draws
Lottery data: results, jackpots, prizes Every draw.
With its context.
Winning numbers are only part of the story. Bring results, schedules, jackpots and prize information together in a consistent structure, with clear states for what is known and what is still missing.
DRAW RECORDIllustrative example
EuroMillions
EU-002 · Europe
Main numbers / Lucky Stars
07182436490311
- Result
- Numbers recorded
- Prize details
- Pending
Same result, structured data
{
"lottery_code": "EU-002",
"sorted_numbers": [7, 18, 24, 36, 49],
"bonus_numbers": [3, 11]
}Inside the dataset
A clear structure. At every level.
From game identity to individual results and their history, each part has a place.
02 / Draw record
Read the result.
Numbers and prize information keep their own availability states.
- drawn_at
- Draw timestamp
- sorted_numbers
- Main result
- prizes_status
- Prize availability
03 / Data context
Follow the detail.
Understand what changed and how much history is available.
- Revisions
- Before and after
- Jackpots
- Recorded estimates
- Coverage
- Game-level measurements
Available fields and history vary by lottery. Missing values remain explicit.
Know what you are working with
Broad coverage.
Specific about the details.
A useful dataset makes its limits visible. Check coverage at the game level and use the available measurements to understand what your application can show.
Coverage is game-specific.
Browse the catalogue by country and lottery. Game formats, bonus numbers, schedules and available history differ, so start with the games your product needs.
History has a starting point.
Historical results and jackpot observations depend on what has been collected for each game. Jackpot history begins when tracking starts; an empty period is not a record of zero activity.
Quality can be inspected.
See completeness and publication delay over the last 30 days, recalculated every day. Expected and missing draws can be measured where a fixed schedule makes that possible.
Beyond the draw
The rules of the game.
And the rules around it.
A game is more than its results. Each one carries what a ticket costs and what it can win, and each market the legal frame the game is sold in.
The game sheet.
The price of a play and its paid add-ons, when sales close before a draw, the jackpot odds and, for fixed-odds games, the payout table — plus the logo, brand colours and ball colours to present it, where available.
The legal frame.
For each researched country and state: minimum age, regulator and operators, tax on winnings, how long a prize can be claimed, whether tickets are sold online and where to find responsible-gambling help. A summary of official sources, not legal advice.
Availability is part of the data
Make room for what is unknown.
A published result, a confirmed prize and complete coverage are different things. Keep those distinctions in your product.
01
Recorded result
Winning numbers are available for a draw. Prize information may still be pending.
Show the result and give prize information its own status.
02
Pending or unavailable
A value has not been reported or is not available. A null amount does not mean zero.
Keep the missing value explicit instead of displaying a zero payout.
03
Revised result
A previously recorded draw has been corrected. Revision history preserves before-and-after values.
Update your stored result and refresh any affected views.
04
Unmeasurable coverage
There is not enough schedule information to calculate an expected-draw measurement.
Present the measurement as unavailable instead of assuming full coverage.
Let’s build something useful
Your product.
A world of possibilities.
Whether you’re adding lottery results to an existing website or building something entirely new, start with a clearer view of the data.