Methodology & Data Sources

sbc.so is not affiliated with or endorsed by Electronic Arts. Everything below describes where our numbers actually come from and, just as importantly, what we cannot yet verify.

Player database

Player ratings, potential, positions, clubs, countries, age, and physical attributes come from public football game databases, not from EA directly. We store overall rating, potential, position codes, club, country, age, height, weight, and - where available - preferred foot, weak foot, and skill moves.

What we label "Career Mode value" and "Career Mode weekly wage" are exactly that: Career Mode figures, not Ultimate Team market prices. We never present these as FUT coin prices.

PAC/SHO/PAS/DRI/DEF/PHY: these headline attributes are computed from real per-attribute sub-stats (crossing, finishing, ball control, and so on) using the standard published FIFA/FC formula, and are shown only for players we have that source data for - we never approximate or invent the underlying attributes themselves. League membership is not shown as a database fact, since we don't yet have a maintained, source-backed club-to-league mapping.

SBC catalog and requirements

SBC listings (challenge name, reward, estimated cost, expiration) are synced from public SBC tracking sites. Requirement text for each individual challenge (e.g. "Squad Rating: Min 90", "# of players from Real Madrid: Min 1") is captured directly from those sites' own challenge pages, not generated or guessed.

The SBC catalog is refreshed on a schedule, not continuously. The catalog page always shows the timestamp of the last successful sync, and estimated costs older than 24 hours are flagged as possibly outdated rather than presented as current.

How the solver checks requirements

When you generate a solution, we check the assembled squad against every requirement string scraped for that challenge and report one of three outcomes per requirement:

  • Met - we have the data needed to confirm the squad satisfies it.
  • Not met - we have the data needed to confirm it does not.
  • Unverifiable - we cannot check it with the data we currently store (most commonly card rarity/version requirements like "Min 1 TOTW player", since we don't track card rarity).

A solution is never presented as satisfying a requirement we didn't actually check. If any requirement is confirmed unmet, the overall result is "not met" even if other requirements pass.

A known gap: our market player pool's greedy squad-building algorithm doesn't specifically search for players matching a club, nation, or league requirement - it optimizes for rating and cost per position. If it doesn't happen to pick a qualifying player, a genuinely satisfiable requirement can still show as "not met" rather than a false pass.

Pricing

Where a player's market price is genuinely unknown, we say so - solutions show "Price unknown" rather than a fabricated cost. We do not currently have a live FUT coin market price feed; until we do, we won't claim a solution is the "cheapest" possible squad.

Corrections

Spot something wrong? Email us at cjstudiodesigns@gmail.com with the page URL and what looks off - we'd rather fix it than leave it live.