Read a cricket scorecard by separating the team’s runs, wickets lost and progress through the innings. Then identify the match format and whether the side is setting a total or chasing one. The same score can describe different situations under different playing conditions.
MCC’s 2026 Laws define an over around six valid balls. Overs notation is not a decimal: the digit after the dot records valid balls in the incomplete over.
Read the overs notation as completed overs plus the valid balls in the next over. For the example below, 12.4 means twelve complete overs and four further valid balls. Writing that out once helps connect the display with the ball count used in a calculation.
Decode one fictional score
Suppose a display shows 84/3 after 12.4 overs. In this invented example, the team has scored 84 runs and lost three wickets. Twelve complete overs plus four valid balls makes 12 × 6 + 4 = 76 valid balls.
The calculation uses twelve complete overs plus four valid balls: 12 × 6 + 4. Wides and no-balls are not valid balls for completing the over, so the number of deliveries bowled can exceed this count.
Give each part a question
| Scorecard part | Question |
|---|---|
| Team total | How many runs have been recorded? |
| Wickets | How many dismissals are recorded? |
| Overs | How far has this innings progressed? |
| Batter entries | Who is contributing to the total? |
| Extras | Which runs are not credited to a batter? |
The last two fields add detail; start with the team situation before trying to interpret every abbreviation.
Add the format before judging the score
Look up the competition’s innings limits and playing conditions. Target calculations, interruptions and match results also need the applicable playing conditions and fuller match information. To practise, write three invented over notations and convert them into valid balls. Once that is comfortable, add the runs and wickets and explain the situation in an ordinary sentence.
Calculate a rate from the same example
The fictional score of 84 after 12.4 overs represents 76 valid balls. At six valid balls per over, that is 76 / 6 overs for the rate calculation. The average is therefore 84 / (76 / 6), or about 6.63 runs per over.
The display remains 12.4 overs; the decimal quantity is used only in the calculation. Keeping the ball count between the display and the arithmetic makes the conversion easier to follow.
Read a fictional chase in context
Suppose a teaching example states that a side needs 30 more runs from 24 valid balls. That is four six-ball overs, giving a required average of 7.5 runs per over. The target and remaining balls are explicit assumptions of the exercise, not a method for deriving an interrupted match’s target.
Read wickets lost alongside that requirement and establish the match format. A basic scorecard can then answer separate questions: how many runs have been recorded, how much of the innings has been used and what the stated chase requires.
For a real match, use the competition’s official score and playing conditions for targets, interruptions and results. If commentary supplies an adjusted target, retain that as a separate stated input rather than inferring it from the ordinary runs-and-overs example.
The invented 84-run example covers 76 valid balls, giving about 1.11 runs per valid ball. Keep the score, ball count and calculation together. Interpreting the team’s wider position then draws on the match format and the rest of the innings information.
Sources consulted
- Laws of Cricket: 2017 Code, 4th Edition 2026 — MCC; consulted 3 November 2026.