Explainers · 2026-06-21

How cricket scoring works: runs, extras and the scorecard

Cricket's scoring can look baffling to a newcomer: numbers pile up, the commentary talks of wides and leg byes, and a scorecard is a dense little grid of figures. But underneath it all sits a simple idea — the batting side is trying to accumulate runs, and there are only a handful of ways to do it. Once you understand where each run comes from, the whole scorecard opens up.

The basic unit: the run

A run is scored when the two batters at the crease exchange ends. After a batter hits the ball, the pair can choose to run: each completed length of the pitch, from one popping crease to the other, is worth one run. Run there and back and that is two; a hard-hit ball into a gap might yield three if the fielders are slow to retrieve it.

The batters do not have to run at all. If the ball trickles only a short distance, or the fielders are lurking close, they may simply stay put and score nothing. Running is a judgement call made in a split second, and it carries risk: a run out is possible whenever a batter is short of the crease with the ball in play. Good running between the wickets — quick calling, sharp turns, backing up — quietly wins a surprising number of matches.

Boundaries: four and six

The most eye-catching way to score is to find the boundary, the rope that marks the edge of the field. If the ball reaches or crosses that rope having touched the ground on the way, the batter is awarded four runs, with no need to run at all. If it clears the rope on the full — without bouncing — the reward is six runs.

Fours and sixes are the currency of the modern game, especially in the shorter formats, but they matter in every version of cricket. A boundary is efficient: it brings runs without the physical toll of sprinting or the danger of being run out. A batter who can pierce the field for four, or clear the rope for six, changes the arithmetic of an innings very quickly. When a scorecard shows a batter's fours and sixes alongside their total, it tells you at a glance how they built their score — grafted in singles, or blazed in boundaries.

Extras: runs the batter did not score

Not every run is credited to the batter. Some are awarded to the batting side as extras (called "sundries" in some parts of the world), and they fall into a few distinct categories. Extras exist to penalise the fielding side for errant bowling or for letting the ball slip past, and they are recorded separately on the scorecard so that the bowler and batter are each held accountable for the right things.

Wides

A wide is called when the bowler delivers the ball too far from the batter to allow a normal shot — too far down the leg side, or beyond the batter's reach outside off. The umpire signals it by stretching both arms out horizontally. A wide adds one run to the total and, crucially, the delivery does not count as one of the six legal balls in the over, so the bowler must bowl it again. In the limited-overs formats the definition of a wide is applied strictly, which is why you see so many called down the leg side.

No-balls

A no-ball is an illegal delivery, most commonly because the bowler has overstepped the popping crease with the front foot, though there are other causes such as a delivery that is too high or a fielder standing in an illegal position. Like a wide, a no-ball adds a run and must be re-bowled. In many formats it also brings a free hit — the following delivery on which the batter cannot be bowled or caught out — which turns a small error into a costly one.

Byes and leg byes

Byes and leg byes are the subtler extras. A bye is scored when the ball passes the batter without touching the bat or body, the wicketkeeper fails to gather it, and the batters run. A leg bye is scored when the ball strikes the batter's body — a pad or thigh, say — rather than the bat, and the batters run from the deflection. Neither is charged against the bowler, because neither is really the bowler's fault; but both are recorded as extras rather than credited to the batter, because the batter did not hit the ball with the bat. They are a reminder that a run can come from almost anywhere on the field.

How dismissals affect the score

Runs tell only half the story; wickets tell the other. Each time a batter is dismissed, the fielding side has taken a wicket, and the batting side loses one of its ten. A team's score is almost always written as runs for wickets — "220 for 4" means 220 runs with four batters out. In some countries the order is reversed to "4 for 220", but it means the same thing.

That little pairing of numbers is the heartbeat of a cricket match. A big total with few wickets down is a position of strength; a modest total with many wickets gone is a side in trouble. When you glance at a scoreboard, the runs tell you how far the batting side has travelled, and the wickets tell you how much petrol is left in the tank.

Reading a scorecard

A full scorecard packages all of this into a compact table, and learning to read it is one of the quiet pleasures of following the game. The batting section lists each player, how they were dismissed (or "not out" if they survived), the runs they scored, and usually the number of balls they faced along with their fours and sixes. From those figures you can reconstruct an innings you never saw: a high strike rate with lots of boundaries suggests an aggressive knock, while many balls faced for modest runs points to a patient, defensive vigil.

Below the batters sits the extras line, breaking down the byes, leg byes, wides and no-balls, and then the team total with its wickets and the number of overs bowled. The bowling section mirrors it from the other side: each bowler's overs, maidens (overs from which no runs were scored off the bat), runs conceded and wickets taken. An economy rate — runs conceded per over — tells you how tightly a bowler kept things, while the wickets column tells you how much damage they did.

Put the two halves together and the scorecard becomes a story. You can see who anchored the innings and who accelerated, which bowler broke a partnership and which one leaked runs, and how the extras nudged the total up. It is history written in numbers, and once the code clicks it reads almost like prose.

The strike rate and the run rate

Two further numbers help you judge tempo. A batter's strike rate is runs scored per hundred balls faced — a measure of how quickly they score. A strike rate around a hundred means roughly a run a ball; much higher signals fast, boundary-laden hitting, while lower suggests careful accumulation. In the longest format, where time is plentiful, strike rate matters less; in the shortest, it is everything.

For the team, the run rate is runs per over, and its cousin the required run rate tells a chasing side how many they need per over to win. Watching those two numbers converge or diverge is one of the great tensions of a run chase: as the required rate climbs, the pressure on the batters mounts, and every dot ball tightens the screw a little further.

Overthrows and penalty runs

A few less common sources of runs are worth knowing. Overthrows occur when a fielder's throw at the stumps misses and speeds away, allowing the batters to run further; any extra runs taken are added to whatever was already scored off that ball. If the throw crosses the boundary, four more runs are awarded on top of those already run, which is how a single delivery can occasionally yield a startling number of runs.

Then there are penalty runs, awarded in blocks of five for various infringements by the fielding side — such as illegal fielding, deliberate time-wasting, or damaging the pitch. These are rare, and a casual viewer may go a long season without seeing one, but they exist to keep the fielding side honest, and they appear on the scorecard among the extras. They are a reminder that the laws of cricket cover a great deal more than the everyday run, and that almost every eventuality has its own agreed accounting.

Putting it all together

Cricket scoring, then, is really a small set of building blocks. Batters score in ones, twos and threes by running, and in fours and sixes by finding the boundary. The fielding side gifts extras through wides, no-balls, byes and leg byes. Wickets track how many batters remain, and the scorecard gathers everything into a table that anyone can learn to read. None of it is complicated once you see the parts; the richness comes from how they combine over the course of an innings.

The best way to make the code second nature is simply to watch with the scorecard open, matching each run and wicket to its line in the table. Before long you will be reading a total the way a seasoned follower does — not as a bare number, but as a story of how it was built. If you would like to test how well you know the players behind those numbers, try Guess the Cricketer over at crickedle.