Ball-by-ball cricket scoring

Score club and tournament matches delivery by delivery on iOS, Android, or web — with an audit trail umpires and scorers can trust on match day.

  • Full scorebook with extras and dismissals
  • Live public scorecard as you score
  • Undo / audit trail for disputed balls
  • Works offline-friendly on match day phones

Match-day scorepad

Tap runs, extras, and wickets in order. The pad is built for scorers who already know a paper book — not a generic sports form.

Live scorecard

Batting cards, bowling figures, and fall of wickets update for anyone following the fixture link — useful for parents and opposing captains.

Audit & corrections

Mistakes happen. Correct a ball with a clear history so organizers can resolve disputes without rewriting the whole innings.

How it works

  1. Create or open the fixture — From My Matches or your league centre, open the match and choose Score.
  2. Set opening batters and bowler — Confirm squads, then start the first over.
  3. Score every ball — Enter legal deliveries, extras, and wickets. End overs and innings with guided prompts.
  4. Publish the result — Close the match — standings and player stats update for the season.

Open matches · Scoring tutorial · Create a match

What ball-by-ball scoring actually involves

Digital scoring is not just a faster scorebook. It changes what happens when someone queries a result three weeks later — which is the part most clubs only appreciate after their first dispute.

What gets recorded per delivery

  • Striker, non-striker, and bowler.
  • Runs off the bat, and whether they came from a boundary.
  • Extras, split into byes, leg byes, wides, and no-balls — these are charged differently and affect the over count differently.
  • Dismissal type and the fielders credited, so catches, stumpings, and run-outs attribute correctly.
  • The resulting over and ball number, which drives strike rotation and end changes.

Because each of those is captured separately rather than as a running total, every derived figure — partnerships, strike rates, economy, fall of wickets, the manhattan — comes out of the same record rather than being maintained by hand alongside it.

Corrections and the audit trail

Scorers make mistakes, particularly when a wicket and an overthrow arrive in the same delivery. Corrections are expected: a recorded ball can be amended, and the amendment is stored alongside the original rather than replacing it silently.

That history is what makes a disputed result resolvable. When a captain queries a total a fortnight later, the league can look at what was entered, what was changed, when, and by whom — instead of comparing two paper books that disagree.

Practical advice for a first scored match

  1. Link every player to a profile before the toss. Typed names create duplicate statistical identities that are tedious to merge later.
  2. Agree who is scoring before play starts, and make sure a second person has access in case the first has to field.
  3. Score a friendly first. The interface is quick once familiar, but a league fixture is not the place to learn it.
  4. Do not wait to fix an error. Correct it at the end of the over while you still remember what happened.
  5. Check the total against the opposition's book at the innings break, not at the end of the match.

Grounds without signal

Plenty of club grounds have no usable mobile data. Scoring continues locally when the connection drops and syncs once it returns, so a lost signal at deep midwicket does not cost you an innings.