Batting Average Calculator

What batting average measures

Batting average is the share of at-bats that end in a hit. A player who collects 34 hits in 100 at-bats is batting .340, which reads as a 34 percent success rate at the plate. It is the oldest and most quoted hitting statistic in baseball, printed on trading cards and scoreboard graphics for more than a century, and it is still the number most fans reach for when comparing hitters at a glance.

The scale runs in thousandths. A .250 hitter gets a hit once in every four at-bats, a .300 hitter once in roughly every three and a third, and a .200 hitter once in every five. Those gaps look small in percentage points, but across a full season of about 500 at-bats the difference between .250 and .300 is close to 25 extra hits, which is the distance between a bench bat and a lineup regular.

This calculator divides hits by at-bats, shows the same number as a percentage, and reports how many additional hits a player needs to reach a target such as .300. The MLB glossary entry for batting average uses the same definition this calculator applies.

The formula and what counts as an at-bat

The formula is batting average = hits / at-bats. Scorekeepers write the result to three decimals and drop the leading zero, so 0.321 becomes .321. The third digit matters because a full season produces hundreds of at-bats, and one point of average over 500 at-bats is 5 hits.

Several plate appearances do not belong in at-bats, and leaving them in is the most common error people make by hand:

• Walks, called or intentional, are not at-bats.
• Hit-by-pitches are not at-bats.
• Sacrifice bunts and sacrifice flies are not at-bats.
• Reaching base on an error or on a fielder's choice counts as an at-bat but never as a hit.
• Catcher's interference is excluded from both counts.

If you only know plate appearances, subtract the excluded events first. A player with 600 plate appearances, 70 walks, 8 hit-by-pitches and 6 sacrifice flies has 600 - 70 - 8 - 6 = 516 at-bats. Dividing his 158 hits by 600 would report .263, when the correct average is 158 / 516 = .306.

Worked examples step by step

Example 1: a veteran finishes the season with 178 hits in 554 at-bats. The average is 178 / 554 = .321, or 32.1 percent. Example 2: a rookie records 96 hits in 420 at-bats, so the average is 96 / 420 = .229. Example 3: a pinch hitter collects 12 hits in 40 at-bats, which computes to 12 / 40 = .300.

The pinch hitter line shows why sample size matters. Over 40 at-bats, one hit moves the average by 1 / 40 = .025, a swing of 25 points. Over 554 at-bats the same hit moves it by roughly .002. That is why April standings fill up with .400 hitters who finish the year near .270: early counts are too small to trust.

Reading the scale: benchmarks from .200 to .400

Because averages cluster in a narrow band, the third decimal carries most of the meaning. Major League Baseball's league-wide average has generally landed between .240 and .260 in recent seasons, so the bands below are graded against that middle.

The .200 mark is known as the Mendoza line, a name borrowed from shortstop Mario Mendoza, whose career average settled around .215. A regular who finishes below it usually loses the starting job. At the other end, .300 remains the accepted line for a star season even as league offense rises and falls: in high-offense years a .300 average is good but not rare, while in pitcher-friendly years it can lead the league.

Batting average against OBP and slugging

Batting average treats a walk as if it never happened and a home run as if it were a bunt single. Modern analysis therefore keeps two companion statistics beside it.

A hitter with 160 hits, 60 walks and 6 hit-by-pitches in 520 at-bats and 4 sacrifice flies has an on-base percentage of (160 + 60 + 6) / (520 + 60 + 6 + 4) = 226 / 590 = .383 while batting .308. The 75-point spread between the two numbers is the value of his patience, which the average alone never shows.

Extra-base power needs the third row. If those same 160 hits produced 250 total bases, his slugging percentage is 250 / 520 = .481 and his OPS is .383 + .481 = .864. Two players can bat an identical .280 and sit 100 points apart in OPS, which is why team builders rarely judge hitters on the average by itself.

Famous averages and the record book

Ted Williams hit .406 for the Boston Red Sox in 1941, and no player has finished a season at .400 or better since. Rogers Hornsby's .424 for St. Louis in 1924 stands as the modern National League record, and Hugh Duffy's .440 in 1894 remains the recognized all-time single-season mark. On the career side, Ty Cobb's .366 across 24 seasons is still the standard.

Close calls underline how hard .400 is. George Brett hit .390 in 1980 and Tony Gwynn hit .394 in the strike-shortened 1994 season, and both fell short in the final weeks. A hitter needs two hits in every five at-bats for six months, against pitching that adjusts after every series.

The National Baseball Hall of Fame keeps the verified seasonal and career leaderboards, and they are worth a check before repeating a number you half remember, because record claims shift with cutoffs and era rules.

Common mistakes and limits of the stat

• Counting walks or sacrifice flies in at-bats, which pushes the average down.
• Dividing by plate appearances instead of at-bats.
• Stopping at two decimals. .32 hides real differences that .324 and .326 expose.
• Comparing eras directly. A .330 average in the dead-ball era and a .330 today describe different rules, pitching and equipment.
• Judging a hitter on 30 at-bats, where one good week looks like a breakout.
• Forgetting that errors count as at-bats, so a fast runner who reaches on mistakes is not hitting .350 on contact.

The stat also has a structural blind spot: it weights every hit the same. A .280 hitter who lines doubles into the gap can be worth more runs than a .300 singles hitter, which is why slugging and on-base percentage belong in the same conversation. For other ratio work, the site's winning percentage calculator, average calculator, and percentage calculator apply the same hits-divided-by-attempts logic in other settings.

All calculations run in your browser, and nothing you type is uploaded or stored.