Not every fan can watch every match on television. Work, study, travel or limited data often mean following a game through live text commentary on a phone. Ball-by-ball commentary can be surprisingly rich once you understand its notation and the numbers around it. This guide explains how to read it quickly, what the common symbols mean and which numbers tell you who is really winning.
The basic line format
Most live commentary shows each delivery on its own line. A typical line starts with the over and ball number, such as 14.3, meaning the third ball of the fifteenth over. It then names the bowler and batter, for example “Bowler to Batter”, followed by the outcome: no run, 1 run, FOUR, SIX or OUT. A short description adds detail, such as where the ball pitched and where the shot went.
Overs are counted from zero, so 0.1 is the first ball of the match. When you see 19.6, the twentieth over has just finished.
Common notation
- Dot or 0: no run scored.
- W: wicket.
- wd: wide, which adds a run and must be re-bowled.
- nb: no ball, which adds a run, is re-bowled and may bring a free hit in white-ball cricket.
- lb: leg byes, runs taken after the ball hit the batter’s body.
- b: byes, runs taken after the ball passed the batter and keeper without contact.
Extras are counted separately from the batter’s runs, which is why a batter’s score and the team total do not always add up the way new fans expect.
End-of-over summaries
At the end of each over, commentary usually shows a summary: runs from the over, the team score, the two batters’ scores and the bowler’s figures. Reading only these summaries is a quick way to catch up if you join late. Look for overs with several dot balls followed by a wicket; pressure often builds this way.
Match schedules, Bangladesh start times and fan guides are available on the NotOutBD live match guide.
Numbers that tell the real story
- Run rate: runs per over so far.
- Required run rate: runs per over needed to win in a chase.
- Partnership: runs added by the current pair; a big partnership often changes momentum.
- Balls remaining and wickets in hand: in a chase, these matter more than the runs needed alone.
A chase that needs 60 from 36 balls with eight wickets left is very different from the same target with two wickets left, even though the required rate is identical.
Win probability graphics
Many apps now show a win probability bar based on past matches with similar situations. It is useful as a quick summary, but it is a model, not a prediction of certainty. Probabilities swing sharply after wickets and big overs, especially in T20 cricket. Treat the bar as context rather than fact.
Saving data and battery
- Use the text-only commentary view instead of video highlights.
- Turn off auto-playing clips in the app settings.
- Refresh at the end of each over rather than every ball.
- Lower screen brightness and close other apps during long matches.
Reading Test match commentary
Test commentary moves more slowly but carries more detail about tactics: field changes, the condition of the ball, the light and the session situation. Watch for notes about the new ball after 80 overs, bowling changes before an interval and the number of overs remaining in the day. These small notes explain why a session suddenly speeds up or slows down.
Key points to remember
- Each line shows the over, the players and the outcome.
- Learn the shorthand for extras: wd, nb, lb and b.
- Use over summaries to catch up quickly.
- In chases, combine required rate with balls and wickets remaining.
If you follow live matches through online platforms, check your contacts first. The NotOutBD agent list shows the officially listed contacts.
