Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1002730

K League 1·Regular Season - 4
Ulsan Hyundai FC crest
Ulsan Hyundai FCHOME
3:0
Match Finished
HT 1-0
Suwon City FC crest
Suwon City FCAWAY
Sun, Mar 19 · 07:30 UTCUnknown16°CRefereeKo Hyung-Jin

◆ 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

Ulsan Hyundai FC

4-2-3-1
  1. Jo Hyeon-WooG
  2. Seol Yung-WooD
  3. Kim Young-GwonD
  4. Jung Seung-HyunD
  5. Kim Tae-HwanD
  6. Park Yong-Woo
  7. D. BojanićM
  8. G. LudwigsonM
  9. Kim Min-HyukM
  10. Jang Si-YoungM
  11. Joo Min-KyuF

Suwon City FC

3-4-3
  1. No Dong-GeonG
  2. L. JacksonD
  3. Park Byung-HyunD
  4. Kim Hyun-HunD
  5. Park Cheol-WooM
  6. Yoon Bit-GaramM
  7. Oh In-pyoM
  8. Lee YongM
  9. Lee Dae-GwangF
  10. L. VeldwijkF
  11. Jeong Eun-WooF

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 2023-03-18T07:30: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.

b1241457a7fadad335679c738ff9b3883ea5b0c069adc65c38d6dfdf99ee85fc
✓ 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.