About CricChase

Live scores, scorecards, fixtures and results, plus a permanent statistical record of every match in the database — players, teams, venues, competitions, records and the tools to compare them.

• People who want to know the score, quickly, on a phone, on a bad connection.
• People looking something up — a career record, a head-to-head, what happened in a match years ago.
• People who want to go further: compare players under specific conditions, look at a batter’s record against one bowler, or work out what a team needs to qualify.

The first group is why the home page opens with scores rather than a headline. The second is why URLs never change once published. The third is why the tools compute rather than estimate.

• Correct beats fast.Cricket arithmetic has traps — overs are not decimals, a wide is not a ball, a run out is not the bowler’s wicket. The site is built so those cannot be got wrong, including at the database level.
• Say what is uncertain.An estimate is labelled an estimate. A stale feed says it is stale. A points table computed without a competition’s own regulations says so. A page with too little data to be meaningful says that too.
• Original work only. Nothing here is scraped or copied from another cricket site. Data sources sets out exactly what that means.
• Readable without permission. No account is needed for anything essential. Scores, scorecards and statistics work signed out, and largely work without JavaScript.
• Advertising should not damage the product. Ads are labelled, never placed against navigation or score controls, never styled to resemble match cards, and reserve their space so they cannot push a scorecard around while you are reading it.

Corrections are the most useful thing you can send — report one here. For anything else, use the contact page.