{{ summaryTitle }}
{{ scoreline }}
{{ summaryLine }}
{{ badge.label }}
Use the name that should appear in the scoreline, tables, chart, and exports.
Keep the label short enough for mobile scoreboards and exported score sheets.
Choose a preset or Custom, then edit the over limit below.
Used for balls remaining and chase pressure. Set Custom format for local match rules.
overs
Use first innings for setting a total or second innings for a chase.
For a chase, enter the winning score, such as 176.
Type a correction or use the delivery buttons below.
Wickets are normalized between 0 and 10 for outputs.
Enter legal deliveries bowled; the output converts them to cricket over notation.
Use legal deliveries, extras, and wicket events while manual fields remain available for corrections.
Use these when a scorer correction is needed.
Aspect Value Scorer note Copy
{{ row.aspect }} {{ row.value }} {{ row.note }}
Metric Value Match cue Copy
{{ row.metric }} {{ row.value }} {{ row.cue }}
Time Over Delivery Runs Score after Cue Copy
No local deliveries logged yet.
{{ row.time }} {{ row.over }} {{ row.delivery }} {{ row.runs }} {{ row.score }} {{ row.cue }} 

          

        

      

    

  

                

                

                    

                        

                            Tags: Game, Productivity
                        

                        

                            Export to PDF
                            Fullscreen
                        

                    

                

            

        

    


                    
        

        

        

            

            
        

        


                                                                                                                                                                                                                                                        
        

        

            
            

                Customize

                

                    

                        

                            
                            
                        


                        

                            
                            
                        


                        

                            
                            
                        

                    


                    

                        Advanced

                        

                            

                                
                                

                                    
                                    
                                

                            


                            

                                
                                

                                    
                                    
                                

                            


                            

                                
                                

                                    
                                    :
                                    
                                

                            


                            

                                
                                

                                    
                                    
                                

                            


                            

                                

                                    
                                    
                                

                            


                            

                                

                                    
                                    
                                

                            


                            

                                
                                
                            


                            

                                
                                
                            

                        

                    

                

            

            
        


        

            
            
            
        


        
        

    

    

        

  

    
Cricket scorekeeping compresses an innings into three facts that must stay aligned: runs scored, wickets lost, and legal balls bowled. A score such as 152/6 (18.3) means the batting side has 152 runs, six wickets down, and 18 overs plus three legal balls completed. In limited-overs cricket, the same line also tells the batting side how much time is left to build a total or finish a chase.

    
The over count is where many casual scoreboards drift. A legal delivery moves the innings forward by one ball. A wide or no-ball adds at least one run but does not count as one of the six balls in the over. Byes and leg byes are extras too, but they usually come from legal deliveries and do move the over count. A useful live board needs to treat those events differently, or run rate and balls remaining become misleading.

    
Scoreboards are decision aids, not complete match records. The scoreline can show whether a chase is ahead of the asking rate, whether wickets are becoming scarce, or whether a projected first-innings total looks competitive. It does not record striker rotation, bowlers, fielding restrictions, Duckworth-Lewis-Stern adjustments, player scorebook detail, or umpire judgments. For official matches, reconcile any quick board against the official scorebook and playing conditions.

    
Good ball-by-ball records are still valuable in practices, local games, watch parties, school matches, and small tournaments. They make corrections easier, preserve how the score moved, and give everyone at the table the same basis for reading the state of the innings.

  






  

    
Technical Details:

    
An innings score is built from delivery events. Runs increase from bat runs, extras, or penalties. Wickets increase when a dismissal is recorded. Overs are not decimal fractions of ten; the digit after the dot is the number of legal balls in the current over, so 7.5 means 47 legal balls, not 7.5 overs.

    
Limited-overs pressure comes from two linked rates. Current run rate describes how fast the batting side has scored so far. Required run rate describes how fast the batting side must score from now on to reach the winning target. Both rates use legal balls, which is why wides and no-balls must be counted carefully.


    

      Diagram showing delivery actions feeding cricket score state, chase rate, ball ledger, and scoring worm outputs.
    


    
Formula Core

    
Run-rate arithmetic converts legal balls into overs by dividing by six. A chase uses the winning target as the score to reach, not the first-innings total itself.

    

      
        
          CRR
          =
          
            R
            B/6
          
        
      
      
        
          RRR
          =
          
            T-R
            (6M-B)/6
          
        
      
      
R is current runs, B is legal balls bowled, M is the over limit, T is the winning target, CRR is current run rate, and RRR is required run rate. The projected score is CRR x M, rounded to the nearest whole run.

    


    
Delivery Counting Rules

    

      

        
        
          

            Event
            Runs added
            Legal ball added?
            Scorer note
          

        
        
          

            Dot ball
            0
            Yes
            The over count advances and the score stays unchanged.
          

          

            +1, +2, +3, Four, Six
            1 to 6
            Yes
            Batting runs increase the score and move the innings by one legal delivery.
          

          

            Wide +1
            1
            No
            The score rises, but balls remaining does not change.
          

          

            No-ball +1
            1
            No
            The basic penalty is added without advancing the over count.
          

          

            Bye +1 or Leg bye +1
            1
            Yes
            The run is an extra, and the delivery still counts as legal.
          

          

            Wicket
            0
            Yes
            Dismissals increase wickets lost and reduce wickets in hand.
          

        
      

    


    
Boundaries And Status Rules

    

      

        
        
          

            Condition
            Output behavior
            Practical meaning
          

        
        
          

            Wickets reach 10
            Wickets in hand becomes 0 and delivery actions stop.
            The innings is treated as all out.
          

          

            Legal balls reach the over limit
            Balls remaining becomes 0 and delivery actions stop.
            The configured limited-overs innings is complete.
          

          

            Second-innings runs reach the target
            The status changes to Target reached and delivery actions stop.
            The chase has reached the winning score entered by the scorer.
          

          

            Required run rate exceeds current run rate by more than 2.00 RPO
            The chase status shows Rate climbing.
            The batting side needs a clear scoring lift from the current pace.
          

          

            Required run rate is at or below current run rate
            The chase status shows On rate.
            Sustaining the current pace is enough by the arithmetic alone.
          

          

            First innings with a target entered
            The target is ignored for chase-rate guidance and a warning appears.
            Target math belongs to the second innings.
          

          

            Negative runs, target, or balls
            The displayed calculations normalize the value to 0.
            Correct the source field before using exported records.
          

        
      

    


    
The built-in extra buttons model simple one-run wides, no-balls, byes, and leg byes. If a delivery includes additional completed runs, penalty runs, a local no-ball rule, or an umpire correction, type the corrected runs, wickets, or legal balls directly before treating the board as the match record.

  






  

    
Everyday Use & Decision Guide:

    
Start with the match shape. Choose T20, ODI, T10, 5-over, or Custom, then confirm the Over limit. For a local match, set Custom before changing the limit so balls remaining, projected score, and chase rate all use the same innings length.

    
Use short team names because the scoreline, tables, chart, and exports all repeat them. Set Innings to 1st innings when a side is setting a total. Set it to 2nd innings and enter the winning Target score when a chase is active. If the first side made 175, enter 176 as the target.

    
The delivery buttons are best for live scoring because they update runs, wickets, legal balls, and the local event list together. Typed fields are better for corrections. If a scorer missed a run earlier, change Runs directly, then read Scoring Worm with care because the final point may reflect a manual correction rather than a logged delivery.

    
    
      
  • Use Innings State when someone needs the current score, overs, current run rate, wickets in hand, and last delivery.
    • 
      
  • Use Chase Rate Sheet during the second innings to compare runs needed, balls remaining, required run rate, current run rate, projection, and wickets in hand.
    • 
      
  • Use Scoring Worm to see how runs and wickets moved through the logged delivery list.
    • 
      
  • Use Ball Event Ledger when a disputed ball needs a quick audit of time, over, delivery type, score after, and chase cue.
    • 
      
  • Use JSON when another workflow needs the scoreline, settings, tables, chart points, and event list in one structured record.
    • 
    

    
A rate badge is not a match prediction. It assumes the current scoring pace continues and it does not know batting order, pitch change, bowler quality, field restrictions, or weather interruptions. Before sharing a result, clear any input warning and compare the visible scoreline with the official table.

  






  

    
Step-by-Step Guide:

    
Use this flow for live scoring, a practice scenario, or a corrected innings snapshot.

    
    
      
  1. Enter Batting side and Bowling side. The summary should show the batting side followed by the current runs, wickets, and over notation.
    2. 
      
  2. Choose Match format. If your match is not T20, ODI, T10, or 5-over, choose Custom and set Over limit to the agreed innings length.
    3. 
      
  3. Set Innings. For a chase, choose 2nd innings and enter the winning Target score; otherwise the required run rate will show as n/a.
    4. 
      
  4. Check the starting Runs, Wickets, and Legal balls. The summary badges should show the same over count and current run rate you expect.
    5. 
      
  5. Record each delivery with the action buttons. Legal scoring buttons advance the ball count, while Wide +1 and No-ball +1 add runs without moving the over count.
    6. 
      
  6. Use Undo last immediately after a wrong delivery click. It restores the score, wickets, and balls to the state before that event.
    7. 
      
  7. Use typed fields for scorer corrections that are not represented by a one-click action. If Check scoreboard inputs appears, fix the warning before copying or exporting.
    8. 
      
  8. Open Chase Rate Sheet during a second-innings chase and compare Required run rate with Current run rate.
    9. 
      
  9. Review Ball Event Ledger and Scoring Worm before sharing the record, especially after manual corrections or disputed extras.
    10. 
    

  






  

    
Interpreting Results:

    
The summary line is the fastest read. In a first innings, it tells you the score, overs, and scoring pace for setting a total. In a chase, it adds runs needed, balls remaining, and required run rate. The badges then add the format, over limit, current run rate, wickets in hand, and chase status.

    
Projected score is rate-based. A side scoring at 9.00 RPO after five overs projects to 180 in a T20, but the projection changes quickly after wickets, dot-ball pressure, or a late boundary over. Use it as a pace cue, not a forecast.

    

      

        
        
          

            Output
            Read it as
            Check before trusting it
          

        
        
          

            Innings State
            The current score, overs, run rate, target state, and last delivery note.
            Confirm manual fields match the real scorebook after corrections.
          

          

            Chase Rate Sheet
            The chase arithmetic for target, runs needed, balls left, required rate, and projection.
            Make sure Innings is 2nd innings and the target is the winning score.
          

          

            Scoring Worm
            A line chart of logged runs and wickets, with a target line during a chase.
            Watch for a final current point that appears because typed values differ from the last logged event.
          

          

            Ball Event Ledger
            The local delivery list with time, over, delivery label, runs, score after, and cue.
            The list is limited to recent local events and is not a full official scorebook.
          

          

            Check scoreboard inputs
            Warnings for values such as wickets over 10, negative numbers, balls beyond the over limit, or missing chase targets.
            Resolve warnings before treating the data as final.
          

        
      

    

    
A good result should be internally consistent: scoreline, innings state, chase sheet, event ledger, and chart should all tell the same story. When they disagree, the usual cause is a manual correction after the last logged delivery.

  






  

    
Worked Examples:


    
Reading a first-innings pace

    
Set Match format to T20, Innings to 1st innings, Runs to 68, Wickets to 2, and Legal balls to 48. The scoreline reads 68/2 (8.0). Innings State shows a current run rate of 8.50 RPO and a projected score of 170 if that pace holds.


    
Checking an early chase

    
Use the sample-style chase setup with Target score at 176, Runs at 12, Wickets at 1, and Legal balls at 6. Chase Rate Sheet shows 164 runs needed from 114 balls. Required run rate is about 8.63 RPO, while current run rate is 12.00 RPO, so the chase status can read On rate. That does not mean the chase is safe; it only says the arithmetic is favorable at that moment.


    
Recording extras without breaking the over

    
Starting from 12/1 (1.0), press Wide +1. The score becomes 13/1, but the over remains 1.0 because the delivery is not legal. Press Bye +1 next and the score becomes 14/1 (1.1), because a bye on a legal delivery advances the ball count.


    
Fixing an input warning

    
If Wickets is typed as 11, the output caps wickets at 10 and warns that wickets are capped. If Legal balls exceeds the selected over limit, balls remaining is shown as 0. Correct the typed value or adjust Over limit before using the chart or exported record.

  






  

    
FAQ:


    

      Does the target mean the first team's score or the winning score?
      
Enter the winning score. If the first innings was 175, set Target score to 176 so Runs needed and Required run rate use the correct chase number.

    


    

      Why did a wide not change the over?
      
Wide +1 adds one run but does not add a legal ball. The score changes, while over notation and balls remaining stay at the previous legal delivery count.

    


    

      Can I score a no-ball with extra bat runs?
      
The quick No-ball +1 action records only the basic one-run no-ball. For a delivery with extra bat runs or local penalties, type the corrected Runs and Legal balls after the umpire's decision is settled.

    


    

      Why is required run rate missing?
      
Required run rate appears only when Innings is 2nd innings, Target score is greater than zero, runs are still needed, and legal balls remain.

    


    

      What does Undo last restore?
      
Undo last removes the newest local delivery event and restores runs, wickets, and legal balls to the values before that event.

    


    

      Is this enough for official scoring?
      
Use it as a live scoreboard and review aid. Official games may require a scorebook, scorer signatures, match regulations, player detail, or adjusted targets that this scoreboard does not replace.

    

  






  

    
Glossary:

    

      
Legal ball

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

      
Over notation

      
The cricket display for completed overs and balls, such as 12.4 for 12 overs plus four legal balls.

      
Current run rate

      
Runs scored per six legal balls so far in the innings.

      
Required run rate

      
Runs per over needed from the remaining legal balls to reach the target.

      
Target score

      
The winning score the chasing side must reach.

      
Extras

      
Runs added to the batting side that are not credited as ordinary bat runs, such as wides, no-balls, byes, and leg byes.

      
Scoring worm

      
A line chart showing how runs and wickets changed across the logged delivery sequence.

    

  






  

    
References: