Every alert, graded
loadingEach alert is graded against Pinnacle's closing line and against the result. Every alert counts: the losing numbers are shown exactly like the winning ones. Alerts are never deleted; corrections are listed in the changelog. Every figure shows how many alerts it rests on and a 95% range (what that means); figures from fewer than 30 alerts are greyed out as too few.
All time
Current rules
By rule version
Every alert keeps the rule version it fired under. When a rule changes, the old alerts stay in the record above; this table compares the versions.
By alert type
By book
Latest alerts
Tap an alert for what it saw when it fired. Marked alerts (void, invalid or test) stay listed with their reason and are left out of the figures.
Changelog
Every correction and rule change, with the date and the all-time figures before and after. Entries are only ever added.
Definitions
- Closing line
- Pinnacle's price for the player when the match starts, with Pinnacle's margin removed: the fair closing price and its probability. Pinnacle is used because its closing price is the most accurate public estimate of the true chance. A match that starts without a Pinnacle price has no closing line, so its alerts have no CLV (their results are still graded).
- Fair CLV (closing line value)
- The fair closing probability minus the alert's fair probability, in percentage points; positive means the alert was ahead of where the market closed. The alert's fair probability: at a bookmaker, its price with that book's own margin removed at that moment (using its price for the other player); at Betfair Exchange, the price net of 5% commission with nothing else removed (an exchange has no margin of its own); at Kalshi and Polymarket, the midpoint of the bid and ask. Alerts without that information have no fair CLV. This is the main figure.
- Price CLV
- The fair closing probability minus the probability in the price the alert quoted, margin included. Stricter than fair CLV, and the one closest to profit at that price.
- Beat close
- The share of alerts with a fair CLV above zero.
- Units
- One unit staked on each alert at its price. Each alert backs one player at one price: the player whose price shortened, or the opponent when a price drifted (at the same book, at that moment); for market and stale-line alerts, the flagged player at the flagged price. A win pays the price minus one, a loss costs one. Betfair Exchange prices are counted net of 5% commission.
- ROI
- Units won or lost divided by the number of decided alerts (one unit each), as a percentage.
- Won-lost
- Decided alerts that won and lost. The range under it is for the share won.
- Void
- The match was not completed (retirement, walkover, cancellation or postponement), as in Pinnacle's tennis rules, or the alert had no price for the backed player. Void alerts count as zero units.
- Pending
- Not graded yet: the match has not finished. CLV is set when the match starts; the result when it ends. An alert whose match never gets a result is voided after 4 days and marked.
- Rule versions
- The alert rules in force when an alert fired (v1, v2, v3 and so on). A rule change starts a new version; alerts fired under earlier versions keep their version and stay in the all-time figures. The "current rules" figures count each alert type from the version that last changed that type's rules: a version that changed only market-value alerts does not restart the count for sharp drops. That keeps the current figures comparable with older versions without throwing away alerts whose rules did not change.
- Void, invalid or test (marks)
- An alert is never deleted. If one turns out to be wrong it is marked: void (should not have been graded), invalid (fired on bad data) or test (sent while testing), with a reason and a date. Marked alerts are listed under the filter and are left out of every figure. Each mark also appears in the changelog.
- 95% range and "too few"
- Each figure shows its count (n) and a 95% confidence interval: the range the long-run value is likely to be in, given how many alerts there are so far. Averages use the normal approximation (mean ± 1.96 standard errors); percentages use the Wilson interval. A figure from fewer than 30 alerts is greyed out as too few: it says very little yet.
- Daily file and its SHA-256
- At 00:20 UTC each night the previous UTC day's alerts, exactly as they were when they fired (no results), are published as a file at bounceodds.app/record/files/<date>.json, and the file's SHA-256 (a fingerprint: change one character and it changes completely) is posted with its link to the public Telegram channel. A published file is never rewritten; the database refuses it. To check: download the file and compute its SHA-256 (macOS or Linux:
shasum -a 256 2026-11-20.json; Windows PowerShell:Get-FileHash 2026-11-20.json), then compare it with the post made that night. If they match, the alerts for that day are the ones sent at the time; an alert added, removed or changed later would not match. - Firing snapshot
- What the alert saw when it fired: the book, its price and the time, the same book's price for the other player, Betfair's matched amount (for Betfair alerts), the bid, ask and 24-hour volume (for Kalshi and Polymarket alerts), Pinnacle's fair price then, and the bet the record grades. Alerts stored before 20 November 2026 have a snapshot rebuilt from their stored fields, marked as rebuilt.
Disclosures
- Operator: Anthony Lobato.
- No affiliate links. Bounce Odds earns nothing when you open an account or place a bet anywhere.
- No payments from bookmakers, exchanges or prediction markets, of any kind. Income is subscriptions only.
- Bounce Odds is an information service, not a tipster, bookmaker or exchange, and does not accept wagers. Past results do not predict future ones.
- 18+. If gambling stops being fun: UK, GamCare National Gambling Helpline 0808 8020 133 and BeGambleAware; US, 1-800-GAMBLER; anywhere, Gamblers Anonymous.