Fair play cricket analysis starts by treating a scorecard as evidence: identify the innings, reconcile its numbers, and state only what its fields can support.
Read the scorecard as a record before making an interpretation
Fair play cricket analysis begins with the recorded innings line: team total, wickets, overs, batting runs, extras and bowling figures. Check that those fields fit together before interpreting them. Do not ask a short score snapshot to explain causes it cannot show.
Begin with the match label, format, innings label and timestamp when supplied. Then read the team line as one statement. A display such as 162/6 in 18.3 overs reports 162 team runs, six dismissed batters and 18 completed overs plus three valid balls.
For the live fixture identity and the freshness of supplied match information, use Fair play cricket analysis — current match context. This guide instead explains how to inspect the scorecard once a source provides one.
- Start with the innings line, not a single player row.
- Reconcile team runs with batting runs and extras before comparing individuals.
- Treat overs as completed overs plus legal balls, never as decimal notation.
- Separate a recorded number from context the scorecard does not supply.
Start with the innings line and map every section to a question
Read the team line, extras, batting table and bowling table in that order. The team score is the control total: a batting row is one player’s contribution, while extras also count in the innings total.
Providers may shorten or rearrange columns. BBC Sport’s scorecard explainer describes the usual fields: batting runs and balls faced; bowling overs, runs conceded, wickets and economy. Read the labels supplied rather than assuming every card is identical.
| Scorecard area | Ask this first | What it can establish |
|---|---|---|
| Innings line | Which side, runs, wickets and overs? | The recorded team position. |
| Extras | Which team runs were not batter runs? | Why total and batting sum differ. |
| Batting rows | Who scored, from how many balls, and was dismissed? | Individual contribution and balls faced. |
| Bowling rows | Which valid balls, runs conceded and wickets? | A bowler’s recorded figures. |
| Fall of wickets | At what score and over was each dismissal? | The listed dismissal score, not its cause. |
Use Fair Play Cricket Analysis to reconcile team runs, batting runs and extras
The basic check is: team total = batting runs + extras. Do it before describing a batter’s share. A batter can have 54 while the team has 162 because other batters and extras supplied the remainder.
MCC Law 18 distinguishes these components. Runs from a struck ball normally go to the striker; runs when it is not struck are the applicable extras, and the one-run no-ball penalty is a no-ball extra. It also debits the bowler with batter runs, no-ball extras and Wides, so bowling conceded runs and batting runs are not interchangeable.
Byes and leg byes add to team score but not batter runs; Wides and no-balls also add to it. MCC Law 22 says a Wide has a one-run penalty and resulting runs are Wides. Name the component being compared: batting runs, team runs or conceded runs.
If an extras total is absent, do not manufacture one by subtracting partial batting rows. A scorecard may omit rows, show a retired batter differently or have a display rule that needs its own label. Mark the reconciliation as unavailable until the full supplied fields allow it.
Read overs as valid balls, not decimal numbers
The dot in an overs figure separates completed overs from legal balls; it is not a decimal point. Thus 12.3 means 12 complete overs plus three legal balls: (12 × 6) + 3 = 75. It is not twelve-and-three-tenths overs. Convert it to 12.5 decimal overs only inside a calculation.
MCC Law 17 defines an over as six valid balls and excludes No balls and Wides from that count. A delivery can add runs without advancing the legal-ball total.
A displayed 18.3 is 111 legal balls: (18 × 6) + 3. That supports ball-based comparisons and rates, not a claim about the surface or reasons absent from the source. The `Fairplay cricket analysis` label is useful only when this boundary stays visible.
Compare batting and bowling figures in their own units
Batting strike rate is runs per 100 balls faced: (runs ÷ balls faced) × 100. Thus 54 from 39 balls is 138.46. It describes that row, not the whole innings. BBC Sport uses the same definition.
Bowling economy is runs conceded per over. First convert any partial over: 29 conceded in 3.4 overs means 22 legal balls, or 3.666… overs for arithmetic; 29 ÷ 3.666… = 7.91. Do not divide 29 by 3.4 as a decimal.
Keep the numerator and denominator in view. A batting strike rate is not a team run rate, and a bowler’s economy is not a batting strike rate turned upside down. The scorecard offers useful comparison only when the columns have the same unit, the same supplied format and a clearly stated sample.
Teaching example: reconcile a hypothetical innings
The following is a teaching example only. River XI, Harbour XI and every figure below are hypothetical, not a real fixture, record or current score.
Batting rows add to 143: 54 + 31 + 22 + 19 + 9 + 8. Extras add to 19: 3 byes + 4 leg byes + 5 no-balls + 7 wides. Therefore 143 + 19 = 162, matching 162/6. The 18.3 notation is 111 legal balls, or 18.50 decimal overs only for arithmetic; 162 ÷ 18.50 = 8.76 runs per over.
The 54 is 37.76% of 143 batting runs but 33.33% of 162 team runs. Both are correct, but they answer different questions. Always name the total used.
| Field | Shown or calculated | Method |
|---|---|---|
| Team line | 162/6 in 18.3 overs | The supplied innings total, wickets and legal-ball notation. |
| Batting runs | 143 | 54 + 31 + 22 + 19 + 9 + 8. |
| Extras | 19 | 3 byes + 4 leg byes + 5 no-balls + 7 wides. |
| Total check | 162 | 143 batting runs + 19 extras. |
| Legal balls | 111 | (18 completed overs × 6) + 3 balls. |
| Team rate | 8.76 runs per over | 162 ÷ (111 ÷ 6), rounded to two decimals. |
| Leading batter | 54 from 39; strike rate 138.46 | (54 ÷ 39) × 100, rounded to two decimals. |
| Example bowler | 29 in 3.4; economy 7.91 | 29 ÷ ((3 × 6 + 4) ÷ 6), rounded to two decimals. |
Keep unknowns, surfaces and small samples visible
A scorecard records events, not all conditions. Unless supplied, it cannot establish surface, weather, fitness, selection, field settings or reasons for an unseen delivery. It can show a run or wicket, not reliably explain why.
One batter’s 39 balls describe 39 balls, not a permanent skill level; one bowler’s 3.4 overs describe 22 legal balls, not a full-format record. For earlier matches, retain format, date range, source and innings count. Call a small sample a small sample.
Check source freshness before treating a score as current. A scorecard’s update time, match status and correction notices belong to that provider’s snapshot. MCC notes that competition playing regulations can create differences from the Laws, so use MCC’s Laws overview for the rule baseline and the competition’s own scorecard labels for the recorded event.
A repeatable method for a supplied scorecard
Use this short sequence for fair play analysis whenever a scorecard becomes available. It keeps the calculation visible and prevents a column from carrying more meaning than it can support.
When you need an innings-sequence lens after this basic check, the companion guide to innings phases addresses that separate topic. For a supplied live score, see the current score page; for defined records, see cricket statistics.
- Identify the match, format, innings and source timestamp shown on the card.
- Copy the team line exactly: runs, wickets and overs.
- Add full batting runs and extras separately; test whether they equal team runs.
- Convert any partial-over figure to legal balls before calculating an over-based rate.
- Name the unit for each comparison: team runs, batting runs, balls faced or runs conceded per over.
- Label absent conditions, incomplete rows and limited samples as unknown rather than filling them with an inference.
Questions, answered
What does 12.3 overs mean on a cricket scorecard?
It means 12 completed overs and three valid balls: 75 legal balls in total. It is not 12.3 decimal overs. Under MCC Law 17, an over contains six valid balls, while Wides and No balls do not count among those six.
Why can the team total be higher than the batters’ combined runs?
The difference is usually extras. Byes, leg byes, Wides and No balls can add to the team total without becoming batter runs. Check the scorecard’s extras line before treating the batting-runs sum as the team total.
How do I calculate batting strike rate from a scorecard?
Divide the batter’s runs by balls faced, then multiply by 100. For 54 from 39 balls, the calculation is 54 divided by 39 multiplied by 100, which equals 138.46 when rounded to two decimals.
How do I calculate a bowler’s economy from 3.4 overs?
Convert 3.4 to 22 legal balls first, which is 3.666 repeating overs for arithmetic. Then divide runs conceded by 3.666 repeating. If 29 runs were conceded, the economy is 7.91 when rounded to two decimals.
What can Fair Play Cricket Analysis say from one scorecard?
It can describe and check the numbers recorded in that innings, including totals, extras, legal balls and listed individual figures. It cannot establish conditions or reasons that the scorecard does not supply, and one short sample is not a complete player or team record.
Sources and evidence
- MCC — Law 17: The Over
Official source for six valid balls in an over and deliveries that do not count. Checked 2026-10-19.
- MCC — Law 18: Scoring Runs
Official source for crediting batter runs, extras and bowler debits. Checked 2026-10-19.
- MCC — Law 22: Wide Ball
Official source for Wide penalties, attribution and the fact that a Wide does not count in the over. Checked 2026-10-19.
- BBC Sport — How do you read a cricket scorecard?
Reader-facing definitions of common batting and bowling columns; published 2026-06-13.
- MCC — About the Laws of Cricket
MCC’s Laws overview, including its role as custodian and the distinction between Laws and competition playing regulations. Checked 2026-10-19.
Scheduled facts and sourced history are separate from live match data. Source attribution does not imply affiliation with IPL, BCCI, ICC or players.