Speed has always been the most visible tool on a baseball field and the hardest to value. A runner who flies from first to third makes the crowd gasp, but the box score records only “single, runner to third,” and the next day’s stat line says nothing about the legs that made it happen. For a century, speed lived in scouting adjectives and stolen-base totals — a crude and incomplete ledger. Statcast changed that on the input side by clocking raw foot speed directly, and modern baserunning metrics changed it on the output side by converting that speed, and the reads behind it, into runs. Put the two together and you can finally answer the old question honestly: what is a fast player actually worth?

This is the story of two numbers that bracket the same skill. Sprint speed measures the raw tool — top-end velocity in feet per second. Baserunning runs measure what a player does with it — the value, in runs, that his legs and instincts add on the bases. The gap between them is where the interesting players live.

Sprint speed: feet per second, measured at full effort

Statcast defines sprint speed as a player’s peak running velocity, in feet per second, measured over his single fastest one-second window on plays where he is plainly trying. A steal attempt, a ball in the gap, a sprint out of the box on a likely extra-base hit — those qualify. A jog to first on a routine grounder does not, because it tells you nothing about top-end speed. A player’s reported figure is the average of his qualifying maximum-effort bursts: his ceiling, sampled repeatedly, not his pace on a lazy afternoon.

Restricting the measurement to full-effort plays is what makes it trustworthy. The system is not asking how fast a player chooses to run on a meaningless play; it is asking how fast he can run when it counts, and averaging those moments to smooth out the noise of any single sprint.

What counts as elite: the “bolt” and the thirty-foot line

The shorthand that grew up around sprint speed is the bolt — any qualifying run at or above roughly thirty feet per second, the threshold the system uses to flag genuinely elite straight-line speed. The fastest players in the league live right around or just above that thirty-foot mark and rack up bolts by the dozen; the league-average qualifying runner sits meaningfully below it; and most players record few bolts or none.

Treat thirty feet per second as a well-established approximate landmark rather than a precise constant. The exact league average drifts year to year, and the honest read on any single figure is “elite,” “average,” or “below average” rather than over-trusting the decimal. A player a hair over thirty is special; one well under the average is a station-to-station runner whatever the box score says.

Author to-do: insert the current-season Statcast Sprint Speed leaderboard here (fastest players in ft/sec, with bolt counts) and the matching FanGraphs baserunning-runs (BsR) leaders, from Baseball Savant and FanGraphs. Do not estimate specific players’ speeds or run values; pull the live numbers.

Why speed isn’t baserunning value

Here is the crucial gap: sprint speed measures top-end velocity and nothing else. It says nothing about how a player uses that velocity. The first-step acceleration, the read on a pitcher’s move, the jump out of the batter’s box, the decision to test an outfielder’s arm, the angle a runner takes rounding a base — none of that is in the speed number. Top-end velocity is the engine; reads, jumps, and decisions are the steering, and a player can have a powerful engine bolted to terrible steering.

Consider a clearly-illustrative, hypothetical pair. Runner A posts a sprint speed comfortably in bolt territory — genuine top-of-the-league wheels — but breaks late on steal attempts, misreads fly balls off the bat, and runs his team into outs on the bases. Runner B is only a tick above average on the readout but reads pitchers like he wrote the scouting report, gets enormous jumps, and takes the extra base at every honest opportunity. By raw speed, A is the superior athlete. By baserunning value, B is the superior player. The tool and the production point in opposite directions, and only the outcome metrics — or a very patient set of eyes — can tell you which is which.

From speed to runs: BsR and baserunning runs

The output side of the ledger is a family of metrics that convert baserunning events into runs above or below average. On FanGraphs this rolls up into BsR (Base Running), expressed in runs, and it is built from a few components that together capture everything a runner does once he’s on base.

The first component values stolen bases and times caught stealing against a break-even standard. This is the part most people already intuit, but the accounting is stricter than the raw totals suggest: a stolen base is worth a fraction of a run, but a caught stealing is a costly out that erases a baserunner, and the cost of getting caught is larger than the reward of a successful steal. That asymmetry sets a break-even success rate — steal often enough to clear it and you add runs; fall below it and your “aggressiveness” is quietly bleeding value, no matter how many bags you swipe.

The second and often larger component values baserunning beyond steals — going first-to-third on a single, scoring from second on a base hit, tagging up, advancing on a ball in the dirt, and avoiding outs on the bases. This is where instincts and reads cash in, and where a merely fast runner with poor judgment can post a negative figure by making outs at third or getting doubled off. Summed and expressed against a league-average baseline, the components yield a single runs figure: how many runs this player’s baserunning added or cost compared with an average runner.

BsR then folds into the broader value framework. It is one of the additive components of FanGraphs WAR, sitting alongside batting and fielding — the formal way a player’s legs show up in his all-in value. For how those pieces combine into a single wins figure (and why two sites compute it differently), see our explainer on why WAR differs by site.

BsR ≈ ( stolen-base / caught-stealing runs vs. break-even ) + ( other baserunning advancement runs )

The same done-versus-deserved frame

The cleanest way to hold all of this together is the done-versus-deserved frame that runs through modern analysis. Sprint speed is the input — the quality of the raw tool, the engine. BsR is the outcome — what the player actually produced with it on the bases. When the two agree, the story is simple: a fast player who runs well, or a slow one who doesn’t. When they diverge, you have learned something specific — either a burner is wasting his wheels through bad reads, or an ordinary-speed player is squeezing real runs out of ordinary legs through instinct and timing. This is the same logic that connects barrel rate to slugging on the hitting side, and it is the right way to read every tool-versus-result pair Statcast produces.

The defensive and range side

Speed doesn’t stop being valuable when the player takes the field — it just feeds a different outcome metric. Sprint speed is a direct input to defensive range: a fielder who covers more ground in the same time reaches batted balls a slower fielder cannot, turning more of them into outs. That is exactly what Outs Above Average is built to measure — it folds a fielder’s speed, his jump, and the difficulty of each play into a single runs-saved figure. In effect, OAA is sprint speed and reads combined on the defensive side and translated into runs, the same way BsR does it on the bases.

And the same caveat applies in both directions: raw speed sets the ceiling, but the jump, the route, and the read determine how much of that ceiling becomes outs (in the field) or extra bases (on the paths). A center fielder with elite sprint speed and poor first-step reads will trail a slower fielder with great instincts in OAA, just as the fast-but-clueless baserunner trails the heady one in BsR. For the wider tour of how Statcast clocks raw tools — speed, pop time, and arm strength — see our overview of Statcast’s athleticism metrics.

The bottom line

Sprint speed finally put an honest number on baseball’s most visible tool: peak velocity in feet per second, measured on full-effort plays, with the bolt and the thirty-feet-per-second line marking elite — an approximate landmark, not a precise constant. But speed is only the engine. Baserunning runs, BsR, measure the steering: stolen-base value against a strict break-even, plus the larger ledger of taking the extra base without making outs, summed into runs and folded into WAR. The same legs feed defensive range through OAA. Read the input and the outcome together, and the divergences are the whole point — a burner can waste his wheels, and a heady runner can out-earn faster men. The radar on a player’s legs is the start of the report. What he does with that speed, in runs, is the verdict.

Sources & Further Reading

  • Baseball Savant — the Statcast Sprint Speed leaderboard, the bolt threshold, and the underlying tracking methodology.
  • FanGraphs Library — the definition of BsR (Base Running) and its stolen-base and advancement components, and how it folds into WAR.
  • MLB.com — the official Statcast glossary entries for sprint speed and bolts.