Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1340834

K League 1·Regular Season - 23
Gwangju FC crest
Gwangju FCHOME
1:1
Match Finished
HT 1-0
Gimcheon Sangmu FC crest
Gimcheon Sangmu FCAWAY
Tue, Jul 22 · 10:30 UTCUnknown28°CRefereeDong Jun Lee, South Korea

◆ 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

Gwangju FC

4-4-2
  1. Kim Kyeong-MinG
  2. Sim Sang-MinD
  3. Min Sang-GiD
  4. Byeon Jun-SooD
  5. Jo Seong-KwonD
  6. Jung Ji-HunM
  7. Yu Je-HoM
  8. Choi Kyoung-RokM
  9. J. AsaniM
  10. Park In-HyeokF
  11. ReisF

Gimcheon Sangmu FC

4-2-3-1
  1. Lee Ju-Hyun
  2. Park Dae-WonD
  3. Lee Jung-TaekD
  4. Kim Kang-SanD
  5. Oh In-pyoD
  6. Maeng Seong-UngM
  7. Lee Seung-WonM
  8. Kim Seung-SubM
  9. Won Ki-JongM
  10. Lee Dong-JunM
  11. Park Sang-HyeokF

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 2025-07-21T10: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.

44fd3650dc59d7287ea8b018e55af7ce5eaeaa1d8d79d5fff6c456e906269af7
✓ 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.