The SQL Pitch Is Ready. Bring on the Strike Bowlers: Cricket Data With 11,000+ Matches and 5 Million+ Balls, Direct SQL on DuckDB and Postgres
Published: November 10, 2026
The cricket database now has South Africa's Test series against Australia, India's T20 series in New Zealand and the ODI tri-series in Pakistan. The latest match in the data is from 2 Nov.
Pakistan beat Sri Lanka in the tri-series final in Lahore, chasing 326. That chase equals the highest in an ODI final, India's 326 against England in 2002, and the 656 runs in the match are the most in any ODI final, per ESPNcricinfo.
For your AI agent
"Go to tigzig.com and let me know what cricket data is available and how to access it"
For you
tigzig.com ➜ Agents & APIs ➜ Database
Credit & Compliance: Data source is Cricsheet (cricsheet.org), licensed ODC-BY 1.0. TigZig is not affiliated with or endorsed by Cricsheet.
A few quick points
▸ The main tables are ball_by_ball (one row per delivery), match_info (one row per match), match_players (the playing XI and officials) and people (the player registry, with ESPNcricinfo IDs).
▸ team1 and team2 do not tell you who batted first. Use the margin columns: winner_runs is filled when the side batting first won, and winner_wickets when the side chasing won.
▸ Venue names were standardised across all matches on 4 Nov, so each big ground now has one name.
tigzig.com/post/cricket-venue-names-standardised-nov2026
Useful links that save time on this data
▸ The 14 things that trip people up:
tigzig.com/post/cricket-database-14-things-that-trip-people-up-sep2026
▸ The SQL functions you can use, and the limits to know about:
tigzig.com/post/cricket-sql-stats-functions-and-limits-sep2026
▸ When an error keeps coming back, the response body usually names the fix:
tigzig.com/post/tigzig-api-error-hints-read-the-body-sep2026
Working on something similar? How I work covers the rates, the availability and what I take on.