Stats
Fair ways to track top batters and bowlers across a season, including eligibility rules and public leaderboards.
By CricMatch Editorial · Updated 2026-08-17 · ~566 words
Trophies for the top run-scorer and top wicket-taker motivate players across league stages—not only in the final. Borrowing the popular “orange cap” and “purple cap” idea works well in local tournaments when the math is transparent.
Count only official tournament matches. Decide whether knockouts count, whether rain-reduced games count fully, and whether a player who switched teams mid-season carries stats (usually not). Minimum overs bowled or innings batted can prevent one lucky spell from crowning a champion unfairly—or you may prefer pure totals for simplicity.
Publish the policy on day one.
Update after every match. Players will screenshot standings; make sure those screenshots match the official system. CricMatch leaderboards help organizers avoid spreadsheet version conflicts between scoring volunteers.
Announce midway leaders after the league stage and final winners on presentation night. Mention strike rates or averages as secondary stories so a pure accumulator and an explosive finisher both get recognition when appropriate.
State whether super overs count (usually no for season caps). State whether a player who bowls two balls in a washout gets a wicket if one is taken (usually the official card decides). State whether guest players in exhibition games count (usually no). Put this next to the leaderboard, not in a forgotten PDF.
If two batters finish on the same runs, name the tie-break: innings, average, strike rate, or shared cap. Bowlers: wickets then economy. Publish it before the last round.
One public leaderboard. If a captain maintains a shadow Excel “because the app was wrong in week two”, you will present two orange caps. Fix the official card and move on. CricMatch season stats exist so the presentation night is a readout, not a negotiation.
Screenshot the table after the last league game and again after knockouts if knockouts do not count. Label which screenshot is official.
Suppose Batter A has 240 runs in five innings and Batter B has 240 in seven. If your award is pure runs, they share or you use the published tie-break. If you secretly wanted “better average” you should have said so in week one. Changing the rule when a popular player is behind is how a league loses teams.
Bowlers: 11 wickets at 7.2 economy versus 11 at 5.1. If the cap is wickets only, they tie until the tie-break. Economy as a tie-break rewards control; strike-rate rewards taking wickets in bursts. Pick one and print it under the table.
Do not count practice matches, abandoned games with no toss, or “friendly” midweek games that used the same CricMatch tournament by mistake. Create a separate exhibition tournament if you still want a card.
Print the leaderboard the morning of the final, signed by the scorer. If knockouts do not count, freeze the caps before the first knockout ball. Announce that freeze in the group so a hat-trick in the final does not restart the argument.
Give a small physical token if you can — even a dyed cap — so the award is not only a screenshot. Players remember objects. They forget Excel.
If two names are close, publish both numbers with the tie-break applied. Silence looks like a stitch-up even when the math is honest.