How to read a cricket scorecard
Understand runs, wickets, overs and individual figures through a worked cricket scorecard example.
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.