Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #828241

K League 1·Regular Season - 9
Seongnam FC crest
Seongnam FCHOME
0:4
Match Finished
HT 0-1
Jeonbuk Motors crest
Jeonbuk MotorsAWAY
Sat, Apr 9 · 05:00 UTCUnknown25°CRefereeKim Woo-Sung

◆ 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

Seongnam FC

5-4-1
  1. Kim Young-KwangG
  2. Lee Ji-HunD
  3. Gwon Wan-GyuD
  4. Ma Sang-HoonD
  5. Kim Min-HyeokD
  6. Kwak Kwang-SeonD
  7. Park Yong-JiF
  8. Kang Jae-WooM
  9. Kim Min-HyukM
  10. Kwon Soon-HyungM
  11. Jun Seong-SuM

Jeonbuk Motors

3-4-3
  1. Song Bum-KeunG
  2. Kim Moon-HwanM
  3. Choi Bo-KyungD
  4. Kim Jin-SuD
  5. Kim Jin-KyuM
  6. T. KunimotoM
  7. Paik Seung-HoM
  8. Moon Seon-MinF
  9. Park Kyu-MinF
  10. GustavoF
  11. Park Jin-SeopD

Jeonbuk Motors named a modestly 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 2022-04-08T05: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.

55184fe26b81306e85819faa521dac300faf1dc48c1f7dc6458d4827df11f6cb
✓ 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.