Knowing how many runs a player contributes on the bases is a useful lens for comparing speed, instincts, and aggressiveness.
This calculator lets you plug in the three base running components tracked by FanGraphs: SB Runs, CS Runs, and Extra Bases Taken Runs and instantly converts them into a single Runs Above Average figure.
Enter the numbers, hit calculate, and see where a baserunner stands relative to league average performance.
With this ultimate base running calculator tool, players can easily assess their performance and identify areas for improvement.
By understanding their contributions through stealing bases or taking extra bases, players can refine their strategies and enhance their overall impact on the game.
Ultimately, this analysis encourages more intelligent base running and can lead to increased scoring opportunities for the team.
This metric not only highlights a player’s baserunning prowess but also provides context within the overall offensive contributions to the team.
By understanding how a player’s runs on the bases contribute to their overall value, enthusiasts can appreciate the impact of speed and decision-making in scoring scenarios.
When discussing player efficiency, “offensive runs above average explained” helps clarify how these calculated run values translate to wins and overall team success.
Base Running Runs Above Average
Base Running FAQ
What is Runs Above Average in base running?
It is the sum of the three base running components created by FanGraphs that estimate how many runs a player adds or costs through stolen bases, caught stealings, and advancement on batted balls.
Where can I find the input numbers?
You can locate SB Runs, CS Runs, and Extra Bases Taken Runs on the player page at FanGraphs in the standard batting section under the Base Running tab.
Why can the result be negative?
A negative figure means the runner cost his team runs compared to an average player, often because of poor stolen base efficiency or conservative advancement.
How precise is the calculation?
The formula is exact to three decimal places, matching the level of rounding used by most public leaderboards.
Does this metric include pickoffs or errors?
No, pickoffs and errors are not part of the three components, so their run impact is not captured here.