Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1163062

K League 1·Regular Season - 27
Ulsan Hyundai FC crest
Ulsan Hyundai FCHOME
1:2
Match Finished
HT 0-1
Suwon City FC crest
Suwon City FCAWAY
Sun, Aug 18 · 10:00 UTCUnknown27°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-1-4-1
  1. Jo Hyeon-WooG
  2. Kim Min-WooD
  3. Kim Young-GwonD
  4. Hwang Seok-HoD
  5. Yun Il-LokD
  6. Won Du-JaeM
  7. Jang Si-YoungM
  8. D. BojanićM
  9. Lee Gyu-SeongM
  10. Kim Min-JunM
  11. Joo Min-KyuF

Suwon City FC

4-2-3-1
  1. Ahn Joon-SooG
  2. Park Cheol-WooD
  3. L. JacksonD
  4. Choi Kyu-BaekD
  5. Lee YongD
  6. Lee Jae-WonM
  7. Son Jun-HoM
  8. Anderson OliveiraM
  9. Kang Sang-YunM
  10. Jeong Seung-WonM
  11. Jung Seung-BaeF

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 2024-08-17T10: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.

6b346a63123befb8416475578fb6c2598c6698f483030664c3df23c0f5859cbe
✓ 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.