Data Methodology
How Verixa collects, validates, and calculates every cricket statistic on this site — sources, update frequency, conflict resolution, and formulas.
Where our statistics come from
Verixa uses two primary data sources, each covering a distinct type of statistical information:
One player, one canonical data record
Every player on Verixa is stored as a single record in our cricket_players database table. All pages — player profile, player comparison, head-to-head, rankings — read from this single record.
Statistics are stored as structured JSON objects (batting_stats, bowling_stats, career_stats) fetched from the same API source and parsed through identical accessor methods in the CricketPlayer model. This means the ODI runs shown on a player's profile page are always identical to the ODI runs shown on any comparison page for the same player.
How often statistics are refreshed
Automatically refreshed when a player's profile is visited and their record is older than 7 days. Major active players are refreshed more frequently.
Synchronised via scheduled task. Rankings pages display a "Last updated" timestamp so users can see data freshness at a glance.
Cricsheet match files are imported periodically. Head-to-head and partnership stats reflect the most recently imported Cricsheet dataset.
Calculator logic is static — formulas do not change. Only user input changes the output. Formulas are documented on each calculator page.
How we resolve data conflicts
When statistics differ between sources, Verixa follows this priority order:
- 1Official ICC scorecard — the authoritative record for all official international matches.
- 2Primary scorecard data — match scorecards from verified official cricket boards (BCCI, ECB, PCB, etc.).
- 3Cricsheet — aggregated career statistics and ball-by-ball data used for player profiles and matchup statistics.
- 4Cricsheet ball-by-ball — for derived metrics and matchup statistics.
If you identify a statistical error, please submit a correction and we will investigate and update within 48 hours.
How key metrics are calculated
Batting Average
Not-out innings do not count as dismissals. A player who is never dismissed has an infinite (∞) batting average.
Batting Strike Rate
Bowling Average
Lower is better. A bowler who has conceded runs but taken no wickets has no valid bowling average.
Bowling Economy Rate
Bowling Strike Rate
Measures how many balls a bowler needs per wicket. Lower is better.
Net Run Rate (NRR)
Team Run Rate = Runs Scored ÷ Overs Faced
Opponent Run Rate = Runs Conceded ÷ Overs Bowled
If a team is bowled out before their allotted overs, the full allotment is used in the denominator, not the overs faced.
Required Run Rate (RRR)
Player Score (Verixa proprietary)
+ (Wickets × 3) + (Five-wicket hauls × 30) + (10-wicket matches × 50)
This is a Verixa-internal metric used to rank and prioritise players for display and comparison features. It is not an official ICC metric. It reflects career volume and milestone achievements across all formats.
DLS Calculator scope
The Verixa DLS calculator is an educational explainer. It models the resource percentage concept using the standard DLS resource table. It is not a certified ICC DLS tool and should not be used for official match decisions. Official DLS calculations are performed by licensed software using the complete resource table maintained by the Professional Cricket Statisticians' Association.
Report a statistical error
If you believe any statistic on Verixa is incorrect, please visit our Corrections page or email support@verixa.in. We review all reported errors and publish corrections promptly.