Inside the World's #1 FPL Team: Every Chip, Every Transfer, Gameweek by Gameweek

Five gameweeks into the season, there's one Fantasy Premier League team sitting above every other entry in the game: 468 points, overall rank #1. Team name "Jake Crow Sliced Jam", managed by Jasper Selvaraj (entry ID 895045). Here's what you can learn from it.

Every number below is pulled straight from FPL's own API — their real gameweek-by-gameweek history, their actual chip usage, and their squad before and after the one wildcard they've played.

The headline numbers

• 468 total points through Gameweek 5 — the highest of any of the roughly 11 million entries in the game
• Average manager through the same 5 gameweeks: 299 points — the world #1 is 169 points clear of average, nearly 60% ahead
• All four chips already used — Bench Boost, Triple Captain, Wildcard, and Free Hit, one per gameweek across GW1, GW3, GW4 and GW5
• 26 points left on the bench across the season so far, despite that aggressive chip usage

Week by week

Two things jump out immediately. First, their best week (119, Gameweek 2) came with no chip active at all — the two "power" chips they've played so far (Bench Boost, Triple Captain) didn't outscore a normal week. Second, Gameweek 3's Triple Captain actually underperformed: 90 points is their second-worst week of the season, chip included.

The Triple Captain that didn't land

Going into Gameweek 3, this is the squad they had assembled (3-4-3, Haaland captained, Isak vice):

They tripled Haaland. He returned 9 points — tripled to 27, a modest haul by Triple Captain standards, and nowhere near justifying the chip on its own. Worse, their bench that week (a three-way tie at 3 points each from Verbruggen, Slater and O'Shea) left 11 points unused — the single biggest bench-points week of their season. A misfiring chip stacked on a heavy bench is about as bad as a gameweek gets for a manager otherwise playing at a world-#1 level.

The wildcard, then an immediate Free Hit

One gameweek later, they wildcarded. This is the squad that rebuild produced — played in Gameweek 4 (3-4-3, Palmer captained this time, not Haaland, João Pedro vice):

Then, just one gameweek after that, a second chip: Free Hit for Gameweek 5. Free Hit doesn't touch the underlying squad — it swaps in a completely different one-week XI, then reverts back to whatever squad you had (here, the wildcard XI above, plus whatever transfers happen in the meantime) once the gameweek ends. This is what they played that one week, with Haaland restored to the captaincy and Gibbs-White now vice:

Only Haaland and Wissa carry over from the wildcard XI — everything else is a one-week rental. The new spine leans hard into Arsenal (Saka) and Chelsea (Palmer) as the midfield engine room, alongside Nottingham Forest's Sels and N.Williams — a differential defensive pairing most managers aren't running.

Did Free Hit misfire? Gameweek 5's 63 points is their lowest score of the season, so it's tempting to read it that way — but run the numbers on the alternative. If they'd made zero changes and simply played the wildcard XI above (same captain, Palmer) in Gameweek 5, it would have scored just 32 points: Schade, João Pedro and Rogers each blanked or returned single digits, and Palmer's doubled captaincy was only worth 4. Free Hit roughly doubled what that squad would otherwise have returned. Gameweek 5 is genuinely their thinnest margin over the field all season (63 vs. a 48-point average, +31% — their smallest edge of any of the five gameweeks, against +43-94% everywhere else) — but that's the whole gameweek scoring low across the board, not the chip failing. If anything, Free Hit is the reason Gameweek 5 wasn't a far worse week than it actually was.

How close does a pure-stats pick get?

For comparison: we build a "Team of the Season" on this site — the best-scoring legal XI, picked purely from cumulative season stats, using the same method FPL's own Dream Team uses for a single gameweek. With Haaland captained (the same call the real world #1 made), that stats-only XI scored 458 points through Gameweek 5 — a 10-point gap to the actual world #1.

The gap wasn't always that close. After Gameweek 1 the real #1 led by 19 points; by Gameweek 4 and 5, the stats-built team actually outscored them both weeks (112 vs 99 in GW4, 86 vs 63 in GW5). Chip timing and a stacked bench are, so far, the difference between a squad built from spreadsheets and the actual best manager alive.

Even the world #1 has a rough week

It's tempting to read "468 points, rank #1" and picture flawless decision-making. The data says otherwise. Look closely and this is a squad with the same kind of ordinary missteps every manager makes:

• Wissa returned zero points in the current Gameweek 5 squad — a forward slot that blanked on the one week (Free Hit) you can least afford it to.
• Gonzalo managed just 2 points in the pre-wildcard XI, a forward pick that never really worked before it got wildcarded away in Gameweek 4.
• The Triple Captain wasn't a contrarian gamble — it was Haaland at home to newly-promoted Coventry, a fixture Man City won 1-0. That's close to the most obvious captain choice in the game that gameweek, the pick a huge share of active managers were also making. Tripled, it still only returned 27 points — a modest week by Triple Captain standards. Even the "safe," popular pick doesn't always pay off.

None of that reads like someone with a secret formula. It reads like a normal FPL season — a stacked bench one week, a forward who blanks, a captain call that looked obvious and just didn't fire — except with all four chips already spent and one standout gameweek (119 points in Gameweek 2) doing a lot of the heavy lifting. The lead at the top of the game right now isn't the product of never being wrong. It's the product of being right often enough, at the right moments, to absorb being wrong the rest of the time — the same trade-off every one of the other 11 million managers is making. This one's just had the variance land a little kinder so far, on top of real skill, real risk-taking with those chips, and a full season still left to prove it wasn't a fluke.

Data pulled live from the official FPL API (entry/895045/history/ and entry/895045/event/{gw}/picks/) — see our dashboards for the same kind of real, verifiable stats on any player or team.