Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #828319

K League 1·Regular Season - 22
Jeonbuk Motors crest
Jeonbuk MotorsHOME
3:2
Match Finished
HT 1-0
Seongnam FC crest
Seongnam FCAWAY
Sat, Jul 16 · 09:00 UTCUnknown26°CRefereeKim Young-Su

◆ 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

Jeonbuk Motors

4-3-3
  1. Song Bum-KeunG
  2. Paik Seung-HoM
  3. Yun Young-SunD
  4. Kim Jin-SuD
  5. Choi Chul-SoonD
  6. Song Min-KyuF
  7. Park Jin-SeopD
  8. Kim Jin-KyuM
  9. GustavoF
  10. Modou BarrowF
  11. Kang Sang-YunM

Seongnam FC

5-4-1
  1. Kim Young-KwangG
  2. Kim Ji-SooD
  3. Lee Si-YoungD
  4. Park Soo-IlD
  5. Gwon Wan-GyuD
  6. Ma Sang-HoonD
  7. M. PalaciosF
  8. Goo Boon-Cheul
  9. M. RaičkovićM
  10. Kwon Soon-HyungM
  11. Jun Seong-SuM

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-07-15T09: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.

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