Erling Haaland – Minutes Played Graphs for anticipating Pep rotation in FPL

Posted on by admin

This write-up pulls together all of Erling Haaland’s playing minutes for Manchester City (across all competitions) and for Norway for the 2025/26 season up to Friday 30 January 2026. The two visuals generated are:

  • Graph A: rolling 7-day total minutes across the season
  • Graph B: match-by-match minutes with key anomalies labelled

The goal is practical: identify when Erling Haaland is “fresh”, when he’s being load-managed, and how to spot the next likely rest before the FPL deadline.

What we measured and why it works

We looked at workload two ways.

  1. Rolling 7-day minutes (Graph A)
    For each match date, we summed Haaland’s minutes across the previous seven days. This is the cleanest single number for congestion because it captures what managers actually worry about: how much football he’s had recently, regardless of competition.
  2. Match-by-match minutes (Graph B)
    This shows how Pep actually manages him in real life: full 90s, planned subs, cup hooks, and rare bench appearances.

Used together, these two views answer both questions FPL Managers care about:

  • “How overloaded was he leading into a rest?” (Graph A)
  • “What does a rest look like in Pep’s selection pattern?” (Graph B)

Key finding 1: January produced the biggest congestion spike of the season

The standout feature in Graph A is the highest rolling 7-day total occurring in early January 2026.

That peak is explained by a classic congestion cluster:

  • 2026-01-01 (Premier League vs Sunderland): 90
  • 2026-01-04 (Premier League vs Chelsea): 90
  • 2026-01-07 (Premier League vs Brighton): 90

That’s 270 minutes in six days, which is basically three full matches without meaningful recovery time. When you see the rolling 7-day line climb to that level, you’re not just looking at “a lot of minutes” — you’re looking at a risk point where elite forwards become more likely to be protected.

This is why the rolling view is so useful: it identifies stress windows that aren’t obvious when you just scan fixtures.

Key finding 2: The Wolves benching wasn’t random — it’s load management

On 24 January 2026 Haaland was benched and only played 18 minutes against Wolves in the EPL. Graph B flags this as the most extreme minutes drop of the season.

Graph A explains why it happened.

In the week leading into that match, Haaland’s minutes stack up as:

  • 2026-01-13 (EFL Cup semi-final vs Newcastle): 90
  • 2026-01-17 (Premier League vs Man United): 79
  • 2026-01-20 (Champions League vs Bodø/Glimt): 90

That’s 259 minutes inside seven days. Even before you factor travel and match intensity, this is a heavy load. And it comes after an already congested start to the month.

So Wolves (18 minutes) wasn’t a tactical surprise or a performance-based decision. The pattern fits deliberate workload protection.

From an FPL perspective, this is the exact type of benching you can sometimes anticipate:

  • not because “Pep roulette”
  • but because the workload number is shouting that a managed game is likely

Key finding 3: Haaland is normally a 90-minute player — so low minutes are meaningful

Graph B shows an important baseline: across league and Champions League matches, Haaland’s typical appearance is very close to 90 minutes. That matters because:

  • if a player is routinely hooked at 65–75, occasional benching is less predictable
  • but if a player is usually a full-match starter, sudden drops (45, 26, 18) are strong signals

In this dataset, the “low-minute” events are not noise. They are identifiable interventions.

Two particularly instructive examples:

  • 45 minutes vs Exeter in the FA Cup (10 Jan): classic planned cup load management
  • 18 minutes vs Wolves (24 Jan): classic league load management after a heavy week

So the story isn’t “Haaland is rotated constantly.” The story is: he’s trusted for 90 most of the time, then managed sharply when the schedule or workload forces it.

A practical workload rule of thumb from the season pattern

This is the part you can actually use week-to-week.

Looking at the season’s rolling 7-day pattern and the resulting “management events”, a sensible risk scale is:

  • Under ~180 rolling minutes (7 days): low rotation risk
  • Around 200–240: rising substitution/managed-minutes risk
  • Around 250+: high probability of either a bench, an early hook, or reduced involvement in one match

This isn’t a medical diagnosis and it isn’t perfect. But it matches what we saw around the Wolves rest: the rolling minutes were very high, and the response was a bench.

The key is not treating the number as a binary yes/no. Use it as a warning light:

  • If you’re captaining Haaland, you want to be confident he’s on the pitch for 80–90.
  • If you’re deciding between him and another premium, you want to know when his minutes ceiling might be capped.

How to use this to predict the next rest

To anticipate another Wolves-style situation, watch for the same ingredients:

  1. Three matches within seven days, especially if two are 90s
  2. One of those matches is Champions League (often higher intensity)
  3. The next league opponent is “manageable” (a fixture City believe they can win without 90 minutes from Haaland)
  4. City have another important match within the following 3–5 days

In other words: the rest is more likely when the fixture is still winnable and the schedule demands protection.

This is why workload tracking matters more than opponent strength alone. Managers often assume the toughest opponent means the player starts. In reality, fixture sequencing often matters more than fixture difficulty.

What this suggests about Haaland specifically

The dataset supports three clear conclusions:

  1. His default is maximum minutes
    He is not routinely rotated. When he starts league and Champions League matches, he frequently plays close to 90.
  2. Pep manages him sharply when needed
    When the schedule compresses, the management is decisive: a bench, a short cameo, or a cup hook.
  3. The “rest events” have context
    Wolves wasn’t random. It followed a heavy seven-day period that was visible in the rolling minutes.

That last point is the real value: you can’t predict every Pep decision, but you can identify when a rest becomes rational — and therefore more likely.

For further discussions have a look at FISO’s FPL forum where you can also see the FPL mini-leagues and FPL side-games available. The free to play FPL or pay to play season/weekend/daily games like FanTeam are ideal ways of following the Premier League action.