Match Win Probability Calculator
Estimate live win probability with pressure gauges, what-if sliders, phase analysis, a probability matrix, and DLS-aware support for rain-interrupted matches.
Win Probability Engine
LiveInputs recalculate instantly. The model is a calibrated logistic across required run rate, wickets in hand, format and phase — designed for fan intuition, not gambling.
Match Setup
Chasing Team — Now
What-If Sliders
Drag to model the very next phaseTeam 1 — Current Position
Conditions
—
Probability Split
Match phase
—
Pressure index
—
Boundary need
—
Acceleration
—
Runs Needed
—
to win
Balls Remaining
—
deliveries
Required RR
—
runs/over
Current RR
—
so far
Wickets Left
—
in hand
Projected Score
—
at current pace
Pressure Breakdown
Probability Trajectory
If T2 sticks to current pace, here's how win probability evolves over remaining balls.
📚 Famous Probability Swings
Each scenario captures a pivotal moment. Click to load it into the calculator.
Understanding live win probability in cricket
Win probability is a statistical estimate of the chance a team has to win the match given the current situation. It is the headline number you see on every live broadcast — and it is now everywhere in cricket coverage, fantasy apps and post-match analysis. This tool is designed to demystify it: live recalculation, explicit pressure components, and a sensitivity matrix so you can see exactly how the model responds to the inputs.
What this calculator gives you
- Live gauge that updates as you change any input — no Calculate button.
- Pressure breakdown: required-vs-current rate, wickets, phase and venue laid out as their own bars.
- What-if sliders: model the next phase by boosting the boundary rate, dropping a hypothetical wicket, or dialling the death-overs pressure penalty up or down.
- Probability trajectory: an SVG curve showing how the chance evolves if Team 2 holds its current pace.
- What-If Matrix: a heatmap of win % across wickets-in-hand × balls-remaining for the current runs-needed.
- First-Innings Projection: a separate mode that projects Team 1’s likely final total and the implied probability for both sides.
- DLS-aware: a single toggle that lets you plug in revised overs from the DLS Calculator for rain-interrupted matches.
How the model works
Internally the engine is a logistic function on a small set of features:
- Required run rate relative to format baseline. Each format has a representative scoring rate (≈5.5 RPO for ODI, ≈8.5 RPO for T20, ≈11 RPO for T10). The model compares the chase’s required rate to this baseline.
- Wickets in hand. Heavily weighted, with extra penalty below 4 and an extra bonus above 7.
- Phase of innings. The death overs apply an additional pressure multiplier when the required rate is well above baseline.
- Venue bias. Shifts the baseline up or down by ±0.5 RPO for batting / bowler-friendly conditions.
Key tipping points to know
- RRR above 12 in T20: Probability dips below 30% unless wickets are very much in hand.
- 5 wickets down in the powerplay: Probability collapses by 30+ points even if the rate looks fine on paper.
- 50% of target at 60% of overs with 7+ wickets: Probability typically above 60%.
- Last over death scenario: A team needing 12+ off 6 balls with 1 wicket is below 10% — modern boundaries are big but death bowling has improved dramatically.
DLS-aware win probability
For rain-affected matches you typically (a) compute a revised target with the DLS calculator, then (b) feed the revised target and revised overs into this tool. Toggle DLS Mode to On and enter the revised total overs in the ‘Match Overs’ field — the engine’s math now correctly accounts for shortened balls remaining.
How accurate is it?
Broadcast probability models can include player-specific batting/bowling performance, ball-by-ball matchups and venue history — features that need proprietary data. Our open model captures the dominant factors and tracks broadcasts well at the strategic level. Expect small differences ball-by-ball and treat the percentages as ranges, not points.
Famous probability swings
Some of cricket’s greatest matches feature dramatic probability shifts. Tap any scenario card below the calculator to load it: the 2019 ODI World Cup Final’s Super Over, Carlos Brathwaite’s four sixes in the 2016 T20 WC Final, and RCB vs KXIP from IPL 2020 where Punjab’s win probability sat at 99.7% before they collapsed in the death overs.
Frequently Asked Questions
How is win probability calculated? +
We use a logistic model on top of the required run rate vs the format baseline, wickets in hand, balls remaining and venue bias. Death-overs pressure and low wickets in hand are penalised. The model returns 0.5% to 99.5% and is calibrated for fan-level intuition — it is not a gambling tool.
What does the 'pressure index' mean? +
Pressure index combines how far ahead the required rate is of the format baseline with how late in the innings you are. 'Very High' means you need to clear the boundary nearly every over with few mistakes; 'Low' means you can pace the chase comfortably.
Why are wickets in hand weighted so heavily? +
Empirical data shows the marginal value of a wicket is non-linear. Losing your 7th wicket has a bigger impact than losing your 2nd because batting depth thins out fast. The model uses a steep wickets curve and an extra penalty when 3 or fewer wickets remain.
What is the 'DLS-aware' mode? +
Switch DLS Mode to 'On' if the match was reduced by rain. Set the revised overs to the DLS revised total — the calculator then uses the revised balls remaining for all internal math, giving accurate probabilities for shortened chases. Pair with the DLS Calculator to compute the revised target first.
Can I use this for first-innings situations? +
Yes — switch to the 'First-Innings Projection' tab. Enter Team 1's current position, your venue's par score, and a dew factor if relevant. The tool projects the likely final total and gives a snap probability for both sides.
What does the What-If Matrix show? +
It uses your current runs needed and shows win probability across a grid of wickets-in-hand (columns) and balls-remaining (rows). It is the fastest way to see at what point the chase becomes implausible.
How accurate is it compared to broadcast graphics? +
Broadcast win-probability models often include player-specific batting performance, ball-by-ball matchups and venue history — features that need proprietary data. Our model captures the dominant factors and tracks broadcasts well at the strategic level, but expect small differences ball-by-ball.
Can I share my scenario? +
Yes. Use the 'Copy Share Link' button — your inputs are encoded into the URL and the recipient gets the same scenario loaded automatically.
Does the venue bias matter much? +
It shifts the format baseline by ±0.5 runs per over and slightly biases the gauge. Useful when chasing in obvious bowler-friendly conditions or on a road.
What format coverage is included? +
T10 (10 overs), T20 (20 overs) and ODI (50 overs) — each with their own baseline run rate and phase definitions.
Score Your Next Match with the App
Ball-by-ball scoring, live stats, offline support, and instant sharing. Free to download on iOS and Android.
