How this instrument works
Batting average (AVG) is hits divided by at bats: how often a plate appearance that counts as an at bat ends in a base hit. Walks, hit-by-pitches, and sacrifices are not at bats, so they neither help nor hurt the number — only a ball put safely in play (or out) counts. The result is conventionally written without the leading zero and read aloud as a whole number: .300 is 'batting three hundred,' a mark that has separated a strong offensive season from an ordinary one for well over a century.
What the number leaves out is just as important as what it counts. AVG treats a leadoff single and a game-winning grand slam identically, and it says nothing about a hitter who draws thirty extra walks a year by working deep counts. That is precisely why sabermetrics-minded analysts lean on on-base percentage and slugging percentage alongside it rather than instead of it — AVG answers one narrow question (how often does contact become a hit?) cleanly, and other stats exist to answer the questions it was never built to answer.
Despite decades of more sophisticated alternatives, AVG has never left the box score. It is intuitive, it requires no historical park or era adjustment to read at a glance, and a .300 hitter is still understood the same way by a fan in 1925 or 2026. That durability is the real case for keeping it around: a single, simple number that has meant roughly the same thing for the entire history of the sport.
- Enter Hits — the total official base hits (singles, doubles, triples, home runs).
- Enter At bats — plate appearances that count as at bats, excluding walks, hit-by-pitches, and sacrifices.
- Read Batting average beneath the inputs, shown to three decimal places.
- At bats must be greater than zero, and hits can never exceed at bats — the instrument flags either problem instead of guessing.
Worked example — 180 hits in 600 at bats
Enter 180 into Hits and 600 into At bats. Batting average = 180 / 600 = 0.300 — a full-season line of 'batting three hundred,' the traditional dividing line between a very good offensive season and a merely ordinary one.
Change nothing but the at bats and the number moves a lot: the same 180 hits over a slightly smaller or larger sample would read differently, which is why AVG is normally judged over a full season rather than a handful of games — small samples swing wildly on a stat with no other inputs to smooth them out.
Questions
What counts as an at bat, exactly?
An at bat is a completed plate appearance that results in a hit, an out on a ball in play, or a strikeout. Walks, hit-by-pitches, sacrifice bunts, sacrifice flies, and interference are excluded from at bats entirely, which is exactly why they don't move batting average up or down — the formula never sees them.
What is considered a good batting average?
Historically, .250 has been treated as a rough replacement-level benchmark — a 50-hits-in-200-at-bats pace an everyday player is expected to clear — while .300 or better across a full season marks a genuinely strong hitter. Anything above .320 in modern MLB is typically among the league leaders; averages above .400 have not been sustained over a full season since 1941.
Why do people still care about batting average when OBP and OPS exist?
Because it measures something specific and easy to explain: how often contact turns into a hit. On-base percentage adds walks and hit-by-pitches, and slugging percentage weights extra-base hits — both are more complete pictures of offensive value, but AVG remains the simplest single number for 'does this player make good contact,' which is why it still appears next to the more advanced stats rather than replacing them.
Can batting average ever be higher than 1.000?
No. Hits can never exceed at bats — every hit is, by definition, also an at bat — so the ratio is capped at 1.000, a hypothetical player who reached base with a hit in every single at bat. This instrument enforces that same limit and will flag an entry where hits are typed in as greater than at bats.
Does batting average count walks as hits?
No, and this is the single most common misunderstanding of the stat. A walk is not an at bat and is not a hit, so it has zero effect on batting average in either direction — a hitter who draws forty walks in a season sees no change to AVG from any of them, which is exactly why on-base percentage exists as a separate number.