Runs Created Calculator — Bill James Basic RC

Background.

Runs Created was Bill James's answer to a question the box score had never answered: of the runs a team scored, how many can be attributed to a particular batter? Runs and RBIs cannot answer it, because both depend heavily on the batters around him — a leadoff man scores when somebody else drives him in, and a cleanup hitter drives in runners somebody else put on. Runs Created works only from what the batter himself did.

The basic formula has three parts and is short enough to do in your head with a calculator: (H + BB) × TB ÷ (AB + BB). The first bracket is what James called the on-base factor — the number of times the batter reached base. The middle term, total bases, is the base-advancement factor. The denominator, at-bats plus walks, is the opportunities factor. Rearranged as (H + BB) ÷ (AB + BB) × TB, the structure is clearer still: a rate of getting on base, multiplied by how far the batter moved runners. That multiplicative structure is what distinguishes Runs Created from every modern linear-weights estimator, which instead assigns a fixed run value to each event and adds them up.

The reasoning underneath it is a genuine identity, not a curve fit. In any window at least as long as an inning, plate appearances must equal outs plus runners left on base plus runs. So a team scores by earning more plate appearances than it makes outs, and by stranding fewer of the runners it earns. Getting on base drives the first term; advancing runners drives the second. Runs Created is that observation turned into arithmetic.

This page implements the basic version and only the basic version, and it is worth saying why. James published at least four Runs Created families over the years — the basic one, one that folds in stolen bases and caught stealing, a technical version adding sacrifices, hit-by-pitches and double plays, and a further technical version incorporating strikeouts. The 2025 Baseball Research Journal survey that this page's formula is sourced to describes all four but prints the later variants' factor definitions as images, and independent renderings of the stolen-base version disagree about whether caught stealings belong in the denominator. Rather than guess at a factor, the page narrows to the version whose definition is unambiguous. That is not a purely defensive choice: the same study found the basic version to be the most accurate of the four when applied to team totals.

Alongside the run total the calculator gives all three factors separately, the batting outs behind the line, and runs created per 27 batting outs — the rate that answers "what would a lineup of nine of this player score in a game?". Both the formula and the implementation are checked against the two worked figures the source article prints, and both reproduce exactly, which is the strongest confirmation available that this page and the published formula agree.

What is runs created calculator?

Runs Created is a run estimator invented by Bill James that converts a batter's box-score line into an estimate of the runs his performance produced. The basic version is RC = (H + BB) × TB ÷ (AB + BB), built from three named factors: an on-base factor of hits plus walks, a base-advancement factor of total bases, and an opportunities factor of at-bats plus walks. It is deliberately multiplicative rather than additive, on the logic that reaching base and advancing runners are complementary rather than independent — a team full of singles hitters who never advance anybody scores far less than the sum of its parts suggests, and a team of home run hitters who never get on base scores far less too. Because it works only from events the batter controlled, it does not reward or punish him for his teammates' performance, which is exactly the flaw in runs scored and runs batted in that it was designed to fix. Its main limitations are equally well known: applied to a single extreme hitter it overestimates, because a great hitter never gets to bat behind himself; the basic version cannot see stolen bases, hit-by-pitches, sacrifices or double plays; and it is not park- or league-adjusted, so a Coors Field season and a pitcher's-park season are not directly comparable. The modern successors are weighted runs created (wRC) and wRC+, which FanGraphs describes explicitly as improved versions of James's statistic.

How to use this calculator.

1. 01Enter at-bats and hits from the box score or season line. Do not substitute plate appearances for at-bats — walks are counted separately, and double-counting them inflates the opportunities factor.
2. 02Enter walks. Include intentional walks; the basic formula makes no distinction between them.
3. 03Enter total bases. If you only have the hit breakdown, total bases are singles + 2 × doubles + 3 × triples + 4 × home runs. The calculator rejects a figure below the hit total or above four times it, because both are impossible.
4. 04Read the three factors alongside the result. They are where the diagnosis lives: two players with identical runs created can arrive there from a high on-base factor and modest bases, or the reverse, and those are very different hitters.
5. 05Use runs created per 27 batting outs to compare players with different playing time. Runs created is a counting statistic, so a full-time average hitter will beat a part-time excellent one; the per-27 rate removes that.
6. 06Do not add up individual players' runs created and expect the team's actual run total. Applying the formula to team totals is materially more accurate than summing individual results, and the difference is not small.

The formula.

Take the three factors one at a time.

The on-base factor, H + BB, counts the times the batter put himself on base by the two routes the basic version can see. Note what is missing: hit-by-pitch and reaching on error are not in it, the first because James's later variants handle it and the basic one does not, the second because reaching on an error is not a batter accomplishment in the scorer's judgement.

The base-advancement factor is total bases: a single is one, a double two, a triple three, a home run four. This is what stops the formula treating a singles hitter and a slugger with identical on-base rates as identical players.

The opportunities factor, AB + BB, is the plate appearances the formula sees. Divide the on-base factor by it and you have an on-base rate; multiply that rate by total bases and you have Runs Created. Written that way — RC = (A ÷ C) × B — the design is transparent: it is not a weighted sum of events but a rate times a magnitude.

Why multiplicative? Because runs come from two things happening together. In any period at least as long as an inning, plate appearances equal outs plus men left on base plus runs, which rearranges to say a team scores by having more plate appearances than outs and by stranding fewer of the runners it creates. Reaching base drives the first; advancing runners drives the second; and neither produces runs without the other. A team that reaches base constantly but never advances anybody strands them all, and a team that advances brilliantly but never reaches base has nobody to advance.

Runs created per 27 outs converts the counting statistic into a rate. Twenty-seven is the number of outs in a nine-inning game, so the figure answers: if this batter hit in all nine lineup spots, how many runs would his team score per game? One definitional note that matters. The outs denominator used here is AB − H, at-bats that did not end in a hit. That is the only kind of out the basic version's inputs can see — caught stealings, sacrifices and grounded-into-double-plays are outside its input set entirely. Variants that include them use a larger denominator and therefore report a slightly lower per-27 figure. The output on this page is labelled per 27 *batting* outs for exactly that reason.

The calculator rejects a line with no batting outs at all, because the per-27 rate would divide by zero and because a line without a single out has no meaningful per-game run rate anyway.

A worked example.

Frequently asked questions.

References& sources.

1. [1]de Souza White, J. (2025). 'Assessing the Accuracy of Runs Created: Comparing Outside and Inside Aggregation Methods.' Baseball Research Journal 54(1), Society for American Baseball Research. Source of the formula implemented here and of its factor names — '(H + BB) is the on-base factor, TB is known as the base-advancement factor, and (AB + BB) is the opportunities factor' — of the finding that inside aggregation is more accurate than outside aggregation and that Basic RC is the most accurate of the four variants, and of the two worked figures reproduced exactly by this calculator (Jorge Mateo 2022 ≈ 49 runs; Dansby Swanson 2022 = 93.81 runs).
2. [2]MLB Advanced Media, Stats API — season hitting line for Aaron Judge, 2025. Source of the worked example inputs: atBats 541, hits 179, baseOnBalls 124 and totalBases 372.
3. [3]Major League Baseball (2026). Official Baseball Rules, Rule 9.02(a). Defines every input this calculator takes as a box-score category: (1) at-bats, with the four situations in which no time at bat is charged; (3) safe hits; (8) total bases on safe hits; and (12) total number of bases on balls.
4. [4]FanGraphs Library, 'wRC'. Source of the statement that 'Weighted Runs Created (wRC) is an improved version of Bill James' Runs Created (RC) statistic, which attempted to quantify a player's total offensive value and measure it by runs', and of the wRC formula that superseded it.