Skip to content

About

An independent EA FC Pro Clubs archive, built by somebody who plays it

Why this exists

EA publishes your club’s last ten matches and nothing else. Play an eleventh and the first one is gone — not archived, not paginated, gone. There is no endpoint that returns it, no parameter that asks for more, and no way to answer a question as ordinary as “are we better than we were in March”.

Clublytics exists to write those matches down before they disappear. Every time somebody looks a club up, the matches EA is currently serving are stored — and because each match payload carries the full player rows for both sides, looking up one club quietly preserves its opponents too. There is no crawler, because EA publishes no list of clubs to crawl. The archive grows because people use it.

That is the whole difference between this and a stats viewer. A viewer shows you what EA is showing you right now. This holds what EA has already thrown away.

Who builds it

Clublytics is built and run by Khalid, a Pro Clubs player, as an independent project. It is not a company and not a team — one person writes the code, chooses what goes on the site, and answers the contact form.

That matters for reading the rest of the site. The decisions here are opinionated, and the opinions come from playing the game: why a rating means something different for a defender than a striker, why three good matches should not outrank four hundred, why a card carries the number that earned it rather than a nickname on its own. Where a judgement has been made, the methodology page says what it was and why.

What it does that EA does not

Keeps a history. Form over a season, an opponent you have played nine times, a player’s record across every club they have been in — all of it is reconstructed from stored matches, not from EA’s ten.

Compares like with like. Percentiles are worked out against players in the same position, because the median defender completes about half the passes of the median midfielder and ranking them together tells a defender they are bad at something they are not being asked to do.

Decodes what EA leaves packed. Several counters — interceptions, dribbles, crosses — are not named fields. They arrive inside a packed event string, and the site reads them out. That is where the numbers no other tracker shows come from.

Says when it does not know. A player with four stored matches gets a figure that says four stored matches, not a confident average. Rankings pull small samples toward the middle before ordering them. An empty state that will fill in later says so.

What it is not

Not affiliated with, endorsed by, or connected to EA Sports. All match data comes from EA’s own public Pro Clubs endpoints, and every club and player name on the site is published by EA.

There are no club crests and no player photographs anywhere on the site, and there will not be. EA’s crest asset ids do not resolve to anything public, and the identifier that does resolve returns the badge of the real-world team whose kit a club borrowed — which would put a Premier League crest on a Sunday-league club. A recognisable badge belonging to somebody else is worse than no badge.

Paying for it

EA refuses connections from most home addresses, so the site runs on a paid server. It is free to use and needs no account to browse: every club page, every player page, the leaderboard and the guides are open to anybody who arrives.

Costs are covered by advertising, by an affiliate link disclosed wherever it appears, and by Pro, which removes the advertising and opens the deeper figures for the people who would rather pay than be sold to. That is the whole arrangement, and it is stated here because a site funded by advertising should say so on the page about itself rather than leave a reader to work it out from the page.