A cricket scorecard is a compact record of what happened in an innings, but its abbreviations can be unfamiliar at first. This guide explains how to read runs, overs, wickets, extras, batting and bowling figures, run rate, required rate, partnerships, and revised targets so you can follow a live match and judge what each team needs next.
Overview
Start with the innings summary. A score such as 248/6 in 40 overs means the batting team has scored 248 runs and lost six wickets. The number after the slash is wickets lost, not overs remaining. In a limited-overs match, the scorecard will also show the maximum overs available and, during a chase, the target set by the first innings.
Cricket scores are built from three basic elements:
- Runs: The total number of runs scored by the batting team.
- Wickets: The number of batters dismissed.
- Overs: The number of legal deliveries completed by the bowling side.
These figures should be read together. A team at 120/2 may be in a different position from a team at 120/6, even if both have faced the same number of overs. Likewise, 120 runs from 20 overs represents a different scoring pace from 120 runs from 30 overs.
| Scorecard term | What it means | Why it matters |
|---|---|---|
| Runs | Total team score | Measures the result of the batting innings so far |
| Wickets | Batters dismissed | Shows remaining batting resources and match pressure |
| Overs | Completed sets of six legal balls | Provides the time or delivery context for the score |
| Extras | Runs not credited to a batter | Separates individual batting output from team scoring |
| Run rate | Runs scored per completed over | Describes the current scoring pace |
| Required rate | Runs needed per remaining over | Describes the pace needed by a team chasing a target |
| Partnership | Runs added by two batters between wickets | Shows how a pair has shaped the innings |
What to track
Batting figures
A batting table usually lists each batter's name, runs, balls faced, fours, sixes, and strike rate. A batter's strike rate is calculated as runs divided by balls faced, multiplied by 100. It describes scoring speed, not the quality of an innings by itself. For example, a batter who scores 30 from 20 balls has contributed at a faster rate than one who makes 30 from 40 balls, but the match situation determines whether that difference is valuable.
Dismissal notes explain how a batter was out, such as caught, bowled, leg before wicket, run out, or stumped. A batter marked not out remains at the crease when the innings ends or when the scorecard is updated between wickets.
Bowling figures
Bowling figures commonly show overs, maidens, runs conceded, wickets, and economy rate. A bowler listed with 4-0-28-2 has bowled four overs, delivered no maiden overs, conceded 28 runs, and taken two wickets. The exact display varies by score provider, so check the column headings before interpreting the sequence.
Economy rate is the average number of runs conceded per over. It should be considered alongside wickets, pitch conditions, innings phase, and the quality of batters faced. A bowler can have a modest economy rate but no wickets, while another may concede more runs and remove key batters.
Extras and overs
Extras are team runs that are not credited to the batter. Common categories include wides, no-balls, byes, and leg byes. A wide or no-ball generally adds to the batting team's total and may also provide an additional delivery under the laws and competition rules. Byes and leg byes count toward the team score but not the batter's runs. Because terminology and penalty details can vary by format or playing conditions, use the competition's official rules when a precise ruling matters.
Overs are written in cricket notation. 12.4 overs means 12 completed overs plus four legal balls; it does not mean 12.4 decimal overs. Since one over contains six legal balls, 12.4 overs represents 76 legal deliveries. This distinction matters when calculating run rate or required rate.
Partnerships and fall of wickets
The partnership section records how many runs two batters added before one was dismissed. A large partnership can explain a team's recovery after early wickets, while a short partnership may indicate sustained pressure from the bowling side. The fall-of-wickets list adds context by showing the score and sometimes the over at which each wicket fell.
Cadence and checkpoints
For a quick live-match reading, use the scorecard at four checkpoints:
- After the powerplay or opening phase: Check the score, wickets lost, and whether the opening batters have established a platform.
- At the halfway point: Compare the current run rate with the pace needed for a competitive total or successful chase.
- After a wicket or partnership change: Reassess which batters remain, who is set, and whether the new batter may need time to settle.
- At the final scheduled overs: Compare the target, runs remaining, balls remaining, wickets in hand, and likely scoring options.
The basic current run-rate formula is:
Current run rate = total runs ÷ completed overs
For example, 150 runs after 25 overs gives a current rate of 6.00 runs per over. Do not divide by the displayed figure as though overs were decimals when the scorecard shows part of an over. Convert completed overs and legal balls into a consistent form first.
In a chase, the required rate is usually calculated as:
Required rate = runs still needed ÷ overs remaining
If a team needs 96 runs from 12 overs, it requires 8.00 runs per over. This is a guide, not a prediction. Wickets in hand, batting depth, boundary sizes, weather, bowling matchups, and the quality of the current batters can all change the practical difficulty.
How to interpret changes
Read the scorecard as a sequence rather than focusing on the total alone. A team moving from 60/0 to 110/1 may have controlled the innings, while a team moving from 60/4 to 110/5 may have recovered from a difficult start. The same score can carry a different meaning depending on wickets and the phase of play.
Next, compare current rate with required rate. If the chasing side's current rate is above the required rate, it may have built a cushion, but a late cluster of wickets can quickly remove that advantage. If the current rate is below the required rate, the deficit may still be manageable when wickets are available and the required rate is stable. A rising required rate often signals that the chase is becoming more demanding, especially when new batters are arriving at the crease.
Give particular attention to the most recent overs. A scorecard with a strong overall run rate can hide a recent slowdown, just as a low overall rate can conceal a late acceleration. Review the over-by-over summary, boundaries, extras, wickets, and bowling changes where available.
For a revised target, look for an explicit note about rain, an interruption, or a changed number of overs. In limited-overs matches, the Duckworth-Lewis-Stern method may be used to set a revised target based on resources available to each team. The exact calculation is competition-specific and should be treated as an official target rather than recreated from the basic run-rate formula. When DLS is applied, check the updated target, overs remaining, and any revised par score shown by the score provider.
A worked reading
Suppose a team is 172/4 after 30 overs in a 50-over innings. Its current run rate is 5.73 runs per over. It has 20 overs remaining, but the useful question is not simply whether it can maintain 5.73. Check which batters are set, how many recognized batters remain, whether the opposition still has its strongest bowlers available, and whether extras or wickets have changed the innings pattern. A later score of 250/8 after 45 overs would show that the team added 78 runs but lost four wickets in 15 overs, a very different phase from the first 30 overs.
When to revisit
Return to the scorecard after every major innings update, wicket, bowling change, or interruption. During a chase, refresh it whenever the required rate changes materially or a new batter arrives. At the end of an innings, compare the final total with the innings progression: opening partnership, middle-over scoring, wickets lost, extras, and final-over acceleration.
For a recurring match-analysis habit, record the same checkpoints each time: score and wickets at the halfway point, current run rate, required rate when the chase begins, largest partnerships, and the overs in which wickets fell. This creates a consistent record without treating one score as proof of a broader trend.
Revisit this guide before a new competition or format if its playing conditions, over limits, tie-break procedures, or rain-related target rules differ. For broader match context, pair the scorecard with a match preview using team news, form, and head-to-head stats. The scorecard tells you what has happened; those surrounding details help explain why the match may be moving in a particular direction.
When checking a live cricket score, follow this order: read the team total, confirm wickets and overs, inspect the current batters, review extras and partnerships, calculate the current or required rate, then check for interruptions or revised targets. That simple routine turns a row of numbers into a clear picture of the match.
