A practical guide to cricket scorecards: totals, legal-ball overs, wickets, extras, rates, innings, multi-day context and rain-revised match targets.
Begin with the match status before the figures
A scorecard records each innings and places it within a match. First identify the teams, format and displayed status, then read the innings totals. A line such as 164/6 does not automatically mean an innings has ended: it says the batting side has 164 runs and six wickets down. The overs, target or result status supplies the missing context.
In a limited-overs match, an innings can finish because its overs are used, all applicable wickets have fallen, or a chase reaches its target. In multi-day cricket, innings sequence and time remaining matter too. On a FairPlay cricket page, treat the scorecard as a structured record and use the stated status rather than inferring a result from one total.
Read runs and wickets together in the team total
The number before the slash is the team's runs; the number after it is wickets, meaning dismissals that have ended batters' innings. Wickets are not deducted from runs. A team can score quickly while losing few wickets, or lose many wickets for a modest total. Read both numbers alongside the over count, batting card and extras.
Worked example, fictional and educational: 164/6 after 20.0 overs means 164 runs, six wickets down and 20 completed overs. The run rate is 164 divided by 20, or 8.20 runs per over. This describes that completed fictional innings; it is neither a live total nor a prediction.
Treat over notation as legal balls, not decimals
The dot in an over figure is not a decimal point. The whole number is completed overs and the digit after the dot is legal balls into the next over. Each completed over has six legal deliveries, so 12.4 means 12 overs and four balls, not twelve point four tenths of an over. The next legal ball changes 12.5 to 13.0, never 12.6.
Convert to balls before calculating a rate from a partial over. Twelve overs and four balls is 12 times 6 plus 4, or 76 legal balls. Wides and no balls add runs but do not consume a legal ball, so an over may contain more than six actual deliveries.
| Notation | Calculation | Meaning |
|---|---|---|
| 3.0 | 3 × 6 = 18 | Three completed overs |
| 3.2 | 3 × 6 + 2 = 20 | Three overs and two legal balls |
| 12.4 | 12 × 6 + 4 = 76 | Twelve overs and four legal balls |
Follow the batting card from runs to strike rate
A batting line commonly lists runs, balls faced, boundary counts and strike rate when supplied. A batter recorded as 47 from 39 made 47 runs from 39 balls faced. Dismissal wording tells how that batter's innings ended; not out means it had not ended when the team innings closed. The order of names shows batting appearances, not necessarily who faced a particular live delivery.
Strike rate is runs divided by balls faced, multiplied by 100. Worked example, fictional and educational: 47 divided by 39 times 100 equals 120.51, rounded to two decimal places. It is a scoring rate, not the batter's share of the total or a conclusion about performance without match context. Boundaries help explain an innings, but running and extras also affect the team score.
- R: the batter's runs.
- B: balls faced, where shown.
- 4s and 6s: boundary counts, where shown.
- SR: strike rate from runs and balls faced.
Account for extras and interpret dismissals carefully
The team total is not only the sum of batters' credited runs. Extras are runs added to the batting side but recorded separately. A scorecard may break them into byes, leg byes, wides, no balls and penalty runs, although the source API does not necessarily deliver every optional field for every match.
Wides are extras rather than batter runs. A no-ball penalty is an extra; runs hit from the bat on a no ball can be credited to the striker. Both require another legal delivery. Dismissal text identifies the recorded event. A run out is a team wicket, but it is not credited as a wicket to the bowler.
| Component | Runs | Check |
|---|---|---|
| Batters' credited runs | 143 | Batting-card total |
| Extras | 21 | Recorded separately |
| Team total | 164 | 143 + 21 = 164 |
Understand bowling figures and economy rate
Bowling figures commonly summarise overs, maidens, runs conceded, wickets and economy rate. A maiden is an over in which no runs are conceded. The wickets figure is dismissals credited to that bowler, which is why it may differ from the team's wicket total when, for example, there is a run out. Supplementary columns such as wides may be absent.
Economy is runs conceded divided by legal overs bowled. Worked example, fictional and educational: 3.2 overs is 20 legal balls, which is 20 divided by 6 or 3.333 recurring overs. A bowler conceding 28 runs therefore has an economy rate of 28 divided by 3.333 recurring, or 8.40. Do not divide by 3.2 as a decimal.
Place each innings in its multi-day order
An innings is a team's turn to bat. Limited-overs matches normally give each side one innings, while multi-day cricket can give teams more than one. First innings and second innings labels identify match sequence, so compare aggregates as well as the latest score. A first-innings lead is not necessarily a final winning margin.
Worked example, fictional and educational: Meadow makes 280 and Harbour makes 325, leaving Harbour 45 ahead after both first innings. Meadow then makes 210, for an aggregate of 490. Harbour begins its next innings on 325 and needs 166 more runs to pass 490, because the target is one more than the opponent's aggregate. Check the stated target and result rather than adding innings casually.
Read targets, draws and rain changes in their proper context
A chase must reach its target, not merely match the opponent's preceding total. Worked example, fictional and educational: with a target of 166, a side on 165 is one run short; 166 reaches the required score. For a completed game, use the scorecard's declared result or the FairPlay cricket results page rather than trying to settle the outcome from partial figures.
A draw in a multi-day match means scheduled time ended without a result under the match conditions; it is not automatically a tie. Rain can reduce available overs and create a revised target under the applicable competition method and rules. Worked example, fictional and educational: a chase revised to 112 from 12 overs falls one run short at 111/5 after 12.0. Read the official displayed target and result; this guide does not calculate rain adjustments.
For current play, Fairplay live scores can provide the displayed innings and status. The available source API data can vary by match and stage. If a fall-of-wickets list, toss, delivery feed or another optional field is not displayed, do not estimate it from the remaining columns. For rules on scoring, deliveries and dismissals, consult the MCC Laws of Cricket.
Questions, answered
Why is 10.3 overs not 10.3 decimal overs?
It means ten completed overs plus three legal balls, or 63 balls. Decimal treatment would produce wrong ball and rate calculations.
Do extras count in the team total?
Yes. They are added to the batting side's total but recorded separately from a batter's credited runs.
Can I calculate a rain-revised target from the original score alone?
No. Use the displayed revised target and official result, because the applicable method and match conditions matter.
Why can team wickets exceed bowlers' credited wickets?
Some dismissals, including a run out, are team wickets without being credited to a bowler.
Sources and evidence
- MCC Laws of Cricket
Reference for legal deliveries, scoring and dismissals.
- How FairPlay works
Product context for FairPlay score presentation.
- FairPlay cricket score source API
Data availability can vary by match; optional fields are not assumed.
Scheduled facts and sourced history are separate from live match data. Source attribution does not imply affiliation with IPL, BCCI, ICC or players.