Ball-by-ball commentary turns a live cricket match into a readable sequence of events. This guide explains common abbreviations, scoring symbols, wickets, reviews, over summaries, partnerships, and required run rates so you can follow a live cricket score even when video coverage is unavailable.
Overview
A ball-by-ball feed records what happens on each delivery, usually from the bowler’s release to the end of the play. A typical update may show the over and ball number, the batter, the bowler, the outcome, and the new score. For example, 12.4 FOUR means the fourth legal delivery of the 12th over went for four runs.
The first point to remember is that over notation is not decimal notation. In 12.4, the number after the dot identifies the delivery, not a fraction of an over. Because a legal over contains six balls, 12.6 is the final legal delivery before the next over begins. A wide or no-ball normally does not count as one of those six legal deliveries, so the feed may show another delivery after 12.6.
Commentary feeds differ slightly between score providers. One platform may write Wd for a wide, while another uses W or the word Wide. Treat the wording as a presentation difference and use the scorecard to confirm the official total. For a broader explanation of runs, overs, wickets, extras, and strike rates, see How to Read a Cricket Scorecard.
What to track
Runs and boundaries
Common ball-by-ball outcomes include:
- Dot ball or 0: No run is added from the delivery.
- 1, 2, 3: The batters complete that number of runs.
- 4 or FOUR: A boundary reached without the batters needing to run four times.
- 6 or SIX: The ball clears the boundary on the full after contact with the bat.
- 2 runs, all run: The batters ran the stated number of runs rather than hitting a boundary.
A boundary is usually credited to the batter, although an overthrow or unusual fielding event can alter how the runs are recorded. If the feed says 4 byes or 4 leg byes, the four runs are extras, not batter runs.
Extras
Extras are runs added to the team total without being credited to the batter. The most common abbreviations are:
- Wd: Wide. The delivery is judged too far from the batter to be playable under the applicable playing conditions. It adds at least one extra and does not count as a legal ball.
- Nb: No-ball. It adds a no-ball extra and does not count as a legal delivery. Additional runs may come from the bat, running, or a boundary.
- B: Bye. The batters run after the ball misses the bat and the ball is not a no-ball.
- Lb: Leg bye. The ball makes contact with the batter’s body or protective equipment, subject to the laws and the umpire’s judgment, rather than the bat.
- 5wd, 3nb, 2lb: The number before the abbreviation shows the total runs recorded as that type of extra.
A wide or no-ball can produce more than one run. For example, 5wd may indicate a wide that reaches the boundary, while 2nb can mean the no-ball penalty plus one additional run. The exact display varies, so check whether the scorecard separates the penalty from other runs.
Wickets and dismissals
A wicket update normally identifies the dismissed batter, the score, and the dismissal method. Common shorthand includes:
- c: Caught, followed by the catcher and often the bowler.
- b: Bowled.
- lbw: Leg before wicket.
- st: Stumped by the wicketkeeper.
- ro: Run out.
- hit wicket: The batter dislodges the stumps in circumstances covered by the dismissal law.
Not every wicket is credited to the bowler. Catches, bowled, lbw, and stumped dismissals generally appear in the bowler’s wicket tally, while run outs and some other dismissals do not. If you want more context on tactical roles around the ball, the guide to cricket fielding positions is a useful companion.
Reviews and umpire decisions
Feeds may use DRS, review, third umpire, NOT OUT, OUT, or umpire’s call. A review pauses the normal flow while the decision is checked. The original decision may stand, be overturned, or remain subject to umpire’s call under the relevant review process. A review is an event, not automatically a wicket or a change to the score.
For a detailed explanation of ball tracking, review outcomes, and umpire’s call, read How DRS Works in Cricket. During a live match, wait for the confirmed decision before updating your interpretation.
Over changes, partnerships, and rates
At the end of an over, a feed may show an over summary such as 1 0 4 Wd 2 0 6 = 14. Read the entries from left to right, then confirm the total. The next over is bowled from the opposite end, and the batters may change ends according to the final completed play.
A partnership records the runs scored by two batters while they share the crease. It can reveal a change in match momentum even when the individual scores move slowly. A partnership of 48 from 62 balls in a Test match tells a different story from 48 from 24 balls in a T20, so always consider both runs and deliveries.
Current run rate is usually the team’s runs divided by overs completed, while required run rate is the runs still needed divided by the overs or balls remaining. A more precise limited-overs formula is:
Required run rate = runs required ÷ balls remaining × 6.
For example, if a team needs 72 runs from 48 balls, it requires 9.00 runs per over. In a Test match, required run rate is less central than the lead, deficit, wickets in hand, time remaining, and match situation.
Cadence and checkpoints
Use a simple reading workflow whenever you open a live cricket match center:
- Check the match state: Identify the format, innings, target, score, wickets, and overs or time remaining.
- Read the latest delivery: Note the ball number, result, batter, and whether the event was legal.
- Update the score mentally: Add runs, extras, or a wicket, but do not treat a wide or no-ball as a completed legal ball.
- Check the strike: The feed or scorecard should show which batter is facing. Strike can change after completed runs, boundaries, over completion, or unusual events.
- Review the over summary: At six legal balls, pause and assess the runs, wickets, extras, and bowling change.
- Compare the situation: In a chase, compare the current rate with the required rate. In a first innings, compare scoring speed with wickets lost and the format’s remaining overs.
For a T20, checkpoint after every over and especially after a wicket, dropped chance, review, or over containing several boundaries. In an ODI, assess the powerplay, middle overs, and final phase separately, while remembering that competition-specific fielding restrictions can vary. In a Test, use sessions and passages of play as checkpoints: opening spells, changes of ball, partnerships, wickets near the end of a session, and the lead or deficit after each innings.
Before the first ball, confirm the toss, innings, playing elevens, and venue where available. The cricket fixtures and schedules guide can help resolve start times and time-zone confusion.
How to interpret changes
Momentum is not one official statistic; it is a reading of how the match situation changes. Look for clusters rather than isolated deliveries. Three dot balls may increase pressure, but a single six can reverse the immediate pattern. A wicket followed by a maiden over is usually more significant than a wicket followed by several boundaries.
In a T20, track boundary frequency, wickets in hand, and the required rate after each over. A rising required rate does not necessarily mean the chase is lost, but it reduces the margin for dot balls and low-scoring overs. In an ODI, compare the chase with the target and balls remaining, then note whether the batting side is preserving wickets or taking risks. In a Test, a sequence of defensive overs can be valuable if the batting side is protecting a draw, while a fast partnership may be intended to create time to take 20 wickets.
Separate confirmed facts from commentary opinion. “Pressure building” is an interpretation; “two maidens and one wicket in the last four overs” is an observable sequence. Use the scorecard for confirmation when commentary appears delayed or contradictory. You can also compare innings, player contributions, and bowling figures using the player stats comparison guide.
When to revisit
Return to this guide during any live match when an unfamiliar abbreviation appears, a review interrupts play, or the over count seems inconsistent after wides and no-balls. Recheck the glossary before switching between T20, ODI, and Test coverage because the same score can have very different importance in each format.
Editors and regular readers should revisit the article before major domestic or international seasons, and at least quarterly, to check whether the preferred score provider has changed its notation, whether competition terminology has been updated, and whether examples still match current match-center displays. Laws and playing conditions can also affect how an event is described, particularly reviews, short runs, penalty runs, and replacement players.
For practical match-day use, save this page with your live score center. Start with the score, wickets, overs, target, and latest ball; verify every unusual event in the scorecard; then reassess the situation at the end of each over. After the final ball, use this scorecard analysis workflow to review which partnerships, wickets, extras, and rate changes shaped the result.