Cricket Live Scores and Scorecards
Follow a cricket match with confidence: wickets, overs, run rate, targets and match state.
What a live score actually tells you
A live cricket score reports how many runs a team has made, wickets lost and how much of its innings has been completed. In limited-overs cricket, the notation 126/4 after 16.2 overs means 126 runs, four wickets down and 16 overs plus two legal deliveries completed. The dot in 16.2 is not a decimal fraction; there are six legal balls in an over. Extras, penalties and unusual interruptions can affect how a displayed score progresses. The scoreboard is a snapshot of a match, not a forecast of who will win. First identify the format and innings before interpreting the figures.
Run rate, required run rate and chase context
Current run rate is runs scored divided by overs faced, including fractional overs converted into balls. Required run rate compares runs still needed with legal deliveries remaining in a chase. For example, chasing 181 with 120 legal balls, a team at 100 after 72 balls needs 81 runs from 48 legal balls, or 10.125 runs per six-ball over. A higher required rate can indicate more scoring pressure but is not a probability model: wickets, batters at the crease, ground dimensions, weather and bowling resources all matter. Do not compare rates from different formats without adjusting for their scheduled innings length.
Read a scorecard by batting, bowling and extras
A batting scorecard shows individual runs, balls faced, boundaries, dismissal type and usually strike rate. A bowling scorecard shows deliveries, runs conceded, wickets, economy and sometimes maidens. Team totals can also include wides, no-balls, byes and leg-byes. An individual batter's strike rate answers a different question from a bowler's economy rate; neither should be treated as a stand-alone measure of match impact. Look for how the innings progressed, which phases were most productive and whether the batting side had wickets left. Context should accompany any comparison across match conditions.
When a score changes after an interruption
Rain, bad light or other interruptions may shorten available play or cause adjustments to a target according to applicable playing conditions. A score widget may briefly show a prior target while an official decision is pending. Likewise, commentary can lag an official scorecard by several deliveries. When live information matters, compare the score display with the competition's official match information. In particular, avoid presenting an old target as current after a reduction in overs. This guide does not provide real-time match data; it explains how to interpret data supplied by authorized score services.
Compare score apps using an evidence checklist
To choose a score app, inspect update speed under your connection, coverage of domestic competitions, ball-by-ball commentary, notification controls, accessibility, data usage and availability of detailed scorecards. Record a like-for-like match sample rather than trusting generic claims that one app is universally fastest. Check whether match status is official, delayed or manually curated; also confirm whether the app tracks women's cricket, youth competitions and the leagues you actually follow. Cricbuzz and other cricket information products may provide scores and news, but they are categorically different from fantasy contests and real-money sportsbooks. An app comparison should not rank those activities as interchangeable.
Continue your research
Use the related guides to understand the differences between cricket score information, fantasy scoring and predictions. Information on this site is educational, not a live scoring service or a promise of results.
A note on win probability graphics
Some live-score products display estimates of which team is more likely to win. These estimates are model outputs, not official match results. The underlying method may use historical matches, score and wicket position, ball count or player information, but many interfaces do not disclose the full model. Compare probabilities only when the underlying assumptions, match format and update timestamp are known. A sharp change after a wicket can be mechanically plausible without proving that the estimate is calibrated. Readers should not treat a win-probability visualization as a personal betting advantage or a statement of certainty.