Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1417321

FA WSL·Regular Season - 21
Tottenham Hotspur W crest
Tottenham Hotspur WHOME
2:1
Match Finished
HT 2-0
London City Lionesses crest
London City LionessesAWAY
Sun, May 3 · 11:00 UTCUnknown18°CRefereeM. Wilson

◆ SPX Quant Forecast

Free account

Sign in to read the full archive

The full settled-report archive, SHA256 verification, match facts, the Quant Arena and your personal accuracy dashboard are free — just create an account.

Match Analysis

Timeline, stats, lineups, player ratings and AI insights — live during the match.

SPX xG

Lineup Analysis

Tottenham Hotspur W

  1. Player 68918
  2. Player 587798
  3. Player 557252
  4. Player 81852
  5. Player 299522
  6. Player 530587
  7. Player 81850
  8. Player 380018
  9. Player 264886
  10. Player 298951
  11. Player 316128

London City Lionesses

  1. Player 144853
  2. Player 99918
  3. Player 622901
  4. Player 440564
  5. Player 81822
  6. Player 68578
  7. Player 68856
  8. Player 68583
  9. Player 621025
  10. Player 393743
  11. Player 557235

Both sides named an XI close to their recent baseline.

Post-Match Deep Analytics

Key absences, beyond-outcome calls and per-player tactical visuals — the shot-based panels finalize from official match data after full-time.

Shot-quality scatter · pass-success grid · key absences · expected shots · beyond-outcome calls — the full tactical deep-dive is a Premium feature →

Integrity Lock

This report's latest stage was generated at 2026-05-02T11:00:00.000Z and its canonical JSON hashed with SHA256. Each prior stage carries its own hash inside the corresponding tab so you can audit every step independently.

022483e084c7737b5d082f5e4825585174ab153b97b9f9a5da2b9fca369382ec
✓ Hash verified — contents unchanged

Model v4.01 · Public beta: every published forecast is timestamped and model-versioned. When the beta period ends (June 2027), per-fixture pre-kickoff forecasts become immutable under our SHA256 audit policy.

Verify yourself via the API.