Sideline Quant
Model feedLoading…
2026/27 · live record · Sideline's Team

Track record

Every gameweek the model publishes its predictions before the deadline and picks a real FPL team with them. After the last match settles, this page marks both against what actually happened — the weeks it got wrong included — and nothing here is edited afterwards.

So far: ahead of the average manager in 4 of 4 gameweeks (+38 points in total). A baseline beat the model on 6 measures: GW2, last season's points per game on spotting 10+ hauls; GW2, top-10k effective ownership on spotting 6+ hauls; GW2, top-10k effective ownership on spotting 10+ hauls; GW4, last season's points per game on points per player; GW4, top-10k effective ownership on spotting 10+ hauls; GW4, fpl's own projection (ep_next) on spotting 10+ hauls. 4 gameweeks in, read it as an early record, not a verdict.

Last settled GW4 · scored against the run of 12 Sept, 11:50 UTC · pre-registered · checkpoints at GW10, GW19, GW38

Points vs the average manager

+38

289 to the average manager’s 251 · above the average in 4 of 4 gameweeks · Triple Captain in GW1

GW1: 59 pts vs average 50 (+9) · TC+9GW1GW2: 91 pts vs average 81 (+10)+10GW2GW3: 56 pts vs average 51 (+5)+5GW3GW4: 83 pts vs average 69 (+14)+14GW4

Against a sample of top-10k managers: −16.9 in GW2, −1.3 in GW3, −6.7 in GW4 (before hits · no sample for GW1). This early, the sample is chosen on the very weeks it is scored on, so a deficit is overstated.

Ordering the players

0.31vs0.20
Model vs last season's points per game · 1.00 = perfect order, 0 = none · mean of 4 GWs on the same 576 players

Spotting 6+ hauls · season

68%vs61%
The model put a player who went on to haul above one who didn't 68% of the time; last season's points per game managed 61% · 115 hauls on 481 shared players

Overall rank

1.33m
1,325,466 · after 4 gameweeks — one team's rank moves a long way this early

The model's own team, week by week

One real FPL entry, picked by the model before every deadline: what it predicted for the squad it submitted, what the squad scored, and where the average manager and a sample of the top 10k landed the same week.

Model said · scored · the field

GW1TC
GW1: average manager 50GW1: model said 65.7 for the squad as submittedGW1: scored 59
+9 vs average · −6.7 vs model
GW2
GW2: average manager 81GW2: top-10k sample 107.9 (60 managers, before hits)GW2: model said 59.2 for the squad as submittedGW2: scored 91
+10 vs average · −16.9 vs top 10k · +31.8 vs model
GW3
GW3: average manager 51GW3: top-10k sample 57.3 (170 managers, before hits)GW3: model said 59.8 for the squad as submittedGW3: scored 56
+5 vs average · −1.3 vs top 10k · −3.8 vs model
GW4
GW4: average manager 69GW4: top-10k sample 89.7 (289 managers, before hits)GW4: model said 63.0 for the squad as submittedGW4: scored 83
+14 vs average · −6.7 vs top 10k · +20.0 vs model
ScoredModel’s prediction for the submitted squadAverage managerTop-10k sample, before hitsPoints per gameweek. Every mark is a row in the ledger.
Total points
289after hits
Team value
£97.0m+ £3.2m bank
Chips played
1TC GW1
Every settled gameweek of the model’s real FPL team. Select a gameweek to see the team.
GWPtsvs avgvs 10ktotalrankpredictedchip
59+9591.99m65.7TC
91+10−16.91501.98m59.2
56+5−1.32061.68m59.8
83+14−6.72891.33m63.0

Select a gameweek to see the team below. A dash means the figure could not be computed for that week; it is never a zero.

The team in GW483 ptsShow the team
Raya
14pts
MinutesMin90
BonusBns3
GKARS
Gabriel
9pts
MinutesMin90
BonusBns2
DEFARS
Lacroix
1pts
MinutesMin4
BonusBns0
DEFCHE
Virgil
8pts
MinutesMin90
BonusBns0
DEFLIV
Calafiori
6pts
MinutesMin90
BonusBns0
DEFARS
Tavernier
8pts
MinutesMin82
BonusBns2
MIDBOU
V
Palmer
5pts
MinutesMin90
BonusBns0
MIDCHE
Szoboszlai
3pts
MinutesMin90
BonusBns0
MIDLIV
Wirtz
3pts
MinutesMin90
BonusBns0
MIDLIV
Mbeumo
2pts
MinutesMin90
BonusBns0
MIDMUN
C
João Pedro
12pts
MinutesMin90
BonusBns3
FWDCHE
benchΣ 6pts
1
Phillips
0pts
MinutesMin0
BonusBns0
GKHUL
2
Guéhi
6pts
MinutesMin90
BonusBns0
DEFMCI
3
Walle Egeli
0pts
MinutesMin0
BonusBns0
FWDIPS
4
Kusi-Asare
0pts
MinutesMin0
BonusBns0
FWDFUL
Transfers
OUTO'ReillyMCIINPalmerCHEOUTB.FernandesMUNINLacroixCHE

How accurate were the predictions?

League-wide, not just our team: every player the model expected to start, scored on what he then did. Points per player first, then whether the model ordered the players the right way and spotted the hauls — each week against a baseline that knows nothing but last season's points per game.

Prediction accuracy per settled gameweek, over likely starters, with the season to date.
GWPoints per playerMAEBig missesRMSEOrderingrank ρPredicted → scoredΣ xP → Σ ptsPlayersnSpotting 6+AUCSpotting 10+AUC
GW1seed2.753.350.290.09–0.45332 → 30295
GW22.373.170.360.23–0.48680 → 66620367%57–7572%57–85
GW32.302.990.160.03–0.28681 → 68519969%60–7764%46–80
GW42.643.440.310.18–0.43686 → 71520570%62–7858%41–76
SeasonGW1–GW42.483.232378 → 2368702

† fewer than 50 hauls that week — too few to claim a result (GW2 6+: 43 · GW2 10+: 13 · GW3 6+: 42 · GW3 10+: 12 · GW4 10+: 14).

Ordering and the haul figures are per gameweek and are not averaged; the season comparison on the same players is in the tiles above. Likely starters only: players the model expected to play 60+ minutes (predicted E[minutes] > 60 (n=702 of 2458 player-fixtures)).

95% percentile intervals from a row-level bootstrap (1000 resamples, seeded). Player-fixtures within a gameweek share fixtures and clean sheets, so these intervals understate the true width — read them as a floor on the uncertainty, not the uncertainty. A haul AUC on fewer than 50 hauls is too few to claim.

What went wrong each week, and how the baselines did

GW46 misses · beaten by last season's points per game on points per player; top-10k effective ownership on spotting 10+ hauls; fpl's own projection (ep_next) on spotting 10+ haulsOpen
  • A worse week than usual: the model missed by 2.64 points a player, against 2.48 across the season so far.
  • Last season's points per game was closer than the model on points per player: 2.71 to 2.71 on the 162 players both scored.
  • Top-10k effective ownership was better than the model at spotting 10+ hauls this week: on the 205 players both scored, it ranked a hauler above a non-hauler 66% of the time, the model 58%.
  • FPL's own projection (ep_next) was better than the model at spotting 10+ hauls this week: on the 205 players both scored, it ranked a hauler above a non-hauler 74% of the time, the model 58%.
  • Spotting 10+ hauls was no better than a coin toss this week: 58%, with an interval (41%–76%) that includes 50%.
  • The team finished 6.7 behind a sample of top-10k managers (average 89.7, 289 sampled). This early, the sample is chosen on the very weeks it is scored on, so the gap is overstated.
  • The model was closer than last season's points per game on the big misses: 3.45 to 3.51 on the 162 players both scored.
  • The model ordered the players better than last season's points per game: 0.30 to 0.24 on the 162 players both scored.
  • The model was better than last season's points per game at spotting 6+ hauls: 67% to 62% on the 162 players both scored.
  • The model was better than last season's points per game at spotting 10+ hauls: 62% to 56% on the 162 players both scored.
  • The model ordered the players better than top-10k effective ownership: 0.31 to 0.18 on the 205 players both scored.
  • The model was better than top-10k effective ownership at spotting 6+ hauls: 70% to 61% on the 205 players both scored.
  • The model ordered the players better than fpl's own projection (ep_next): 0.31 to 0.26 on the 205 players both scored.
  • The model was better than fpl's own projection (ep_next) at spotting 6+ hauls: 70% to 60% on the 205 players both scored.
  • The team scored 83, 14 above the average manager's 69.
  • Only 14 players scored 10+ this week — too few to claim a result on the 10+ figure.

Scored against the run of 12 Sept, 11:50 UTC · rows a0497656…c5bd · full report →

Against the baselines

Last season's points per gamesame 162 players
MeasureModelBaselineVerdict
points per player2.712.71baseline ahead
big misses3.453.51model ahead
ordering the players0.300.24model ahead
spotting 6+ hauls67%62%model ahead
spotting 10+ hauls62%56%model ahead
Top-10k effective ownershipordering only · same 205 players
MeasureModelBaselineVerdict
ordering the players0.310.18model ahead
spotting 6+ hauls70%61%model ahead
spotting 10+ hauls58%66%baseline ahead
FPL's own projection (ep_next)ordering only · same 205 players
MeasureModelBaselineVerdict
ordering the players0.310.26model ahead
spotting 6+ hauls70%60%model ahead
spotting 10+ hauls58%74%baseline ahead
GW34 misses · no baseline aheadOpen
  • Its ordering of the players barely matched the week's: rank correlation 0.16, where 1.00 would be a perfect order and 0 no relationship at all.
  • Spotting 10+ hauls was no better than a coin toss this week: 64%, with an interval (46%–80%) that includes 50%.
  • The team finished 1.3 behind a sample of top-10k managers (average 57.3, 170 sampled). This early, the sample is chosen on the very weeks it is scored on, so the gap is overstated.
  • The best team the model could legally have bought scored 51 — 40% of the 127 a perfect-hindsight XI would have made.
  • A better week than usual: 2.30 points of miss per player, against 2.48 across the season so far.
  • The model was closer than last season's points per game on points per player: 2.40 to 2.48 on the 156 players both scored.
  • The model was closer than last season's points per game on the big misses: 3.08 to 3.25 on the 156 players both scored.
  • The model ordered the players better than last season's points per game: 0.20 to 0.07 on the 156 players both scored.
  • The model was better than last season's points per game at spotting 6+ hauls: 68% to 56% on the 156 players both scored.
  • The model was better than last season's points per game at spotting 10+ hauls: 64% to 43% on the 156 players both scored.
  • The model ordered the players better than top-10k effective ownership: 0.16 to 0.09 on the 199 players both scored.
  • The model was better than top-10k effective ownership at spotting 6+ hauls: 69% to 55% on the 199 players both scored.
  • The model was better than top-10k effective ownership at spotting 10+ hauls: 64% to 49% on the 199 players both scored.
  • The team scored 56, 5 above the average manager's 51.
  • Only 42 players scored 6+ this week — too few to claim a result on the 6+ figure.
  • Only 12 players scored 10+ this week — too few to claim a result on the 10+ figure.

Scored against the run of 4 Sept, 16:27 UTC · rows 6f8b387e…5a77 · full report →

Against the baselines

Last season's points per gamesame 156 players
MeasureModelBaselineVerdict
points per player2.402.48model ahead
big misses3.083.25model ahead
ordering the players0.200.07model ahead
spotting 6+ hauls68%56%model ahead
spotting 10+ hauls64%43%model ahead
Top-10k effective ownershipordering only · same 199 players
MeasureModelBaselineVerdict
ordering the players0.160.09model ahead
spotting 6+ hauls69%55%model ahead
spotting 10+ hauls64%49%model ahead

FPL's own projection (ep_next) — not available this gameweek: no FPL ep_next capture in this gameweek's pre-deadline window.

GW25 misses · beaten by last season's points per game on spotting 10+ hauls; top-10k effective ownership on spotting 6+ hauls; top-10k effective ownership on spotting 10+ haulsOpen
  • Last season's points per game was better than the model at spotting 10+ hauls this week: on the 163 players both scored, it ranked a hauler above a non-hauler 82% of the time, the model 76%.
  • Top-10k effective ownership was better than the model at spotting 6+ hauls this week: on the 203 players both scored, it ranked a hauler above a non-hauler 67% of the time, the model 67%.
  • Top-10k effective ownership was better than the model at spotting 10+ hauls this week: on the 203 players both scored, it ranked a hauler above a non-hauler 74% of the time, the model 72%.
  • The team finished 16.9 behind a sample of top-10k managers (average 107.9, 60 sampled). This early, the sample is chosen on the very weeks it is scored on, so the gap is overstated.
  • 12 points sat on the bench and did not count (no Bench Boost).
  • A better week than usual: 2.37 points of miss per player, against 2.48 across the season so far.
  • The model was closer than last season's points per game on points per player: 2.34 to 2.39 on the 163 players both scored.
  • The model was closer than last season's points per game on the big misses: 3.21 to 3.25 on the 163 players both scored.
  • The model ordered the players better than last season's points per game: 0.43 to 0.23 on the 163 players both scored.
  • The model was better than last season's points per game at spotting 6+ hauls: 71% to 66% on the 163 players both scored.
  • The model ordered the players better than top-10k effective ownership: 0.36 to 0.27 on the 203 players both scored.
  • The team scored 91, 10 above the average manager's 81.
  • Only 43 players scored 6+ this week — too few to claim a result on the 6+ figure.
  • Only 13 players scored 10+ this week — too few to claim a result on the 10+ figure.

Scored against the run of 28 Aug, 17:22 UTC · rows dc666d46…9013 · full report →

Against the baselines

Last season's points per gamesame 163 players
MeasureModelBaselineVerdict
points per player2.342.39model ahead
big misses3.213.25model ahead
ordering the players0.430.23model ahead
spotting 6+ hauls71%66%model ahead
spotting 10+ hauls76%82%baseline ahead
Top-10k effective ownershipordering only · same 203 players
MeasureModelBaselineVerdict
ordering the players0.360.27model ahead
spotting 6+ hauls67%67%baseline ahead
spotting 10+ hauls72%74%baseline ahead

FPL's own projection (ep_next) — not available this gameweek: no FPL ep_next capture in this gameweek's pre-deadline window.

GW1seed5 misses · no baseline aheadOpen
  • A worse week than usual: the model missed by 2.75 points a player, against 2.48 across the season so far.
  • Too optimistic overall: it predicted 332 points for 95 likely starters, who scored 302 — 10% high.
  • 11 points sat on the bench and did not count (no Bench Boost).
  • Captain Mbeumo scored 2 — tripled to 6 by the Triple Captain.
  • The best team the model could legally have bought scored 38 — 26% of the 148 a perfect-hindsight XI would have made.
  • The model was closer than last season's points per game on points per player: 2.75 to 2.93 on the 95 players both scored.
  • The model was closer than last season's points per game on the big misses: 3.35 to 3.38 on the 95 players both scored.
  • The model ordered the players better than last season's points per game: 0.29 to 0.27 on the 95 players both scored.
  • The team scored 59, 9 above the average manager's 50.
  • No haul figures for this week: the predictions it is scored against did not keep haul probabilities, so there is nothing to mark. Not a zero.
  • Gameweek 1 is marked against the predictions committed before the season started (the "seed"), because live runs were not being kept yet.
  • No top-10k sample was taken for this week, so there is no elite comparison.

Scored against the seed of 18 Aug, 21:51 UTC · rows 4d566e22…dc02 · full report →

Against the baselines

Last season's points per gamesame 95 players
MeasureModelBaselineVerdict
points per player2.752.93model ahead
big misses3.353.38model ahead
ordering the players0.290.27model ahead

Top-10k effective ownership — not available this gameweek: no top-10k capture before this gameweek's deadline.

FPL's own projection (ep_next) — not available this gameweek: no FPL ep_next capture in this gameweek's pre-deadline window.

Every stated population, and the reliability tablesThe auditor’s view: the same error on four groups of players, and whether the model’s probabilities mean what they say.Open

Points per player, on every group we could score it on

GroupGW1GW2GW3GW4Season
Every player the model projected1.49n=5841.18n=6021.08n=6181.18n=6541.23n=2458
Players the model gave any minutes1.67n=5191.27n=5561.29n=5181.41n=5491.41n=2142
Players who actually playedhindsight2.21n=3011.89n=2991.91n=2902.13n=3072.04n=1197
Likely startersthe headline2.75n=952.37n=2032.30n=1992.64n=2052.48n=702

About half of all projected rows score exactly 0, which is why the every-player figure is small and is never shown alone. The players-who-played row selects on the outcome — a player who did not play is not in it — and is marked hindsight for that reason. Comparing with anyone else’s error figure only means something on the same group.

When the model says 70%, does it happen 70% of the time?

Plays 60+ minutes
played 60+ minutes · every projected player-fixture with a retained p_start60 (n=2458 of 2458)
PredictedObserved95% rangen
0%0%0–1492
1%0%0–2246
3%3%1–6245
7%13%9–18246
16%25%20–31246
35%44%38–50245
65%65%59–71246
85%89%84–92246
93%94%90–96246
Scores 6+
scored 6+ points · every projected player-fixture with a retained p_ge_6 (n=1874 of 2458)
PredictedObserved95% rangen
0%0%0–1378
0%0%0–2185
1%1%0–4187
2%2%1–5187
5%3%1–6188
10%8%5–13187
15%13%9–18187
22%25%19–31187
34%37%30–44188
Scores 10+
scored 10+ points · every projected player-fixture with a retained p_ge_10 (n=1874 of 2458)
PredictedObserved95% rangen
0%0%0–1378
0%0%0–2185
0%0%0–2187
0%0%0–2191
1%1%0–3185
2%2%1–5187
4%2%1–5188
5%6%4–11186
10%11%7–16187

Bins of the model’s stated probability against the rate at which it happened, with Wilson 95% intervals. A calibrated forecaster’s observed column tracks its predicted column; the range says how much a small bin can be trusted.

Who beat the model's number, and who fell short

The players furthest above and below their predictions so far this season.

Points scored minus the model’s prediction, added up over the settled gameweeks. Only weeks the model expected the player to start (60+ minutes) count. Two seasons of form fit in a fortnight of variance; read it as colour, not evidence.

Scored above the model’s number

BogleLEEDEF
3 GWs · predicted 8.7 → scored 31
+22.3
GroßBHAMIDxA +2.4
4 GWs · predicted 15.4 → scored 33
+17.6
BelloumiHULMIDxG +1.6
3 GWs · predicted 8.6 → scored 24
+15.4
SchadeBREMIDxG +2.0
4 GWs · predicted 15.3 → scored 30
+14.7
TarkowskiEVEDEF
4 GWs · predicted 14.8 → scored 29
+14.2

Scored below the model’s number

O'ReillyMCIDEF
4 GWs · predicted 18.1 → scored 5
−13.1
ThiagoBREFWDxG −2.4
4 GWs · predicted 17.4 → scored 5
−12.3
JamesCHEDEF
4 GWs · predicted 12.6 → scored 3
−9.6
CanvotCRYDEF
3 GWs · predicted 10.2 → scored 1
−9.2
RichardsCRYDEF
3 GWs · predicted 11.2 → scored 3
−8.2