Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1162942

K League 1·Regular Season - 7
Suwon City FC crest
Suwon City FCHOME
1:0
Match Finished
HT 0-0
Daejeon Citizen crest
Daejeon CitizenAWAY
Sun, Apr 14 · 05:00 UTCUnknown26°CRefereePark Byung-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

Suwon City FC

4-2-3-1
  1. Ahn Joon-SooG
  2. Park Cheol-WooD
  3. Kwon Kyung-WonD
  4. Kim Tae-HanD
  5. Lee YongD
  6. Lee Jae-WonM
  7. Jeong Seung-WonM
  8. Anderson OliveiraM
  9. Yoon Bit-GaramM
  10. Kim Joo-YeopM
  11. J. MonrealF

Daejeon Citizen

4-4-2
  1. Lee Chang-GeunG
  2. Oh Jae-SukD
  3. A. KrivotsyukD
  4. A. CalverD
  5. Lee Jung-TaekD
  6. Farley RosaM
  7. Kim Han-SeoM
  8. Ju Se-JongM
  9. Kim Seung-DaeM
  10. Lee Hyeon-SikF
  11. Gong Min-HyunF

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-04-13T05: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.

838b1e2901bb79e9822be8d9f505cbfbec0c4ee8f5df7110431a1d43f0147e53
✓ 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.