Cricket: rules, formats and the right sources

Read runs, wickets and overs together

Extras and deliveries that do not count as legal balls can explain why a simple ball count differs from what you expected. A team's score can show runs alongside wickets lost. The overs figure describes progress through the innings rather than another run total. For example, an overs notation ending in .3 represents three legal deliveries into an over, not a decimal fraction of the match.

Worked example with invented numbers: a side chasing 161 is 145/6 after 18.3 overs in an unreduced T20 innings. It has scored 145 runs, lost six wickets and faced 111 legal balls. It needs 16 more runs from nine legal balls. Four wickets remain available under the ordinary ten-wicket innings structure, but the chase can finish before all nine balls are used if the target is reached or the innings ends.

Read the slash as runs/wickets, not runs per over. A wide or no-ball can add runs without consuming a legal delivery, so do not count commentary events as though each must advance 18.3 to 18.4. The scorecard’s extras, dismissal and ball labels explain what changed. This example assumes ordinary conditions and does not reconstruct a real match.

1. Identify the chasing side, innings, target and current score together.
2. Convert the overs notation into legal balls before dividing or subtracting.
3. Calculate runs and balls remaining, then label current and required rates separately.
4. Recheck the official target and match status after an interruption before reusing the result.

Identify the format and the stage

A Test match, a one-day match and a T20 match have different structures and playing conditions. Before interpreting a required run rate or a remaining-overs graphic, check the format, innings and competition. Rain, revised targets or a shortened match can change the context, so a stale score image should not be treated as a current match record.

A normal T20 innings has a maximum of 20 overs and an ODI innings normally 50, subject to the applicable conditions. Test cricket is scheduled across days and can have two innings per side; a single “required rate” graphic does not summarise that whole match. An innings can finish early through a completed chase, wickets or other conditions, so a maximum is not a promise that all scheduled overs will be bowled.

If rain changes the chase above, the result “16 from nine” remains an explanation of the old inputs only. Locate the announced revised target and remaining allocation before recalculating. Do not create a DLS target by scaling runs in direct proportion to overs: wickets and resources matter, and the official revision must be attributed to the match source.

Use primary rules for a disputed point

Check the edition and format rather than relying on an undated social-media explanation of a dismissal or target calculation. The MCC Laws of Cricket provide the fundamental laws. The ICC publishes playing conditions for its international formats. Competition-specific documents can add the operational detail needed for a particular tournament.

For a disputed no-ball, dismissal or interrupted finish, first write the question precisely: which delivery, which innings and which competition edition? Consult the MCC law for the underlying rule, then the competition’s playing conditions for modifications and procedures. A social clip may omit the umpire’s call or the relevant replay; retain the exact event rather than arguing from a cropped score.

A useful resolved note names the rule edition, describes the relevant event and states what the rule answers. If the event itself is unavailable, the remaining uncertainty is the event evidence, not a reason to invent an umpiring conclusion. For run-rate arithmetic, the worked numbers on this page are sufficient; a disputed official target requires the competition’s announcement.

Keep sports information separate from app claims

Statistics and commentary can be displayed by an app that has no role in organising the competition. Establish its publisher and the scope of the current product separately. This guide helps readers interpret cricket information in India; it supplies neither a live score nor a forecast or prize-bearing selection.

Choose the next page by the question you still have. The Cricbuzz live-score guide covers the selected match, innings, commentary and update state. The Cricbuzz statistics guide separates batting strike rate, average and team standings. Neither a scorecard nor a rate calculation predicts the next delivery.

For app identity or an account task, start from the documented product owner. The Dream11 review separates the Sporta product from similarly named COME records. A complete rules explanation does not establish access to a contest, a payment method or a streaming right.

Read the decimal-looking over notation correctly

Overs use a delivery count after the point: 18.3 means eighteen completed overs followed by three legal deliveries. It is not the decimal value 18.3 overs. Read the innings and format alongside it. The notation here is an explanatory example, rather than a current score or selection recommendation.

The calculation must pass through balls: 18.3 means 18 + 3/6 = 18.5 mathematical overs. Dividing 145 by the decimal-looking 18.3 would give about 7.92, which is the wrong denominator. Dividing by 18.5 gives the same approximately 7.84 as 145 × 6 ÷ 111.

For the remaining nine balls, the mathematical duration is 1.5 overs, while a scorecard can express it as 1.3 in delivery notation. Write “nine legal balls” when sharing the required-rate calculation to avoid confusing those two representations. If a screenshot omits the target, fixture or timestamp, retrieve those fields before calculating; if it is an older image, keep the result dated to that image rather than calling it live.