Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1002845

K League 1·Regular Season - 24
Ulsan Hyundai FC crest
Ulsan Hyundai FCHOME
2:1
Match Finished
HT 2-0
Jeju United FC crest
Jeju United FCAWAY
Fri, Jul 21 · 10:30 UTCUnknown25°CRefereeKim Hee-Gon

◆ 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. Lee Myung-JaeD
  3. Kim Young-GwonD
  4. Kim Ki-HeeD
  5. Kim Tae-HwanD
  6. Kim Min-HyukM
  7. Lee Gyu-SeongM
  8. G. LudwigsonM
  9. Lee Dong-GyeongM
  10. Kang Yun-GuM
  11. Joo Min-KyuF

Jeju United FC

5-4-1
  1. Kim Dong-JunG
  2. Kim Dae-HwanD
  3. Chung WoonD
  4. Lim Chai-MinD
  5. Yeon Je-WoonD
  6. Rim Chang-WooD
  7. Han Jong-MuM
  8. Kim Geon-WoongM
  9. Kim Bong-SooM
  10. Kim Ju-KongM
  11. Seo Jin-SuF

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-07-20T10: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.

724da39009074063ae98d317ddb86850a3f5030681e4ea667ebabb573327b4bb
✓ 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.