How to Read a Cricket Scorecard Like a Pro
A cricket scorecard is more than just numbers on a page. It's the definitive record of a match, and if you know how to read it, it tells you the complete story. Who dominated. Where the momentum shifted. How the match was won or lost. I often say that a good scorecard reader can reconstruct an entire match without having watched a single ball. Let me show you how.
The Match Header
Every scorecard starts with the basics: the two teams, the venue, the date, the format (T20, ODI, Test, or a custom format), who won the toss, and the final result.
Pay attention to that result line. It tells you a lot. "Won by 45 runs" means the team batting first posted a total the opposition couldn't chase. "Won by 6 wickets" means the chasing team got there with 6 wickets still in hand. Already, before you've looked at a single batting or bowling figure, you know the shape of the contest.
The Batting Card
This is the heart of the scorecard. Each innings has a batting card listing every batsman who came to the crease. Here's what you're looking at:
| Column | Meaning | Example |
|---|---|---|
| Batsman | Player name | Virat Kohli |
| Dismissal | How they got out | c Smith b Anderson |
| R | Runs scored | 82 |
| B | Balls faced | 56 |
| 4s | Number of fours hit | 9 |
| 6s | Number of sixes hit | 3 |
| SR | Strike rate (runs per 100 balls) | 146.43 |
Reading the Dismissal
The dismissal column uses shorthand notation, and once you learn it, you'll read it as naturally as you read the score. Let me decode the common ones for you.
b Anderson means bowled by Anderson. The ball hit the stumps. Clean and simple. c Smith b Anderson means caught by Smith off Anderson's bowling. The bowler created the chance, the fielder took it. lbw b Anderson is Leg Before Wicket off Anderson. The ball would have hit the stumps, but the batsman's pad was in the way.
run out (Smith) means the batsman was run out, with Smith involved in the fielding. st Dhoni b Jadeja means stumped by wicketkeeper Dhoni off Jadeja's bowling. not out means the batsman was still at the crease when the innings ended. And retired hurt means they left the field due to injury.
The key thing to notice: the bowler gets credited for bowled, caught, LBW, stumped, and hit-wicket dismissals. Run outs don't count against the bowler. Keep that in mind when you're evaluating bowling figures.
Strike Rate
How fast was a batsman scoring? That's what strike rate tells you.
Strike Rate = (Runs / Balls Faced) × 100
A strike rate of 150 means the batsman was scoring 1.5 runs per ball. That's aggressive, fearless cricket. A strike rate of 50 means they were playing cautiously, occupying the crease. Neither is inherently better. It depends on the situation. In T20 cricket, you want 130+. In Test cricket, 50 or 60 is perfectly respectable.
The Extras Line
Below the batting card, you'll spot something like this:
Extras: 12 (b 2, lb 3, w 5, nb 2)
That tells you 12 extra runs were given away: 2 byes, 3 leg byes, 5 wides, and 2 no-balls. These runs count toward the team total but no batsman gets credit for them. In a tight match, that extras line can be the difference between winning and losing.
The Innings Total
After the batting card and extras comes the summary:
Total: 186/7 (20 overs) · Run Rate: 9.30
That reads as 186 runs scored for the loss of 7 wickets in 20 overs, at a run rate of 9.30 per over. If it says "186 all out", all 10 wickets fell. Simple as that.
The Bowling Card
Now flip to the other side of the contest. The bowling analysis shows how each bowler performed:
| Column | Meaning | Example |
|---|---|---|
| Bowler | Player name | Jasprit Bumrah |
| O | Overs bowled | 4 |
| M | Maiden overs (no runs conceded) | 1 |
| R | Runs conceded | 24 |
| W | Wickets taken | 3 |
| Econ | Economy rate (runs per over) | 6.00 |
Economy Rate
Economy rate tells you how expensive a bowler was. Think of it as the bowling equivalent of strike rate.
Economy = Runs Conceded / Overs Bowled
In T20 cricket, an economy under 7 is excellent. Under 5 in ODIs is impressive. Under 3 in Tests is tight, disciplined bowling. When you see figures like 4-1-24-3 (4 overs, 1 maiden, 24 runs, 3 wickets), you're looking at a bowler who had a genuinely outstanding spell.
What Counts Against the Bowler?
Here's something worth knowing. Not all extras are the bowler's fault. Wides and no-balls count against their economy, but byes and leg byes do not. So when you see a bowler with an economy of 9, take a closer look. Some of those runs might be byes that slipped past the keeper. The bowler did nothing wrong on those deliveries.
Fall of Wickets
This is my favourite section of any scorecard. It's where you find the narrative.
FOW: 1-23 (Sharma, 3.2), 2-45 (Rahul, 6.1), 3-48 (Kohli, 7.0)
The 1st wicket fell at 23 runs (Sharma out in over 3.2). The 2nd at 45 (Rahul out in over 6.1). The 3rd at just 48 (Kohli out in over 7.0). Now read between the lines. The team went from 45/1 to 48/3. Two wickets fell in barely 5 balls. That's a collapse. That's panic in the dressing room. That's momentum swinging violently. A long gap between wickets, on the other hand, tells you a partnership was building, that the batsmen were in control.
Partnerships
Some scorecards include partnership data, and I wish more of them did:
3rd wicket: Kohli & Pant, 87 runs, 62 balls
Partnerships give you context that individual scores can't. A batsman's 40 looks very different if they were part of a 120-run stand compared to walking in at 48/3 and steadying a sinking ship. Context is everything in cricket.
Reading the Story
A great scorecard reader doesn't just look at numbers. They reconstruct the match. Here's how I do it.
Start with the match-winner. Look for the highest score in the batting card and the best bowling figures. But don't stop there. A 35 off 18 balls in a tight chase can be more valuable than a casual 70 in a dead match. Context always matters.
Then look for momentum shifts. The fall of wickets is your friend here. Quick wickets in clusters signal collapses. Long gaps signal dominance. You can almost feel the tension rising just by reading those numbers.
Check the extras. Did the bowling side give away 15+ extras in a T20? That's practically gifting runs. And look at who bowled at the death, the last few overs. Their economy rate tells you whether they held their nerve or crumbled under pressure. Death bowling is where matches are decided, and the scorecard tells you exactly who stepped up.
Finally, was the chase comfortable? Won by 7 wickets with overs to spare? Dominant. Won by 1 wicket off the last ball? You missed a thriller.
Common Scorecard Formats
Scorecards come in different levels of detail. A summary gives you just the final score: "India 186/7 beat Australia 172 all out." A standard scorecard includes the batting card, bowling card, extras, and fall of wickets. And a detailed scorecard gives you everything: partnerships, over-by-over progression, ball-by-ball data.
Modern scoring apps like Skipper Cricket generate detailed scorecards automatically from ball-by-ball data. Your local Saturday match gets the same rich, detailed record that an international game does. That's the beauty of digital scoring.
Wrapping Up
The batting card tells you who performed. The bowling card tells you who controlled the game. The fall of wickets reveals the narrative, the twists and turns. And extras? They can quietly swing the outcome when nobody's paying attention.
But here's the thing. Numbers alone never tell the full story. You need context. A scorecard is like a photograph of a match, and once you learn to read it properly, you'll start seeing things that casual fans miss. Keep reading scorecards, keep asking questions, and I promise the patterns will become second nature.