How to read a cricket scorecard

A cricket scorecard is a compact accounting system. Reading it in the right order lets you understand the result without mistaking a team total for a batter's score, or an over display for a decimal number. The examples below are illustrative, not reports of real matches.

Start with the result, format and innings

In a limited-overs match, 168/6 means 168 team runs for six wickets. It does not tell you whether that was a winning score. Look at the opponent's innings and the result line. If the other side finished 165/9 chasing 169, the first side won by three runs. If a chasing side reaches 169/4 with six wickets still available, the usual result is a six-wicket win.

In a two-innings match, read all innings before assessing a lead. A team can score fewer runs in its second innings and still win because of its first-innings advantage. Follow-ons, declarations and forfeitures also change the order and shape of the match. Our follow-on calculator explains one of those situations.

Decode the overs before calculating a rate

An innings shown as 19.4 overs has used 19 complete overs plus four legal balls. With six balls per over, that is 118 balls, or 19.6667 overs. A total of 165 from that position gives 165 × 6 ÷ 118 = 8.39 runs per over. Dividing by the display value 19.4 produces 8.51 and is incorrect.

Wides and no-balls do not count among the six valid balls in an over. They can therefore increase the score without moving the legal-ball display. A long over in the commentary is not necessarily a broken scorecard. MCC's Law 17, The over explains which deliveries count.

Read the batting rows

Runs and balls faced answer different questions. A batter with 42 from 30 has a strike rate of 140: 42 divided by 30, multiplied by 100. Fours and sixes show boundary contributions, but the remaining runs can come from singles, twos and other completed runs.

The dismissal text explains whether and how the innings ended. An asterisk normally means not out. “Did not bat” is different from a zero: the player never had a batting innings. This distinction matters in career averages and in minimum-innings filters.

Read the bowling rows

A line of 4–0–28–2 usually means four overs, no maidens, 28 runs conceded and two wickets. Check the table headings rather than relying on position alone. The economy rate is seven runs per over. Bowling average is 14 runs per wicket for that spell, although one spell is too small a sample to describe a career.

Not every team wicket belongs to a bowler. Run-outs are the most common reason the bowling wicket total is lower than the innings wicket total. Byes and leg-byes also affect the team total without being charged to the bowler in the same way as runs off the bat.

Three useful cross-checks

• Add every batter's runs and the innings extras. They should reconcile to the team total.
• Compare the bowling legal balls with the innings legal-ball total, allowing for source limitations.
• Compare the fall of wickets, innings wickets and result. A missing innings or unexplained mismatch calls for a source check, not an invented explanation.

Try this on a recent scorecard, then consult data coverage if a field is missing. CricChase combines source scorecards with derived statistics; an empty field means unavailable information, not necessarily zero.

Sources and limits

MCC's scoring runs law explains the scoring framework. Individual competition playing conditions can modify how a match is conducted. This guide teaches scorecard interpretation; it does not replace an umpire's ruling or an official result.