Home / Blog / Cricket

How to read a cricket scorecard

Understand runs, wickets, overs and individual figures through a worked cricket scorecard example.

By ScoreZaap · · 3 min read

Read the headline in order

In a hypothetical score of 156/4 after 18.2 overs, 156 is the team total, four wickets have fallen, and two valid balls have been bowled after 18 completed overs. The total includes batter runs and extras. It is not the personal score of one player.

Check the innings, match format and target before deciding who is ahead. The same total can describe very different situations. A chase with few balls left needs a different reading from an innings that still has plenty of time.

Separate batting from bowling

A batting row commonly lists runs, balls faced, fours, sixes and strike rate. Runs measure output; balls describe the recorded opportunity used. A star commonly indicates not out, but check the interface labels because providers arrange scorecards differently.

A bowling row commonly gives overs, maidens, runs conceded and wickets. A run out can reduce the team's wickets remaining without giving a bowler a wicket. Team runs need not equal the sum of bowling runs because some extras are allocated separately.

Look for the innings story

Scan the fall of wickets and partnerships. A collapse followed by a recovery can reach the same total as steady batting, but the remaining resources differ. Total, overs, wickets and the current pair make a better quick summary than the total alone.

On ScoreZaap, start with the match headline and then open the scorecard for detail. If a number changes, check the delivery outcome and innings label before assuming a problem. Live scoring can be corrected. Every number in this guide is a teaching example, not a report of a real fixture.

Reading a chase: CRR and required rate

In a one-day chase, two rates sit next to the score. Current run rate (CRR) is the batting side's scoring speed so far: runs divided by overs faced. Required run rate is the speed still needed: runs remaining divided by balls remaining, expressed per over. If the required rate stays above the current rate for long, the chase is slipping; if it drops below, the batting side is ahead of the asking rate.

A hypothetical 140/2 after 25 overs chasing 280 needs 140 more from 25 overs: required 5.6, current 5.6, an even game. On ScoreZaap, the live match page shows the current run rate beside the score during a chase.

Reading a Test scorecard

A Test scorecard lists up to four innings in order. Labels like "trail by 152 runs" compare a side's running total with the opponent's completed innings; "lead by" is the same comparison in the other direction. Day and session labels (Day 3: 1st Session) describe play, not the result. A side can bat twice in a row only through the follow-on, and an innings can end early through a declaration - both have their own guides.

Common questions

Why does 18.2 overs not mean 18.5? The number after the dot counts legal balls in the current over, not tenths. Why did a number change after I read it? Live scoring is corrected routinely; check the delivery outcome and innings label before assuming an error. Where do net run rate and rankings fit? They matter in league tables, not a single match, and live on ScoreZaap's rankings pages.

Follow live scores on ScoreZaap →