{{ summaryTitle }}
{{ summaryValue }}

{{ summaryLine }}

Format{{ computation.ok ? formatLabel : '—' }} Run rate{{ computation.ok ? `${formatRate(computation.values.current_run_rate)} RPO` : '—' }} Chase{{ computation.ok ? computation.values.chase_state : '—' }}
{{ workflowAnnouncement }}
Current over{{ computation.ok ? computation.values.overs_label : '—' }}
{{ stageAnnouncement }}
Cricket innings setup and correction controls
Use a concise team or innings label.
Keep it short enough for a mobile scoreboard.
Limited-overs presets use six legal balls per over.
Enter 1–500 whole overs; choose Custom for local formats.
overs
Use the second innings when the batting side is chasing.
Set 0 when there is no active chase target.
Includes batting runs and extras.
Enter a whole dismissal count from 0 to 10.
Six legal balls become one completed over.
balls
The neutral default is off.
{{ show_target_line ? 'Enabled' : 'Disabled' }}
{{ tableExportStatus }}
AspectValueScorer noteCopy
{{ row.label }}{{ row.value }}{{ row.note }}
{{ tableExportStatus }}
MetricValueMatch cueCopy
{{ row.label }}{{ row.value }}{{ row.note }}
{{ chartExportStatus }}

The chart renderer is unavailable. The innings and event ledgers remain available.

{{ tableExportStatus }}
#OverDeliveryRunsScore afterCueCopy
{{ row.sequence }}{{ row.over }}{{ row.delivery }}{{ row.runs }}{{ row.score }}{{ row.cue }}
{{ jsonExportStatus }}

A score of 96/3 after 11.4 overs packs several facts into one line. The batting side has 96 runs, has lost three wickets, and has faced 70 legal balls. The “.4” is four balls into the next over, not four-tenths of an over.

That legal-ball count drives limited-overs arithmetic. Current run rate divides runs by overs actually faced. A chase adds the winning target, balls remaining, and required run rate. Wides and no-balls add runs without using one of the six legal balls, while ordinary scoring shots, byes, leg byes, and most wicket deliveries advance the ball count.

  • Current run rate is runs scored per six legal balls so far.
  • Required run rate is runs still needed per six legal balls remaining.
  • Projected score extends the current rate to the configured innings limit.
  • Wickets in hand is ten minus the wickets already lost.

Rate is only one view of an innings. A projection assumes the same scoring pace continues and does not predict wickets, bowling changes, pitch conditions, field restrictions, or a late acceleration. Two sides on the same run rate can therefore have very different prospects when their wickets in hand differ.

Targets also need careful wording. If the first side scores 175, the second side's winning target is 176. Entering 175 would make the chase appear complete one run too early. Match-specific adjustments such as revised rain targets must be entered as the actual winning target supplied for that innings.

Ball-by-ball tracking works best as a scorer's working record rather than an official scorebook. It can keep arithmetic consistent and make each change reversible, but unusual extras, compound deliveries, penalty runs, and local playing conditions may need a fuller scoring system.

How to Use This Tool:

Set the innings limit and current score before recording the next delivery.

  1. Enter the two sides, choose a Match format, and select the Innings. For a chase, enter the score needed to win in Winning target; use 0 when no target is active.
  2. Confirm Current runs, Current wickets, and Legal balls. Use these fields to establish or correct the current state.
  3. Record the next delivery with the scoring buttons. Wides and no-balls add one run without advancing the six-ball rail; byes and leg byes add one run and one legal ball.
  4. Use Undo latest to reverse the most recent delivery. Check the scoreline and chase cue before continuing, especially after correcting the numeric fields directly.

Interpreting Results:

Read the scoreline and wickets before the rate labels. A high current rate with few wickets left is less secure than the same rate with a large wicket buffer. The projected score is a pace extension, not a forecast of what will happen.

During a chase, On rate means the current run rate is at least the required run rate. Rate climbing appears only when the required rate is more than 2.00 runs per over above the current rate. Values between those conditions return Manage chase.

  • Target reached applies as soon as runs are greater than or equal to the winning target.
  • All out applies at exactly 10 wickets when the target has not been reached.
  • Overs complete applies when no legal balls remain and the chase is still short.
  • A final Current point on the scoring worm means the typed score no longer matches the last recorded delivery state.

Technical Details:

Limited-overs rates use legal balls as their time base. Six legal balls make one over, so calculations use B/6 overs even though the scoreboard displays completed overs and leftover balls as x.y.

Formula Core

The current run rate (CRR) divides total runs R by legal balls B expressed as overs.

CRR= { 0if B = 0 RB/6if B > 0

Before the first legal ball, CRR is 0. The projected score extends that rate across the configured over limit O and rounds to the nearest whole run.

P= { Rif B = 0 round(CRR×O)if B > 0

For an active second-innings chase, runs needed N and balls remaining Br determine the required run rate (RRR).

N=max(0,TR) , Br=max(0,6OB) , RRR=NBr/6 when a chase is active, N > 0, and Bᵣ > 0

RRR is shown only while a positive target remains and at least one legal ball is available. At 72 runs from 48 balls, CRR is 9.00 runs per over. In a 20-over innings the pace-only projection is 180.

Rule Core

Cricket delivery actions and score effects
Delivery action Runs added Legal balls added Wickets added
Dot, 1, 2, 3, 4, or 6 0, 1, 2, 3, 4, or 6 1 0
Wide or no-ball 1 0 0
Bye or leg bye 1 1 0
Wicket 0 1 1

The innings closes when wickets equal 10, legal balls reach or exceed six times the over limit, or an active chase reaches the target. Balls remaining never fall below zero. Wickets in hand are 10 minus wickets lost.

Team labels are required and limited to 40 characters. Runs and targets accept whole numbers from 0 to 100,000; wickets from 0 to 10; and legal balls from 0 to 3,000. The delivery history retains at most 80 events, so a long innings may preserve only its latest recorded sequence while the typed totals continue to represent the current score.

Limitations:

The delivery buttons model a compact subset of cricket scoring. They are suitable for a working limited-overs board, not every combination an official scorer may need.

  • Wide, no-ball, bye, and leg-bye actions each add exactly one run.
  • A wicket action adds no run and counts one legal ball; unusual dismissals on no-balls, wides, or completed runs need manual correction.
  • The projection does not model wickets, remaining batters, bowling quality, venue, weather, or revised-target methods.
  • Official scorers and competition playing conditions remain authoritative.

Worked Examples:

A wide during a T20 chase

At 12/1 after 1.0 over, a side chasing 176 needs 164 from 114 legal balls. Its current rate is 12.00 and required rate is about 8.63 runs per over, so the chase is On rate. Recording Wd changes the score to 13/1 but leaves the over at 1.0; 163 are then needed from the same 114 balls, lowering the required rate to about 8.58.

References: