Make sense of the chase.

Use 12.4 for 12 overs and four legal balls. That is 76 balls. An input ending in .6 is invalid: six legal balls complete the next over, so 12.6 must be entered as 13.0.

1. Enter the chasing side’s current runs.
2. Enter completed overs plus legal balls, excluding wides and no-balls from the ball count.
3. Enter the target required to win, including any target officially revised for the match.
4. Enter the innings length as overs and legal balls. Use the current shortened length if play has been reduced.

The tool validates the inputs and reports balls remaining. It does not fetch scores or change a target automatically. Check both against the match scorecard.

With 120 runs after 15 overs, a target of 181 and a 20-over innings, 90 balls have been faced and 30 remain. The current rate is 120 × 6 ÷ 90 = 8.00. The side needs 61 runs, giving a required rate of 61 × 6 ÷ 30 = 12.20.

The target is 181 because reaching 180 would only equal an unchanged opponent’s 180. This is a hypothetical example, not a current match, prediction or suggested fantasy selection.

At zero legal balls, current run rate has no denominator, so it is shown as unavailable. If the target is reached, required rate is zero. If there are no balls left and the target has not been reached, there is no remaining-ball rate to calculate.

Wickets, a declared innings, a tie-break, penalties and a result decision are outside this arithmetic. If a revised DLS target is in use, enter the target published by the match source. Read why run rate cannot produce a DLS target.