Latest Players

How to Read a Cricket Player Profile

A player's career rarely fits into a single number. The same batter can average 55 in home Tests and 30 on bouncy away pitches; a bowler can be expensive in T20 yet deadly with the new ball in ODIs. Each profile on Crickpal pulls together the figures that actually matter for a player across formats, so you can judge them on the evidence rather than reputation. This short guide explains what those numbers mean and how to use them.

The batting numbers that matter

• Average — runs scored divided by times out. It rewards consistency and is the classic measure of a batter's worth, especially in Tests.
• Strike rate — runs per 100 balls. In T20 and ODI cricket this can matter as much as the average, because quick runs change matches.
• Hundreds and fifties — how often a player converts a start into a big score. A high fifty count with few hundreds can hint at a batter who gets in but doesn't go on.

The bowling numbers that matter

• Average — runs conceded per wicket. Lower is better; it shows how cheaply a bowler takes wickets.
• Economy rate — runs conceded per over. The headline stat in white-ball cricket, where containing runs is half the job.
• Strike rate — balls bowled per wicket. A low strike rate marks a genuine wicket-taker rather than a holding bowler.

Why format context is everything

The single biggest mistake in reading stats is comparing across formats. Test cricket rewards patience and technique over five days; T20 rewards risk and power across twenty overs. A strong profile is one that holds up in the format being discussed — so always check which format a number belongs to before drawing a conclusion, and weigh recent form alongside the career totals.