Fantasy Points Per Game Calculator

Background.

Fantasy points per game is the fairest way to compare fantasy production, because raw season totals punish anyone who missed time. A player with 145.6 points in 9 games has been more productive than one with 160 in 12, and only the per-game rate shows it.

This calculator takes a points total you already have — from your league app, a stat site, or Quanta's fantasy football points calculator if you are scoring a line yourself — and returns four things: the per-game average, a straight-line projection of where the season finishes at that rate, how far the total still is from a target you set, and the pace required over the games that are left to get there.

The projection is deliberately naive. It extends the current rate forward and nothing else: no strength-of-schedule adjustment, no regression toward a positional mean, no injury risk. That is a feature for a quick check and a limitation for anything more serious, and the page says so rather than dressing a linear extrapolation up as a forecast.

Two conventions are worth knowing. Enter only games the player actually appeared in — counting bye weeks or inactives as games played drags the average down for reasons unrelated to performance. And if the season is over, enter zero games remaining: the required-pace figure will read 0 and the verdict will explain that there are no games left in which to make up a shortfall, rather than showing a division error.

What is fantasy points per game calculator?

Fantasy points per game, usually written FPPG, is a player's total fantasy points divided by the number of games they played. It is the standard rate statistic in fantasy football because season totals conflate production with availability: a player who misses four weeks to injury will trail a less productive player who started every week, even though the first is the better start when healthy. FPPG strips availability out and answers the narrower question of how much a player produces when he plays. Its weakness is the same as its strength — it says nothing about how often that happened, so a 20-point-per-game player who appeared six times may have been worth less to your season than a 14-point player who appeared in all seventeen. Read it beside games played, never alone. The projection on this page multiplies the per-game rate by the total number of games in the sample plus the games left, giving the season total implied by holding the current rate; the required-pace figure inverts the question and asks what rate the remaining games must produce to reach a chosen target. Both are simple linear arithmetic and both are sensitive to small samples: after two games, a per-game average is dominated by one big performance.

How to use this calculator.

1. 01Enter the points total and the number of games actually played. Do not count bye weeks or games the player was inactive for.
2. 02Enter the games remaining in your season. Fantasy regular seasons usually run 14 weeks with playoffs after, so count whichever window you care about.
3. 03Set a target. A payout line, a rival's projected total, or last year's positional cut-off all work.
4. 04Read the required-per-game figure against the current per-game figure. If required is higher, the verdict says by how much; if lower, it says the present pace is already enough.
5. 05Treat the projection as a pace indicator rather than a forecast. It assumes the rate holds exactly, which it will not.

The formula.

Points per game is the total divided by games played. The projection multiplies that rate by played plus remaining games, which is the same as scaling the current total by (G + R) ÷ G. Points still needed is the target minus what has been scored, and the required pace is that shortfall divided by the games left.

All four are linear, so they inherit the weaknesses of linearity. The projection assumes the rate is stable when in practice fantasy scoring is volatile week to week, driven heavily by touchdowns, which are the least repeatable component of a fantasy line. A rate built on two or three games is dominated by a single outlier performance; the same rate over ten games is a much stronger estimate of the same quantity.

Two edge cases are handled explicitly rather than left to produce errors. If no games remain, the required-pace division would be by zero, so the calculator returns 0 and the verdict states that the season is complete and no games remain in which to make up a shortfall. If the target has already been beaten, points still needed goes negative rather than being clamped to zero, because the size of the cushion is useful — and the verdict reports it as a cushion rather than as a deficit.

Fractional and negative inputs are both accepted on purpose. Every major fantasy platform scores fractional points by default, so a total of 145.6 is normal rather than a rounding artefact, and default settings that deduct two points for an interception and two for a fumble lost mean a short-run total really can sit below zero. The arithmetic is carried out in exact decimal rather than binary floating point so that totals like 182.4 divided by 11 and multiplied by 17 reproduce exactly.

A worked example.

Frequently asked questions.

References& sources.

1. [1]NFL Fantasy Football — 'Scoring', Default Scoring Settings (updated 21 March 2025). Source for the two behaviours this calculator has to accommodate: 'Use Fractional Points: Yes' and 'Use Negative Points: Yes', which are why fractional totals are normal and why a running total can legitimately be below zero under default settings that deduct 2 points per interception and 2 per fumble lost.
2. [2]Yahoo Fantasy Football — default league settings, scoring and stats. Corroborates fractional scoring and the −2 fumble-lost penalty across a second major platform, and documents the settings differences (−1 per interception, 0.5 per reception) that make cross-league point totals non-comparable without knowing the scoring rules.