Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1311093

K League 1·Relegation Round - 4
Incheon United crest
Incheon UnitedHOME
1:2
Match Finished
HT 1-2
Daejeon Citizen crest
Daejeon CitizenAWAY
Sun, Nov 10 · 07:30 UTCUnknown17°CRefereeKim Yong-Woo

◆ 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

Incheon United

3-4-3
  1. Lee Bum-Soo
  2. Oh Ban-SukD
  3. Kim Dong-MinD
  4. Kim Yeon-SooD
  5. Min Kyeong-hyeonM
  6. Kim Do-HyeokM
  7. Lee Myung-JooM
  8. Hong Si-HooM
  9. Gerso FernandesF
  10. S. MugošaF
  11. Kim Min-SeogF

Daejeon Citizen

3-4-3
  1. Lee Chang-GeunG
  2. A. KrivotsyukD
  3. Kim Hyun-WooD
  4. Kim Moon-HwanD
  5. Kang Yun-SungM
  6. Victor BobsinM
  7. Lee Soon-MinM
  8. Yoon Do-YongM
  9. Choi Geon-JooF
  10. M. IshidaF
  11. Kim Jun-BeomF

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-11-09T07: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.

55d703211728e2699abe2573f6c08c2819889cc81aaf4e56bc7db416e5f01762
✓ 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.