Comparison

How we compare

A factual comparison of the public FPL projection models: whose method is published, whose data is reusable, who publishes a graded record, who is free and who machines can read. No accuracy claims across sites.

Whose team scored what

Every site here publishes a recommended XI before the deadline. We freeze each one in a public git commit as it is published, then score them all on official Fantasy Premier League points after the gameweek — captain doubled, nothing else. Ours are the two squads we actually field.

Gameweek 3

TeamPointsCaptain
evmax — Model XI37—official points, autosubs applied
evmax — Consensus XI59—the crowd's template, same grading
Fantasy Football Scout — Scout Picks41—XI as published (early)
Fantasy Football IQ — IQ AI's squad45B.FernandesXI as published (final)

Gameweek 4

TeamPointsCaptain
evmax — Model XI76—official points, autosubs applied
evmax — Consensus XI83—the crowd's template, same grading
Fantasy Football Scout — Scout Picks88—XI as published (final)
Fantasy Football IQ — IQ AI's squad64B.FernandesXI as published (final)

Gameweek 5

TeamPointsCaptain
evmax — Model XI44—official points, autosubs applied
evmax — Consensus XI31—the crowd's template, same grading

Player by player — who projects most accurately

The analyst's view. Each source's projection for every player is frozen before the deadline and scored after: mean absolute error, lower is better, on the players who played 60+ minutes and on the common intersection of all nonempty sources. Original source coverage is reported separately. The 60+ group is selected after outcomes; it is a descriptive slice. A model earns its keep only by beating the two naive baselines.

Gameweek 3

SourceMAE, 60+ minRMSE, 60+ minMAE, everyone
evmax2.468n=1923.4771.891n=343; source coverage=585
Fantasy Football IQ2.371n=1923.2451.786n=343; source coverage=617
FPL ep_next (official)2.986n=1923.9312.157n=343; source coverage=617
baseline: season pts/appearance2.951n=1923.9132.297n=343; source coverage=358
baseline: last-4 mean2.951n=1923.9132.297n=343; source coverage=358

Gameweek 4

SourceMAE, 60+ minRMSE, 60+ minMAE, everyone
evmax2.576n=1943.4961.866n=387; source coverage=655
Fantasy Football IQ2.491n=1943.3931.83n=387; source coverage=654
FPL ep_next (official)2.686n=1943.5911.999n=387; source coverage=655
baseline: season pts/appearance2.643n=1943.5592.226n=387; source coverage=387
baseline: last-4 mean2.643n=1943.5592.226n=387; source coverage=387

Gameweek 5

SourceMAE, 60+ minRMSE, 60+ minMAE, everyone
evmax2.589n=2073.6671.716n=406; source coverage=659
Fantasy Football IQ2.639n=2073.6561.752n=406; source coverage=659
FPL ep_next (official)2.716n=2073.7721.818n=406; source coverage=659
baseline: season pts/appearance2.743n=2073.7342.176n=406; source coverage=406
baseline: last-4 mean2.743n=2073.7342.176n=406; source coverage=406

Graded so far — evmax against FPL's own projection

The two columns captured since gameweek 1, on identical players. The full benchmark joins this table from gameweek 3.

GWevmax MAEep_next MAEplayersahead
GW12.734—58ep_next not captured
GW22.8482.90964evmax ahead
GW32.4043.19863evmax ahead
GW41.2071.243655evmax ahead
GW51.1481.166659evmax ahead
GW61.1031.176667evmax ahead

Fantasy Football IQ projections are used under their published licence (free to use with attribution — fantasyfootballiq.app). Only derived metrics appear here; nobody's projections are republished. Sources with restrictive terms are invited in writing instead — the invitation and the answer both get published.

Why these tables never quote anyone's self-reported number

Every model grades itself over a different sample: different gameweeks, a different set of players, sometimes a different definition of error. Side by side, those numbers would look authoritative and prove nothing. The benchmark above exists precisely so the comparison can be made honestly: one sample, one yardstick, frozen in public before kickoff.

What can actually be checked

Our prospective season experiment tracks registered approaches under shared rules, separately from the historical squads.

Every cell links to its source. Checked 24 August 2026. If a row is wrong or out of date, tell us and we will correct it here.

SiteMethod publishedData reusablePublic graded recordFree to useMachine-readable
evmaxPublishedCC BY 4.0, per gameweekPublic ledger, every gameweekFree, no ads, no sign-upJSON API, MCP server, llms.txt
Onside ArenaPrivate — “the exact recipe stays private”Projections in a public git repo; no reuse licence statedPublic rolling ledger vs ep_nextFree core, paid tiersAPI, llms.txt, MCP (v0.2.0, unchanged since 5 Jun 2026)
Solio AnalyticsPartly described, model not publishedAgent endpoint, refreshed 4-hourly; licence not statedNo public graded ledgerFree tier, membership gatingNo-auth data endpoint
FPL ReviewPrivateNo open datasetOccasional articles (“Ultimate Truth”)Free lite model; solver paid (Patreon from €3.90/mo)Blocks AI crawlers
Fantasy Football HubPrivateNo open datasetMarketing claims, no public ledgerPaid (Starter £11.99/mo)No public API
Fantasy Football ScoutPrivateNo open datasetMarketing claims, no public ledgerPaid membershipNo public API

Where we are behind

Onside Arena has far more graded history than we do. They have been publishing a rolling ledger with tens of thousands of graded predictions; ours starts at gameweek 1 of this season and currently holds a single gameweek. A record of one week proves nothing yet, and we would rather say so than let the table imply otherwise.

Their infrastructure is ahead in places — a calibration page and a resolved entity on Wikidata, both of which we lack. Solio's model comes from the person who built the solver toolkit the community runs on. We are the newer, smaller project.

What we do claim is narrower and checkable: nobody else publishes the method, the licensed data, the graded record and free access at once.

How to check any of this

Our method is written out on the About page and the numbers behind every claim are downloadable from the data page under CC BY 4.0. Projections are frozen before each deadline and graded afterwards in the ledger, with the raw grading files linked per gameweek. Machines can read all of it through the JSON API and the MCP server.