Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1386132

League Two·Regular Season - 12
Fleetwood Town crest
Fleetwood TownHOME
3:2
Match Finished
HT 1-1
Harrogate Town crest
Harrogate TownAWAY
Sat, Oct 11 · 14:00 UTCUnknown14°CRefereeD Drysdale

◆ 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

Fleetwood Town

3-4-1-2
  1. Player 18173G
  2. Player 440035D
  3. J. BoltonD
  4. H. HolgateD
  5. Player 19888M
  6. Player 18535M
  7. Player 328421M
  8. Player 45259M
  9. M. Virtue-ThickF
  10. Player 553695
  11. J. NorwoodF

Harrogate Town

4-2-3-1
  1. J. BelshawG
  2. Player 274224D
  3. Player 346525D
  4. A. O'ConnorD
  5. W. BurrellD
  6. Player 20029M
  7. B. MorrisM
  8. Player 194498M
  9. C. McAlenyM
  10. S. Duke-McKennaM
  11. J. MuldoonF

Fleetwood Town named a notably stronger XI than its 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 2025-10-10T14: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.

9bfc776643d162400d42818af7b2cce6b4d23dafa36cb63224c6d5328bbc7940
✓ 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.