Baseball season records: what wins, losses, and 162 games mean
An accessible explainer on MLB season length, winning percentage, team strength, and why fictional game results need clear labels.
Why a baseball season uses 162 games
A major-league season gives teams many chances to test their roster across different opponents and ballparks. In a 162-game schedule, a team's record records wins and losses rather than the score of every individual game. A 90–72 record means 90 wins and 72 losses; together those numbers total 162 games.
The length matters because a single result is noisy. A great pitcher can lose after one bad inning, and a team can win a low-scoring game with one late hit. Over a full season, more games give a broader view of a club's performance, though injuries, schedule differences, and random variation still matter.
Reading winning percentage
Winning percentage divides wins by games played. For example, 90 wins in 162 games gives a winning percentage of .556 when rounded to three decimal places. A tie, when a league standings format includes one, is treated as half a win for this calculation. Percentages help compare teams that have played different numbers of games.
A record is easier to interpret with context. The same win total can mean something different early in a season than after all 162 games, and a team's record does not explain run differential, injuries, opponent strength, or how closely it won and lost its games.
Why player quality is hard to compress
Baseball performance comes from different jobs. A hitter contributes through reaching base, advancing runners, and producing extra-base hits. Fielders prevent runs through positioning, range, hands, and throwing. Pitchers have distinct roles and face different workloads: a starter works through several innings, a reliever handles shorter situations, and a closer is often used at the end of a close game.
A roster score compresses those skills into a smaller number so a game can be played quickly. Compression is useful for an arcade draft, but it hides detail. Any simple rating should be treated as a game mechanic rather than an official ranking or complete description of a player.
Using a fictional record responsibly
A game can turn a roster rating into a season record to make a draft feel concrete. That record is a result inside the game model. It does not become a statistical forecast simply because it uses wins, losses, or the familiar 162-game schedule.
A real forecast would need a published method, relevant player projections, playing-time estimates, injuries, team context, schedule, park effects, and uncertainty calibration. A browser game can be entertaining without making that claim: its result should be clearly labeled fictional, explain the rules that shape it, and identify where its data snapshot may be out of date.
Sources and update notes
For current schedules and official standings, consult MLB's schedule and standings pages. For roster moves and player status, consult the club and MLB player pages. A game data snapshot is a convenience for repeatable gameplay; it can lag behind those current sources. This guide explains the general meaning of a 162-game record and does not supply a current standings table.