Reading a cricket scorecard like a pro

A cricket scorecard looks like a wall of numbers, but every column is answering a specific question. Once you know which question each one answers, you can reconstruct the shape of a match you never watched. Here is how to read one from the top down.

Start with the batting table

The batting table lists each batter, how they got out, their runs, and the balls they faced. Two numbers matter most: runs and balls faced. From those you get strike rate, printed as runs per 100 balls.

Strike rate 150 means the batter scored 150 runs for every 100 balls. In a T20 that is aggressive and valuable.
Strike rate 60 in a T20 usually means the batter was stuck and cost the team momentum, even if the run total looks respectable.
In a Test match, a strike rate of 45 can be exactly what the team needed: someone occupying the crease and tiring the bowlers.

So context sets the meaning. The same strike rate is a hero in one format and a liability in another. Always ask what the format and match situation demanded before you judge a batter's line.

The dismissal column is the second story. c Smith b Bumrah means caught by Smith off Bumrah's bowling. lbw b Ashwin means leg before wicket to Ashwin. not out means the batter was still there at the end. A row of run out entries points to a team that panicked between the wickets, not a bowling attack that earned its wickets.

The extras line is not noise

Extras are runs the batting side got without a batter hitting them: wides, no-balls, byes, and leg-byes. A high extras count (say, 20 or more in a limited-overs innings) tells you the bowling side leaked runs through poor discipline. If a team lost by 15 and conceded 22 in extras, the scorecard is telling you where the match slipped away.

Move to the bowling table

The bowling table shows overs, maidens, runs conceded, and wickets, usually written as 4-0-32-2 (four overs, zero maidens, 32 runs, 2 wickets). The derived number is economy rate: runs conceded per over.

Economy under 6 in a T20 is excellent; the bowler choked the scoring.
A maiden (an over with no runs) is pressure made visible. A bowler with two maidens forced the batters to take risks later, which often shows up as a wicket for a teammate an over or two afterward.

Read the bowling and batting tables together. A batter with a low strike rate next to a bowler with several maidens is the same event seen from both ends: someone bowled tight, someone got bogged down.

The fall-of-wickets line tells the plot

Near the bottom you will find fall of wickets, written like 1-45 (Rohit, 6.2). This means the first wicket fell at 45 runs, it was Rohit, and it happened in the 6.2nd over. String these together and you get the narrative:

1-12, 2-15, 3-19 early on means a top-order collapse. Three wickets for almost no runs.
A long gap such as 2-40 then 3-180 means a huge partnership rebuilt the innings between the second and third wickets.
Wickets tumbling in the last few overs (7-150, 8-152, 9-155) is a death-overs collapse, usually batters swinging for the boundary and missing.

The fall-of-wickets line is the closest thing a scorecard has to a timeline. Read it and you can feel where the pressure moved.

Put it together on one innings

Say a T20 innings reads 178/6. The scorecard shows an opener at 82 off 50 (strike rate 164), the middle order all under 20, extras at 14, and fall of wickets clustered between overs 15 and 19. You now know the story without a single replay: one batter carried the innings, the middle order failed, the bowling side gave away too many extras, and the end was a scramble. That is a team that is one injury away from trouble, because it depends on a single player.

A short checklist

Next time a scorecard is in front of you, run these four passes in order:

Top scorer and their strike rate — who set the tempo, and was it fast or slow for the format?
Extras — did the bowling side donate runs?
Best bowling figures and maidens — who applied pressure?
Fall of wickets — when did the match turn?

Four passes, maybe thirty seconds, and a static table becomes a match report. The numbers were always telling you the story. Now you can hear it.