Read a Cricbuzz score one event at a time.

Confirm the fixture and innings

Match team names, date, competition, format and innings. A women’s fixture or an A-team match can share a short country label with another event. An innings-break screen and a new-innings score describe different states.

Overs use legal balls, not decimal fractions

In a six-ball over, 14.3 means fourteen completed overs and three legal balls: 87 legal balls in total. It is not 14.3 multiplied by six. Wides and no-balls can add runs without advancing the legal-ball count.

Read runs, wickets and target together

A team at 120/4 has scored 120 with four wickets lost in the displayed innings. A target belongs to the chase and can change under applicable conditions. A batting rate or required rate needs the remaining legal balls and correct target.

Use commentary for the sequence

A scorecard is a summary, while ball commentary gives an event order. Check the ball label and correction notes before concluding that a wicket or run disappeared. An official correction can alter a previously displayed event.

A paused score may describe the match state

Rain delay, innings break, stumps and abandonment are different statuses. A screen that stops changing during a break is not sufficient evidence of an app failure. Compare the status and the governing competition result.

17.4 overs means 106 legal balls

In a six-ball-over format, 17.4 is 17 completed overs and four legal balls: 17 × 6 + 4 = 106. It is not the decimal 17.4. A score of 150 at that point has a rate of 150 ÷ (106 ÷ 6), approximately 8.49 runs per over.

A wide or no-ball can add a run without advancing the legal-ball count in the same way as a legal delivery. Use the commentary sequence to interpret why the score changed while the over label appears unchanged.

A target or rain delay changes what the numbers answer

Read innings break, revised target, rain interruption and final result as match states. A required rate needs runs still needed and legal balls remaining under the current conditions. Do not calculate it from a superseded target.

If a notification arrives one ball later than the live page, retain its event time and compare that event in commentary. Refreshing repeatedly without identifying the ball can make the two screens appear contradictory when they describe different moments.

Example: a late notification

A notification for 12.4 arrives after the page already shows 12.5. Match the event labels and capture the times; the notification’s delivery time is not necessarily the event time. Report a missing or wrong event separately from delivery latency.