Understand runs, wickets, overs, and extras.

A cricket scorer records the match state one delivery at a time. The visible score is usually written as runs for wickets, such as 64/3. That means the batting team has scored 64 runs and lost 3 wickets. The scorer also tracks overs, balls in the current over, the batting side, the bowling side, the innings, the target in a chase, and the final result after the match ends.

Runs can be scored by hitting the ball and running, by hitting a boundary, or through extras. A four is normally awarded when the ball reaches the boundary after touching the ground. A six is normally awarded when the ball crosses the boundary without touching the ground. Local cricket can have field-specific rules, so teams should agree those details before the first ball.

GV Cricket is built around this same match state. The scorer taps each event, the live scoreboard updates, spectators can follow a shared link, and finished matches can become result pages with the final score and match summary.

An over is normally six legal balls. A legal ball moves the over forward. Wides and no-balls add runs to the batting side but usually do not count as legal balls, so the bowler must bowl an extra delivery. That is why an over can show more than six total deliveries when extras are included.

Byes and leg byes are different from wides and no-balls. They can add runs when batters run after the ball passes the batter or deflects from the body, depending on the situation and local playing conditions. In a scorecard, extras matter because they affect the team total while keeping batter and bowler figures clear.

For local matches, the most important habit is consistency. Decide how strict wides, no-balls, waist-high full tosses, free hits, boundary values, and retired batters will be handled before the match. Then score every team with the same rules.

A live scoreboard is only useful when it follows the scorer accurately. Each scoring tap should answer a simple question: did the batting team add runs, did a wicket fall, did a legal ball happen, and did the innings or match state change? When those pieces are correct, the score, wickets, overs, current over, target, and result can all stay synchronized.

GV Cricket connects the scoring rules to the match tools. Simple mode focuses on fast team scoring when a local match needs speed. Advanced mode adds player names, batting stats, bowling figures, and richer overlays when the scorer wants a fuller scorecard.

The same data can power spectator links, cricket scoreboard overlays for OBS or PRISM Live, score announcements, sound effects, and match result pages. That helps clubs, schools, leagues, and streamers run a cleaner match day without switching between separate scorekeeping tools.

Local cricket often uses short overs, limited batters, retired batter rules, custom boundaries, smaller fields, indoor nets, or tennis-ball conditions. These changes are normal, but they should be written down or announced before play starts. Clear rules prevent disputes when the score is close.

For tournament matches, decide whether net run rate, super overs, player stats, substitutions, and incomplete matches matter. For school and community games, decide how new players rotate through batting, bowling, wicket keeping, and umpiring. For streams, decide who controls the scoring phone and who watches the overlay.

The goal is not to make every local match feel like a professional broadcast. The goal is to keep the score trusted, visible, and easy to share. GV Cricket supports that by keeping live scoring free and by giving every match a path from setup to live score to final result.