Fantasy Points Per Game vs Total Points: Why Per-Game Averages Matter for Waiver Decisions
Most fantasy platforms display a player’s total points scored for the season. This number is useful for determining who on your roster has contributed the most, but it is a poor comparison tool for players who have played a different number of games. Fantasy points per game fixes this.
FPPG Quick Reference
| Situation | Use total points? | Use FPPG? | Why |
|---|---|---|---|
| Two players played same number of games | Yes — both equally valid | Yes — also valid, same result | No difference; either works |
| Comparing returning-from-injury player to healthy incumbent | No — misleads due to missed games | Yes — use FPPG to compare production when active | Injured player’s low total reflects missed games, not production rate |
| Evaluating player post-bye for waiver pickup | No | Yes — use recent FPPG (last 4 weeks) | Season total includes pre-bye context that may no longer apply |
| Receiving a trade offer on an injured player | No — buyer uses total to lowball | Yes — check FPPG to avoid bad deal | Player with 60 points in 6 games (10 FPPG) may be better than 80 in 9 (8.9 FPPG) |
| Setting weekly lineup between healthy players | Secondary only | Yes — recent FPPG (last 3–4 weeks) as primary signal | Recent form is more predictive than full-season averages |
| Season-long positional rankings | Yes — reasonable when games played are similar | Secondary | When games played are roughly equal, totals and FPPG rankings align well |
Why Total Season Points Mislead
Consider two wide receivers:
- WR A: 120 total points, played all 14 games — 8.6 points per game
- WR B: 90 total points, played 9 games — 10.0 points per game
Total points says WR A is better. Points per game says WR B is producing at a higher rate. If you are evaluating which player to start next week when both are healthy, WR B’s per-game rate is more relevant than their season total.
This distinction matters most for:
- Players returning from injury who have missed several games
- Players on a bye who have low season totals despite good weekly production
- Late-season waiver wire pickups being compared to incumbents who have 14 weeks of accumulation
When FPPG Is the Better Metric
Waiver wire decisions. When a player becomes available mid-season due to injury or bench designation, their season total is often low because they missed early games or were on the bench. Comparing their FPPG to your current starter’s FPPG gives a fairer comparison of who will produce more in any given week.
Trade value assessment. If someone is trying to buy low on an injured player with a low season total, check their FPPG before accepting a bad deal. A player with 60 total points in 6 games (10 FPPG) is actually producing at a high rate — their total is low only because they missed time.
Evaluating upside vs consistency. Players who have high highs and low lows can have misleading totals. A player with 3 monster weeks and 4 quiet weeks has a different FPPG profile than a player with 7 consistent weeks. Knowing which pattern you are getting helps you decide if you want that player based on your roster needs.
When Total Points Still Matters
Evaluating consistency over a season. If you want to know which player has been reliable across all of their opportunities, total points over a long stretch captures consistency in a way FPPG does not. A player with consistent 10-point weeks accumulates reliably; a player who alternates 20-point and 0-point weeks might have the same FPPG but is much less predictable.
Rankings and positional tiers. Season-long rankings are typically done by total points among players who have played approximately the same number of games. When comparing similarly healthy players in the same position, total points is often reasonable.
How to Calculate FPPG
Most platforms show total points but not FPPG by default. The formula is simple:
FPPG = Season total points / Games played
To find games played, check the player’s game log. Count any week where they had a recorded stat line, even if it was a small one. Weeks missed entirely (no stats) do not count.
For a player in their first 8 games of the season with 72 total points: 72 / 8 = 9.0 FPPG.
Applying FPPG to Lineup Decisions
When deciding between two players for the same starting slot:
- Find the FPPG of both players over the last 4 weeks (recent form, not the entire season)
- Consider the matchup — does the opponent allow more or fewer points to the position?
- Factor in the game environment — is this a high-total game where more production is expected?
FPPG is the baseline. Matchup and context adjust from there. A player with 10 FPPG in a favorable matchup against a weak defense is a stronger start than a player with 12 FPPG in a poor matchup against a top defensive unit.
For how to evaluate matchups that context-adjust your FPPG baseline, see: Fantasy Football Matchup Analysis: How to Use Defensive Matchups to Make Better Start-Sit Decisions. For how snap count data complements FPPG in evaluating role changes, see: Fantasy Football Opportunity Share: How to Evaluate Rush Share and Target Share.