What Is a Good Score in a 10 Over Cricket Match? Count the 60 Balls

Ten overs is the format most people actually play and the one almost nobody writes about properly. Ask what is a good score in a 10 over cricket match and you get numbers scaled down from T20 or ODI cricket, which is the wrong arithmetic. Ten overs is 60 balls. That is small enough to hold the whole innings in your head, and it changes what counts as par, when you accelerate, and how much one bad over costs you.

The short answer

In a 10 over cricket match, a working par score is about 90 to 110, which is a run rate of 9 to 11 an over. Above 110 is a strong total, and under 75 is usually chaseable. Professional 10-over cricket runs much higher: the record team total in the Abu Dhabi T10 is 159 for 0. Shorter innings push the scoring rate up, not down, because batters have fewer balls to protect and less reason to save wickets.

Why 10 overs is not half a T20

A par T20 total sits around 160 to 170. Halve it and you get 80 to 85. That estimate is too low, and the reason is wickets.

In 20 overs you have 120 balls to spend and ten wickets to lose. That is twelve balls per wicket, so wickets are the scarce resource and the whole shape of the innings is built around not losing them too early. In ten overs you have 60 balls and the same ten wickets. Six balls per wicket. Wickets stop being scarce. Balls become the scarce resource, and the only mistake that really hurts is a ball that produces nothing.

That single change flips the batting plan. A dot ball in a T20 costs you less than one per cent of the innings. A dot ball in ten overs costs you 1.7 per cent, and six dots in a row has taken a tenth of your match away. You cannot build. You can only start fast and stay fast.

The 60-ball budget

Work backwards from the run rate instead of guessing a total:

• 8 an over is 80
• 9 an over is 90
• 10 an over is 100
• 11 an over is 110
• 12 an over is 120

Now count the boundaries that get you there. To reach 100, you need roughly 12 to 14 balls that go for four or six. Twelve boundary balls averaging four and a half runs gives you 54 off 12 deliveries, which leaves 48 balls to produce about 46 runs. That second part is comfortable with singles, twos and a handful of dots. Take the boundary count down to seven or eight and the remaining 52 balls have to produce more than a run each, which almost nobody manages under pressure.

So a good score in a 10 over cricket match is really a boundary count in disguise. One boundary every four or five balls is par. One every three is a winning innings.

The powerplay is a fifth of the match

Professional T10 uses a two-over powerplay, and a full match is scheduled inside about 90 minutes. Two overs is twelve balls, which is 20 per cent of the innings. In a T20 the six-over powerplay is 30 per cent of the innings but spread across six overs, so there is time to recover from a quiet start. In ten overs there is not. If you take 10 off the powerplay you are already behind a 100 par score, and the next eight overs have to run at better than eleven.

Conditions that move par up or down

Par is not one number. Move it before the first ball:

1. Night conditions. The ball comes through differently under lights and a few batters never adjust their timing. Knock five to ten off par if you are batting at night against someone who bowls well with it.
2. Who is bowling the back end. A bowler who can land a yorker on demand takes two overs of your acceleration away. Against someone who cannot, the last three overs are worth 40 on their own.
3. The format you agreed. A five-over game is 30 balls, and par there is not half of a ten-over par. It is closer to 55 to 65, because there is no setup phase at all.
4. The chase. Teams defending 95 lose more often than you would think, because a chasing side knows the exact number and can budget it ball by ball.

What this looks like when you play online

The useful thing about short-format cricket is that you can test all of this in an afternoon instead of a season. On Howzat Live you can play cricket online in a live 1v1 match against a real person, in a browser, with nothing to download and nothing to pay. One of you bats and one of you bowls, you can talk to each other in match chat, and you pick 5, 10 or 20 overs before you start.

Ten overs is the format where the par-score arithmetic above matters most, and it is the one I would start with. A five-over game is over before either of you has settled into a plan. A 20-over game gives you enough balls that sloppiness gets forgiven. Ten overs punishes exactly one thing, which is wasting deliveries, and that makes it the fastest way to learn how to pace an innings.

A few ways to run the experiment properly:

• Pick 10 overs and day conditions for your first few matches so you are only changing one variable at a time.
• Write your par number down before the toss. Then see how close the actual total came.
• Play the same format twice in a row, once batting first and once chasing, and compare which felt easier.
• Use a private link to get a specific friend into the same match, or take a quick match against whoever is online.

You can create a free account in under a minute, and after five rated matches you get a Scale badge from 0 to 10 that tracks how you are actually doing. Beating stronger opponents moves you up faster, and playing the same person over and over is damped so you cannot farm one friend to the top of the leaderboard.

Practising the numbers against a bot

If you want to rehearse a chase without the pressure of a real opponent waiting on you, there are three computer difficulties: Gully bot, Club bot and Academy bot. Set a ten-over target, chase it, and watch where the innings leaks runs. It is a good way to learn what 60 balls feels like.

Two things to know about bot matches. Results against the computer are rated at half weight and capped at a few per day, and they can only carry you as high as Scale 3 on Club. Everything above that has to come from matches against real people. That is deliberate. A bot has habits you can learn, and a par score you can beat against Club bot is not the par score a decent human will let you have.

Defending a 10-over total

The bowling side has the same arithmetic in reverse, and most people get it wrong by thinking about overs instead of balls.

If you are defending 100, you are allowed 60 balls of leakage at 1.66 runs each. A single costs you nothing. A boundary costs you two and a half balls worth of budget. A six costs you nearly four. So the entire job is boundary prevention, not wicket-taking, and the bowler who concedes 1-1-1-1-1-1 for six is doing a better job than the one who goes 0-0-0-4-0-6 for ten with a play and a miss in between.

Three practical rules:

• Bowl the length that makes the batter hit square or straight, not the length that lets them swing across the line.
• Treat the first two overs as the ones to survive, because a batter who starts at eleven an over will not slow down.
• Keep something in reserve for the last two overs. In ten overs those twelve balls routinely decide the result.

So what is a good score

A good score in a 10 over cricket match is 90 to 110 on a normal surface, built from twelve to fourteen boundary balls and as few dots as you can manage. Scale it to 55 to 65 for a five-over game and 150 to 170 for 20 overs. And treat those as starting points, because the par score for your match is the one you and your opponent set the last time you played.

More short-format breakdowns are on the blog, and if something here does not match what you are seeing in your own matches, contact us and tell me about it.