What Does FPPG Mean in Fantasy Football?
FPPG — fantasy points per game — is the number on every DraftKings and FanDuel player card. What it measures, how scoring changes it, and the traps that make it lie.
FPPG stands for fantasy points per game: a player's total fantasy points divided by the number of games they have actually played. It's the headline number on every player card on DraftKings and FanDuel, and the first column most season-long managers sort by. The formula could not be simpler — the traps are all in what goes into it.
The calculation
FPPG = total fantasy points ÷ games played
A running back with 145.6 points through 9 games has an FPPG of 145.6 ÷ 9 = 16.18. That's the whole formula. The fantasy points per game calculator does the division and then the two projections managers actually want next: at 16.18 a game with 5 games remaining, the player projects to another 80.9 points (a 226.5-point season) — and if you need him to reach 240 for your league's record book, he must average 18.9 the rest of the way.
Why per-game beats totals
Totals reward attendance; per-game rewards production. A receiver with 150 points over 12 games (12.5 FPPG) has out-totaled one with 145.6 over 9 (16.18 FPPG) — but the second player has been meaningfully better every week he's played. For roster decisions, trade valuations and daily-fantasy pricing, the per-game figure is the one that transfers to next week, because next week is one game, not a season.
That's also why FPPG is the standard for comparing players who missed time. Injuries, byes and late-season rests distort totals badly; FPPG corrects for them — mostly. The corrections have corners, and the corners are where mistakes live.
Trap one: what counts as a game played
The convention — the one the platforms use — is that bye weeks don't count (the player didn't play) but games a player appeared in do count, however briefly. A running back who took eight snaps before leaving injured has "played" that game, and it drags his FPPG down as if he'd been healthy all afternoon. When you're evaluating a player coming off injury, recompute his FPPG excluding wrecked games — the number the platform shows and the number that predicts next week can be quite different.
Trap two: FPPG depends entirely on scoring format
"Points" is not one thing. The same season produces different FPPG in every scoring system, and comparing numbers across formats is meaningless. Take a wide receiver's season: 78 receptions, 1,150 yards, 8 touchdowns over a full 16 games.
| Format | Scoring | Season points | FPPG |
|---|---|---|---|
| Standard | yards ÷ 10 + TDs × 6 | 115 + 48 = 163 | 10.19 |
| Half-PPR | + 0.5 per reception | 163 + 39 = 202 | 12.63 |
| Full PPR | + 1 per reception | 163 + 78 = 241 | 15.06 |
Same player, same season — and a 48% difference in FPPG between standard and full PPR. Reception-heavy players (slot receivers, pass-catching backs) leapfrog touchdown-dependent ones the moment receptions score. Before quoting anyone's FPPG, know which format produced it; to build the underlying number from raw stat lines in your own league's rules, use the fantasy football points calculator and then divide by games with the per-game tool.
Trap three: small samples
Two games into a season, FPPG is noise. A receiver who caught two touchdowns in week one is "averaging" numbers he will not sustain, and waiver-wire overreactions to tiny samples are the most reliably losing move in fantasy. There's no formula fix — just a rule of thumb: treat FPPG as meaningful from about week 4 or 5, and weight recent games over September games as the season ages. Daily platforms show season-long FPPG on the card; sharp DFS players look at the last three to five games instead.
FPPG and salary: the DFS value calculation
Daily fantasy adds one more step to the arithmetic. DraftKings and FanDuel price every player with a salary, and the working number sharp players compute is value: points per $1,000 of salary. A player at a $6,800 salary with a 16.18 FPPG is returning 16.18 ÷ 6.8 = 2.38 points per $1k; the common rule of thumb is that a winning DraftKings lineup needs roughly 3x value from most slots. The reason FPPG matters so much on those platforms is that it is the numerator of this ratio — mis-measure it (wrong format, injury-wrecked games, tiny sample) and the value column inherits the error, salary and all.
Using FPPG for projections — honestly
Multiplying FPPG by remaining games is a pace, not a prophecy. It assumes health, role stability and schedule-neutral matchups, none of which is guaranteed. The projection is still worth computing — it turns "he's been good" into "he's on pace for 226, and I need 240 to win the points title, so I need a trade" — as long as you treat it as the baseline scenario rather than the forecast. The FPPG calculator labels its projection output exactly that way for exactly that reason.
The quick answers
What does FPPG mean? Fantasy points per game: total fantasy points ÷ games played.
Is a 16 FPPG good? Format-dependent — in full PPR, roughly WR1/RB1 territory; in standard scoring it's elite.
Do byes count as games? No. Games a player briefly appeared in do — recompute manually when that distorts things.
Why does DraftKings show a different FPPG than my league? Different scoring format. Same stats, different points.
FPPG is one of dozens of sports rates worth knowing cold — the same logic (production ÷ opportunity) runs through batting averages, run rates and handicaps across Quanta's sports calculators, each of which shows its formula and a worked example on the page. Something about your league's scoring these tools don't cover? Let us know and we'll look at adding it.