Cricket Scoreboard Tracker

Limited-overs cricket turns every delivery into a resource decision. The batting side is trying to build or chase a total while spending two scarce resources: wickets and legal balls. A score such as 86/2 is only meaningful once the over count is known. At 8.0 overs it may be a strong platform; at 15.0 overs it may leave too much work for the last phase of the innings.

The compact scoreboard language hides several separate judgments. Runs move the total. Wickets reduce the batting side's room for risk. Legal balls move the innings clock. Extras add to the team total without always crediting the batter, and wides or no-balls are easy to miscount because they add at least one run while leaving the six-ball over unchanged.

Chases add another comparison. The batting side does not only need runs; it needs runs at a pace that fits the balls remaining. Required run rate rises quickly after quiet overs because every dot ball removes one scoring chance. Current run rate can look healthy early in an innings, but it becomes less forgiving when the target is high, the over limit is short, or wickets are falling.

Reliable live scoring starts after the umpiring decision has been made. The scorer still has to choose what happened on the delivery: dot ball, boundary, wide, no-ball, bye, leg bye, or wicket. Once that choice is settled, the arithmetic should move the total, over notation, chase pressure, and delivery history in the same direction.

The scorecard also records pace. A scoring worm, run-rate figure, and delivery ledger can show whether one expensive over, a wicket cluster, or a long quiet spell changed the innings. Those clues support discussion and review, but they do not replace official playing conditions, umpire calls, or competition-specific scorekeeping rules.

How to Use This Tool:

Set the innings context first, then score deliveries as they happen. Manual fields remain available when the current score needs a correction.

1. Enter Batting side and Bowling side so the scoreline, tables, chart, and structured data use the right match labels.
2. Choose Match format. The T20, ODI, T10, and 5-over options fill the normal over limit; choose Custom when a local game uses another length.
3. Set Innings. For a chase, choose 2nd innings and enter the Target score, meaning the score needed to win.
4. Check the starting Runs, Wickets, and Legal balls. The summary should show the score in cricket notation, such as 12/1 (1.0).
5. Use Delivery actions for dots, 1, 2, 3, four, six, wide, no-ball, bye, leg bye, and wicket. Wide and no-ball buttons add one extra run without adding a legal ball.
6. Use Undo last after a single scoring mistake. For larger corrections, edit Runs, Wickets, or Legal balls directly, then compare the scoreline with Ball Event Ledger.
7. Read Innings State for the current score, Chase Rate Sheet for target pressure, Scoring Worm for the run and wicket path, and JSON when you need a structured handoff.

If a warning appears, fix the setup before relying on the result. Typical warnings cover more than 10 wickets, negative values, legal balls beyond the over limit, a first-innings target, or a second innings with no target score.

Interpreting Results:

The scoreline gives the state of the innings; the run-rate fields explain how urgent that state is. Current run rate is the pace already achieved. Required run rate appears during a chase and shows the pace needed from the remaining legal balls. A batting side can be On rate and still be under pressure if only a few wickets are left.

Projected score extends the current run rate across the configured over limit. It is a pace estimate, not a forecast of wickets, pitch changes, bowling quality, or late-innings acceleration. After a boundary over, wicket maiden, or manual correction, recheck the projection instead of treating the old number as stable.

• On rate: current run rate is at least the required run rate, assuming the batting side can sustain it.
• Rate climbing: required run rate is more than 2.00 runs per over above the current rate, so the chase needs a scoring surge.
• Manage chase: required rate is close to the current rate, so wickets in hand and strike rotation matter.
• Closed innings: all 10 wickets have fallen, the over limit is reached, or the chase target has been reached.

Technical Details:

Cricket over notation is base-six notation for legal balls. The value 4.5 means four complete overs plus five legal balls, not 4.5 decimal overs. Run-rate arithmetic must convert legal balls to decimal overs before division, otherwise 4.5 overs would be treated as too much time and the rate would be understated.

Extras change the total in different ways. A wide or no-ball adds a penalty run and does not count as one of the over. A bye or leg bye adds an extra to the team total after a legal delivery. Those rules make legal-ball count the main time base for current run rate, required run rate, balls remaining, and projected score.

Formula Core

The main rates convert legal balls into overs by dividing by six. Required run rate uses only the balls still available in the chase.

For 72/3 after 10.0 overs in a 20-over chase of 176, the current run rate is 72 / (60 / 6) = 7.20 runs per over. The batting side needs 104 runs from 60 legal balls, so required run rate is 104 / 10 = 10.40 runs per over. The projected score at the same pace is round(7.20 x 20), or 144. Before any legal ball has been bowled, projection stays at the current run total.

Delivery Counting Rules

Each scorekeeping action follows a fixed rule before the new score, over label, event cue, and scoring worm point are updated.

Status Rules and Bounds

Chase status is rule-based. More urgent terminal states take precedence over rate labels, so a reached target, all-out innings, or completed over allocation is shown before any run-rate comparison.

Negative runs, target, and legal-ball values are treated as zero for calculation. Legal balls can be entered beyond the configured over limit, but balls remaining is then shown as zero and a warning is raised.

Limitations:

This is a scoring aid, not an umpiring aid or an official match system. It records the scoring action selected by the scorer and applies the visible arithmetic rules.

• The no-ball action records the one-run penalty only; add unusual bat runs, byes, penalties, post-no-ball delivery effects, or competition-specific rules through manual correction if needed.
• Rain-adjusted targets, super overs, penalty runs, short-run decisions, retired batters, and detailed dismissal types are outside the available controls.
• The event ledger keeps the latest 80 logged events, so it may not replace a full official scorebook for a long innings.
• Manual edits can make the scoreline differ from the event path, so compare Ball Event Ledger with the current score after corrections.

Worked Examples:

Fast start to a T20 chase

Set Innings to 2nd innings, Target score to 176, and the score to 12/1 after 6 legal balls. Chase Rate Sheet shows 164 runs needed from 114 balls, Required run rate near 8.63 RPO, and Current run rate at 12.00 RPO. The chase can be shown as On rate, but the single early wicket still matters.

Wide in the middle of an over

At 45/2 after 2.3 overs, choosing Wide +1 moves the score to 46/2 and adds a Ball Event Ledger row with a wide cue. The over count remains 2.3 because the delivery did not add a legal ball; the next legal delivery advances the over notation to 2.4.

Quiet overs create rate pressure

In a 20-over chase of 176, a score of 80/4 after 12.0 overs leaves 96 needed from 48 balls. Required run rate becomes 12.00 RPO while Current run rate is 6.67 RPO, so the status changes to Rate climbing. The Scoring Worm should show the flat scoring period that caused the gap.

Setup warning before using a target

If Innings stays on 1st innings while Target score is filled, the warning explains that the target is ignored for chase-rate guidance. Switch to 2nd innings for a chase, or clear the target when the batting side is setting a total.

Advanced Tips:

• Choose Custom and set Over limit before scoring deliveries when a local match uses a shortened innings, otherwise balls remaining and projected score follow the last preset length.
• Keep Legal balls as a raw ball count. Enter 17 for 2.5 overs, not 2.5, because the displayed over label is six-ball notation.
• After a manual correction, compare Ball Event Ledger with the current scoreline so the latest event path still explains the visible total.
• Use Target score as the winning score in the second innings. A side chasing 175 should enter 176, so runs needed and required run rate match the win condition.
• Read Rate climbing together with wickets in hand. A two-run-per-over gap is more urgent when only one or two wickets remain.
• Open Scoring Worm after major momentum swings; a flat run segment, wicket marker, or steep boundary over often explains the current chase label better than the summary alone.

FAQ:

Glossary:

Legal ball

A delivery that counts toward the six balls in an over.

Extras

Runs added to the team total that are not credited as normal batting runs.

Current run rate

Runs scored per over so far, calculated from legal balls.

Required run rate

Runs per over needed from the remaining legal balls in a chase.

Scoring worm

A line chart that plots runs and wickets along the innings event path.

Target score

The score the chasing side must reach to win.

References:

• The over, Marylebone Cricket Club.
• Scoring runs, Marylebone Cricket Club.
• No ball, Marylebone Cricket Club.
• Wide ball, Marylebone Cricket Club.
• Bye and Leg bye, Marylebone Cricket Club.