Base Running Calculator
Base Running Calculator
Number of successful stolen bases in the season or period
Number of times caught attempting to steal a base
Enter Stolen Base Stats
Input your Stolen Bases (SB) and Caught Stealing (CS) to see your SB%, run value (SBR), break-even analysis, and performance rating.
Stolen base percentage, run value, and wSB with seasonal constants
Base running is one of the most underappreciated aspects of baseball analytics. While home runs and batting averages dominate casual conversation, the ability to steal bases efficiently — and the run value generated or surrendered in the attempt — plays a meaningful role in determining how many runs a team scores over the course of a season. The Base Running Calculator gives players, coaches, fantasy managers, and sabermetrics enthusiasts a precise, data-driven view of stolen base effectiveness using both simple and advanced metrics rooted in FanGraphs methodology. At its core, Stolen Base Percentage (SB%) tells you what fraction of steal attempts are successful. A runner who steals 70 bases and is caught 10 times has an SB% of 87.5%, which is elite. But SB% alone does not tell the whole story. What matters from a run-value perspective is whether the successful steals produce more run value than the caught stealings cost. This is where Simple Stolen Base Runs (SBR) and Weighted Stolen Base Runs (wSB) come in. SBR uses a straightforward linear weights formula: each successful steal contributes approximately +0.3 runs, while each caught stealing costs approximately −0.6 runs. These coefficients reflect decades of play-by-play analysis showing that removing a baserunner (especially a fast one who was likely to advance) is roughly twice as costly as a successful steal is beneficial. The equilibrium point — where SBR equals zero — occurs when a player steals exactly twice as many bases as they are caught. This translates to a break-even SB% of approximately 66.67%, or two successes for every failure. The advanced metric, wSB (Weighted Stolen Base Runs), is FanGraphs' more sophisticated version. It accounts not only for the direct cost and benefit of steal attempts but also for the opportunity cost: a team with more baserunners on first in steal-eligible positions has more chances to attempt, so the league average SB contribution is subtracted from the player's total opportunities. The formula is: wSB = (SB × runSB) + (CS × runCS) − (lgwSB × (1B + BB + HBP − IBB)). This places each player's stolen base contribution on a runs-above-average scale, making it easy to compare across seasons and eras. The seasonal constants used in the wSB formula — runCS and lgwSB — change year to year because the overall run environment shifts. In high-scoring seasons, the penalty for a caught stealing is larger (more runs surrendered per out), meaning the break-even threshold rises slightly. This calculator embeds verified seasonal constants from 2015 through 2025, allowing you to evaluate a historical season accurately by selecting the appropriate year. For fantasy baseball players, understanding wSB provides a genuine edge. A base stealer with a 60% SB% might look productive based on raw stolen base totals but is actually costing their team runs. Conversely, a player who only attempts steals when they are very likely to succeed — even with lower volume — may contribute more net run value. This calculator surfaces that distinction instantly. Coaches and analysts can use the break-even feature to set minimum performance thresholds. If a runner has been caught stealing 12 times in a season, they need at least 24 successful steals just to break even on run value. Knowing this in real time allows coaching staff to make more informed decisions about when to send runners and which players add or subtract value through their base running decisions. The CSV export feature makes it easy to track multiple players across a season. Enter each player's stats, export the results, and maintain a spreadsheet of base running contributions alongside your other offensive metrics for a complete picture of offensive value.
Understanding Base Running Metrics
What Is Stolen Base Percentage (SB%)?
Stolen Base Percentage is the ratio of successful stolen base attempts to total stolen base attempts, expressed as a percentage. A player with 30 stolen bases and 10 caught stealings has an SB% of 75%. The metric has been tracked in baseball since the late 19th century and remains the most common summary statistic for evaluating a base stealer's raw efficiency. In modern sabermetrics, SB% is primarily useful as an input to more comprehensive run-value metrics like SBR and wSB rather than as a standalone performance measure. The critical benchmark is 66.67%: below this threshold, stolen base attempts are net-negative in terms of expected run value, meaning the runner is hurting the team more than helping it by attempting to steal.
How Is wSB Calculated?
Weighted Stolen Base Runs (wSB) is computed using the formula: wSB = (SB × runSB) + (CS × runCS) − (lgwSB × (1B + BB + HBP − IBB)). The constants runSB (0.2) and runCS (approximately −0.38 to −0.40 depending on the season's run environment) represent the linear weight of each event. The lgwSB term adjusts for league average: it is the league-wide SB run value per steal opportunity, multiplied by the player's own opportunities (singles plus walks plus hit-by-pitches minus intentional walks). This subtraction converts the raw run contribution into a runs-above-average figure. A wSB of zero means the player contributed exactly what an average runner would have from the same set of opportunities.
Why Does Base Running Value Matter?
Base running value feeds directly into Wins Above Replacement (WAR). Specifically, wSB is one component of BsR (Base Running Runs), alongside UBR (Ultimate Base Running, which captures non-steal advancements) and wGDP (weighted Grounded into Double Play Runs). Each additional run a team produces translates to approximately one-tenth of a win over the course of a season. An elite base runner generating +10 wSB across a season — think players like Billy Hamilton, Rickey Henderson, or Trea Turner at his peak — is contributing roughly one full win above average through stolen base efficiency alone. This is a substantial and often overlooked source of offensive value that is invisible in traditional box scores.
Limitations and Caveats
The seasonal constants embedded in this calculator are estimates based on published FanGraphs run environment data. For exact research-grade values, consult the FanGraphs Guts page for the precise runCS and lgwSB constants for each season. Additionally, wSB captures only stolen base run value — it excludes non-steal baserunning plays (covered by UBR) and double-play avoidance (covered by wGDP). For a complete BsR estimate, you would need to add those components. Small sample sizes also limit the predictive value of these metrics: a player with only 10 stolen base attempts in a season is subject to wide variance, and their wSB may not be representative of true talent level. Multiple seasons of data provide more reliable estimates of a runner's true base running ability.
How to Use This Calculator
Choose Simple or Advanced Mode
Use Simple mode for a quick SB% and SBR calculation with just stolen bases and caught stealing totals. Switch to Advanced mode when you want the FanGraphs wSB metric, which requires singles, walks, hit-by-pitch, intentional walks, and a season year selection.
Enter Your Stolen Base Stats
Type in the number of Stolen Bases (SB) and Caught Stealing (CS) for the player or period you are evaluating. These can be season totals, career totals, or a partial-season split — the calculator works for any sample size, though larger samples yield more reliable ratings.
Review the Break-Even Analysis
The results show your SB% against the 66.67% break-even threshold. If your SB% is below this line, the base stealing is costing your team runs. The 'additional steals needed' figure tells you exactly how many more successful steals are required to reach zero SBR given your current caught stealing total.
Export and Track Over Time
Use the Export CSV button to download your results. Track multiple players or month-by-month splits in a spreadsheet to build a comprehensive view of base running contributions across a roster or across a full season.
Frequently Asked Questions
What stolen base percentage do you need to add value?
The break-even threshold for stolen base attempts is approximately 66.67%, or two successful steals for every one caught stealing. This figure comes from linear weights analysis: a successful steal adds roughly +0.3 runs and a caught stealing costs roughly −0.6 runs. Since the cost is twice the reward, a runner must succeed at least twice as often as they fail to produce net-positive run value. A player with a 60% SB% is actually hurting their team in terms of expected runs, even if their raw stolen base total looks impressive on a traditional stat sheet.
What is the difference between SBR and wSB?
SBR (Simple Stolen Base Runs) uses fixed coefficients (0.3 per SB, −0.6 per CS) to estimate the direct run value of stolen base events. It is easy to compute and works well for quick analysis. wSB (Weighted Stolen Base Runs) is FanGraphs' more rigorous version. It uses seasonally adjusted constants and subtracts the league-average SB contribution relative to the player's opportunities (singles, walks, HBP minus intentional walks). This converts the result to runs above average rather than runs above zero, enabling fair comparisons across different run environments and seasons.
Why does the runCS constant change by season?
The runCS constant represents the run cost of a caught stealing, and it varies because it is derived from the season's overall run environment. Specifically, runCS = −(2 × RunsPerOut + 0.075), where RunsPerOut is total league runs divided by total league outs for that season. In high-scoring offensive environments, each out surrendered costs more in expected run value, so the caught stealing penalty is larger. The lgwSB constant similarly adjusts to reflect how much value an average runner generates per opportunity in that specific season. This calibration ensures wSB comparisons remain meaningful across different offensive eras.
What counts as a steal opportunity for wSB?
In the wSB formula, steal opportunities are defined as: singles (1B) + walks (BB) + hit-by-pitches (HBP) − intentional walks (IBB). Intentional walks are excluded because a batter who receives an intentional walk is being pitched around intentionally — the defense has decided to put them on base — so it does not represent a typical base-on-balls situation where the runner might have been expected to attempt a steal. This set of events captures the situations where a runner is most commonly on first base in a position to potentially attempt a steal.
How does wSB relate to WAR?
wSB is one of three components of BsR (Base Running Runs), which feeds into position player WAR calculations. BsR = wSB + UBR + wGDP, where UBR measures run value from non-steal baserunning decisions (taking the extra base on hits, avoiding outs on the basepaths) and wGDP measures the run impact of grounding into double plays relative to average. BsR represents the total baserunning contribution in runs above average. Since roughly 9–10 runs above replacement equals one additional win, a player with a BsR of +5 is contributing approximately half a win through baserunning alone compared to a league-average runner.
Is a high stolen base total always a good thing?
Not necessarily. A player who steals 40 bases while being caught 25 times has an SB% of 61.5%, well below the 66.67% break-even threshold. In SBR terms, that player contributed 0.3 × 40 − 0.6 × 25 = 12 − 15 = −3 runs: they cost their team three runs. Meanwhile, a player who steals only 20 bases with 5 caught stealings has an 80% SB% and an SBR of +0.3 × 20 − 0.6 × 5 = 6 − 3 = +3 runs. The high-volume stealer with poor efficiency is actually less valuable from a run-production standpoint than the selective stealer with high efficiency.