Whether you're tracking your kid's Little League season, figuring out your weekend cricket club stats, or settling a friendly debate about who's actually the better hitter—this calculator gives you instant results for both baseball and cricket.

Just pick your sport, plug in your numbers, and you'll have your answer in seconds.

One thing worth knowing upfront: batting average means something completely different in each sport. In baseball, it's about how often you get a hit. In cricket, it's about how many runs you score before getting out. Same name, totally different math. This tool handles both.

Batting average is probably the first stat most players ever learn. It's been around forever, and it answers a pretty simple question: how productive are you when you step up to bat?

In baseball and softball, your batting average tells you what percentage of your at-bats turn into hits. If you're hitting .300, you're getting on base with a hit about 3 times out of every 10 at-bats. That's actually really good—more on that later.

In cricket, batting average works differently. It measures how many runs you typically score before getting out. An average of 40 means you're putting up about 40 runs each time you bat and get dismissed. The higher that number, the more your team can rely on you.

Both versions get at the same basic idea: they smooth out your hot streaks and slumps into one number that shows your consistency over time.

The math is straightforward once you know what goes into it.

Batting Average = Hits ÷ At-Bats

Say you have 45 hits in 150 at-bats:
45 ÷ 150 = .300

Baseball averages always look like decimals—three places after the dot. When someone says a player is "hitting three hundred," they mean .300. Nobody says "zero point three zero zero." It's just baseball shorthand.

Batting Average = Total Runs ÷ Times Dismissed

If you've piled up 856 runs and been dismissed 22 times:
856 ÷ 22 = 38.91

Cricket averages drop the leading zero and often get rounded in conversation. That 38.91 would just be called "an average of 39" at the pub.

Okay, so you've got a number. But is it any good?

Honestly, that depends on where and what you're playing. A .275 average might feel disappointing in Little League but would be perfectly solid in the majors. Context matters a lot here.

The tables below are rough guidelines—not hard cutoffs. Every league is different, and there's plenty of variation. But they'll give you a decent sense of where you stand.

Notice how the "excellent" threshold drops as you move up? That's not a coincidence. Major league pitching is absurdly good. Even the best hitters in the world fail 7 times out of 10. Hitting .300 against MLB pitching puts you in elite company.

T20 averages look lower for a reason. The format demands aggressive batting—you're supposed to swing hard and take risks. Getting out cheaply while trying to clear the rope is just part of the game. In T20, a 25 average with a 140 strike rate is way more useful than a careful 45 average at strike rate 100.

1. Select Baseball from the sport options
2. Enter your hits — that's base hits only: singles, doubles, triples, home runs
3. Enter your at-bats — official at-bats, which excludes walks, HBP, and sacrifices (more on that below)
4. Get your average — shown as a decimal like .285

1. Select Cricket from the sport options
2. Enter your runs — total runs across all your innings
3. Enter dismissals — only innings where you actually got out (not retired, not not-out)
4. Get your average — shown as runs per dismissal, like 34.50

This trips people up more than the actual math. Getting your inputs right is half the battle.

Here's what counts as an official at-bat:

• Any plate appearance that ends in a hit, an out, or an error

Here's what doesn't count:

• Walks (base on balls)
• Hit by pitch
• Sacrifice bunts
• Sacrifice flies
• Catcher's interference

Why exclude those? Because they don't really test whether you can hit. Drawing a walk is great—it gets you on base—but you didn't put bat to ball. Same with getting plunked. These outcomes help your on-base percentage, but they're neutral for batting average.

Dismissals include:

• Bowled, caught, LBW, stumped, run out, hit wicket

Not dismissals:

• Retired hurt
• Not out at end of innings
• Retired not out

This is where cricket averages get a bit weird. If you're frequently not out—say you're a lower-order bat who often runs out of partners—your average might undersell your actual contribution. Those runs count, but you don't add dismissals, so the math looks different than for someone who bats higher up and gets out more often.

The formulas differ because the sports reward different things.

In baseball, you come up to bat multiple times per game—sometimes 4 or 5 plate appearances. The question batting average answers: when you get a chance to hit, how often do you actually come through?

In cricket, you usually bat once per match (sometimes twice in multi-day formats). And you keep batting until you're out or the innings ends. So the question becomes: how many runs can you put up before your turn is over?

This also explains why the numbers look so different. A .300 baseball average and a 40 cricket average are both excellent—but 40 looks way bigger than 0.300. They're measuring fundamentally different things.

Your 11-year-old has 32 hits in 98 at-bats through 18 games.

32 ÷ 98 = .327

That's a strong Little League average—right in the "good" range. Roughly a hit every three at-bats. Not bad at all.

You've been playing Saturdays and notched 287 runs while getting dismissed 11 times. You've also had 3 not-out innings.

287 ÷ 11 = 26.09

For recreational club cricket, that's solid. You're contributing runs most times you go out there. The not-outs don't count as dismissals, so they're helping your average a bit too.

A varsity player has 52 hits in 134 at-bats heading into playoffs.

52 ÷ 134 = .388

That's excellent. Well above the .300 mark that coaches typically look for. This player is getting on base reliably.

You started the season cold: 8 hits in 42 at-bats through April—a .190 average. Rough. But you made some adjustments, and since May you've gone 24-for-58 (.414).

Your overall season line: 32 ÷ 100 = .320

Here's the thing: that .320 doesn't show how far you've come. Sometimes it's worth calculating your average over different stretches to see your actual trajectory.

A club cricketer plays both limited-overs and T20:

• 50-over matches: 412 runs, 14 dismissals = 29.43 average
• T20 matches: 198 runs, 12 dismissals = 16.50 average

That T20 average looks rough, but context matters. If those 198 runs came at a 145 strike rate, this batter is doing exactly what T20 demands—scoring fast, even if it means getting out more often.

Fair warning: this stuff is easier to say than do. But these are the actual levers you can pull.

For Baseball and Softball:

• Put the ball in play. Strikeouts are automatic outs. Contact gives you a chance—sometimes the fielder bobbles it, sometimes you find a gap.
• Be selective early, aggressive late. Work counts in your favor. You'll see better pitches to hit.
• Use the whole field. Hitters who can go the opposite way are harder to defend and harder to shift against.
• Quality over quantity in BP. Mindless hacks don't help. Practice with a purpose.

For Cricket:

• Respect your wicket. Especially early. Build your innings before opening up.
• Know your scoring shots. Under pressure, go to what works—not what looks cool.
• Read conditions. Pitches vary. Adjust your approach instead of fighting reality.
• Work on that one weakness. Whatever gets you out most often—bowlers will find it eventually. Shore it up.

One more thing: batting average isn't everything. It doesn't capture walks, power, clutch hitting, or strike rate. It's a useful piece of the puzzle, but not the whole picture.

This calculator uses the same formulas as MLB and the ICC—the standard approaches for both sports. Your results are only as good as your inputs, though. Make sure you're entering at-bats (not plate appearances) for baseball, and dismissals (not total innings) for cricket.

And remember: batting average is one stat. A useful one, but just one. For the full picture, you'd also want to look at on-base percentage, slugging (baseball), or strike rate (cricket). No single number captures everything about how well someone bats.