Use elapsed time, not the display label
Under Betfair's current football rules, one time-band example defines 0-10 minutes as 0:00 up to but not including 10:00, and 11-20 minutes as 10:00 up to but not including 20:00. This illustrates why a label such as “10th minute” is insufficient for settlement.
| Official elapsed time | Example interval |
|---|---|
| 09:59 | 0-10 band |
| 10:00 | 11-20 band under the cited rule |
| 19:59 | 11-20 band |
| 20:00 | Next stated band |
The actual product can use different labels or boundaries. Copy its interval definition before mapping data.
Exact minute versus interval market
An exact-minute selection and a time-band selection answer different questions. Broadcast notation such as 45+2 describes stoppage time, while a data feed may store elapsed seconds, period time, and announced stoppage separately. The market must say how that event is grouped.
No-goal outcome
A complete interval market needs a state for no qualifying goal. It can appear as No Goal, an interval covering the remainder, or another rule-defined outcome. If visible interval probabilities sum to less than one, check whether the missing mass belongs to no goal or an omitted band before comparing prices.
Illustrative complete probabilities might be 0.24, 0.31, 0.27, and 0.18 across three time bands plus No Goal:
Probability total = 0.24 + 0.31 + 0.27 + 0.18 = 1
Removing the 0.18 no-goal state would leave an incomplete market.
Which goal time controls settlement?
Retain the official goal event, scorer, timestamp, period, VAR state, and correction version. An initially recorded goal can be disallowed, or an own goal can have product-specific treatment. Opta's published football definitions show why provider event contracts matter, but the operator's named settlement source remains controlling.
Worked band return
For an illustrative GBP 8 stake at decimal odds 3.25:
Gross return = 8 * 3.25 = 26
Net profit = 26 - 8 = 18
The return is valid only if the final official first-goal time falls within the exact accepted band.
Verification workflow
- Archive the market's interval boundaries.
- Store official elapsed seconds and broadcast notation separately.
- Confirm first half, full match, extra time, and stoppage-time scope.
- Include No Goal and all residual intervals.
- Apply disallowed-goal, own-goal, and correction rules.
- Map the final timestamp to one and only one interval.
Build boundary fixtures before release
Check synthetic goal events at 00:00, one second before each band boundary, exactly on each boundary, one second after it, the end of first-half regulation, first-half stoppage time, second-half kickoff, and final whistle. Add a no-goal fixture and a goal later disallowed after review. Each event must map to one and only one final settlement state.
Store elapsed match seconds separately from wall-clock time, provider minute labels, and broadcast notation. A display of 45+2 is not a substitute for an event timestamp. Preserve period, sequence, provisional status, final status, and correction time so a disallowed first goal exposes the next qualifying goal rather than leaving the original band in place.
When an operator changes interval labels, version the mapper and rerun historical boundary tests. Do not silently apply new boundaries to old accepted bets; settlement and model evaluation must use the contract that existed at the decision time.
Next step
Use First Goalscorer Betting for the next part of this topic.
Continue learning
- Next guide: Top Goalscorer Betting
- Related guide: Transfer and Next Manager Betting
Assumptions and limitations
The probabilities and price are illustrative. DraftKings' soccer rules and Betfair are operator examples. Time-band labels, official sources, VAR treatment, awarded matches, and abandoned fixtures can differ.

