In-Match Intel — Coming Soon · CricMetry - T20 Cricket Intelligence

Skip to content

Competitions Teams Players Matchups Leaderboards In-Match IntelUpcoming

Find your next insight.

Search players and teams

Explore the selected competitions

No matching profiles in this context.

Tab to navigate · Enter to open · Esc to close

Loading analytics… The data service may need a moment to wake up.

CRICMETRY.

T20 Cricket, measured differently.

About Cricmetry

Cricket, in context.

About Cricmetry

Cricmetry is a versatile cricket analytics tool for people who want to understand the game beyond the scorecard.

It brings players, teams, competitions and matchups into one place, making it easier to explore performance, spot patterns and ask better cricket questions.

For teams, coaches, scouts and analysts, Cricmetry offers a way to explore player profiles, compare strengths and weaknesses, and examine how performance changes by phase, opposition and bowling style.

For broadcasters, commentators, journalists and content creators, it helps surface the numbers and context behind a cricket story. For fans and curious followers, it makes deeper analysis easier to explore without having to build a spreadsheet from scratch.

Move from league trends to team records, from a player’s overall numbers to specific batting and bowling matchups. Filter by competition and season, explore innings phases, and compare performances with the sample sizes in view.

Our data

Match data comes from Cricsheet, under the Open Data Commons Attribution License (ODC-By). Current coverage focuses on men’s T20 competitions and The Hundred. Coverage varies by competition and reflects the matches Cricsheet supplies; it may not include every match. Analytics use regulation innings and exclude super overs.

Cricmetry is a work in progress. Feedback, ideas and suggestions are always welcome.

Built by Momin Butt, for people who want to turn cricket data into understanding.

About Momin

Momin Butt is a data analyst by profession and a lifelong cricket obsessive.

His work in cricket started long before CricBrief.

Over the years, he has worked across different parts of the cricket ecosystem — mostly through part-time, freelance and contractual roles alongside his wider career in data and analytics.

He has worked as a Cricket Consulting Analyst with Sportradar Australia, contributed as a cricket commentator and writer for ESPNcricinfo, The Roar Sports and Sportskeeda, and worked in cricket analytics and content with Grassroots Cricket, Cricingif and CricWick.

Through these roles, he has had the opportunity to work with and produce insights for people across the cricket industry — including broadcasters, tournament organisers, cricket boards and franchise teams across competitions such as the IPL, PSL and CPL.

At the same time, his full-time career has developed across data science, product analytics and business intelligence.

Today, he works as a Senior Data Analyst at Saudi Telecom Company (stc) in Riyadh, with previous experience in travel tech and hospitality at Agoda in Bangkok.

That combination of two worlds - cricket storytelling and data analytics - is what eventually led him to build CricBrief and other upcoming cricket data products that he is currently working on.

CricBrief is still very much a work in progress, and your feedback, ideas or suggestions would be genuinely helpful.

LinkedIn Email Medium blog

The numbers, in context.

Format-specific phases: T20: overs 1–6, 7–11, 12–16, 17–20. Hundred: legal balls 1–25, 26–50, 51–75, 76–100. Mixed views keep these phase profiles separate.
Regulation innings: Super-over scoring is excluded. Official team records retain tie-break winners. Recorded no-balls count for batting balls faced; wides do not. Neither counts as a legal bowling ball.
Transparent samples: Career batting rates: 300 balls; average: 10 dismissals. Bowling economy: 300 legal balls; average/SR: 15 wickets. Phase: 100 balls, death 60. Style: 75 balls, subtype 40. Matchup rate rankings: 30 balls. Tables show exact contextual thresholds and denominators.
Missing metadata stays missing: Styles use a cached metadata snapshot. Unknown arm is never inferred from bowling subtype; unknown categories remain visible. Player styles describe metadata classifications, not measured delivery variations.
Rate definitions: Batting strike rate is runs per 100 faced balls; bowling economy is charged runs per six legal balls for T20, and per 100 legal balls for Hundred or mixed-format All Leagues. All Leagues sums numerators and denominators before recalculating rates. Style/matchup averages use credited striker dismissals. Zero denominators stay unavailable.
Coverage: Only matches supplied by the official Cricsheet Men → New CSV archives are included. Coverage is not historically complete for every competition. Source season labels stay exact; no missing matches or metadata are inferred.

Match data: Cricsheet — licensed under the Open Data Commons Attribution License (ODC-By).

Coverage varies by competition