Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1438654

AFC Champions League Two·Group Stage - 6
Kaya crest
KayaHOME
0:1
Match Finished
HT 0-1
Pohang Steelers crest
Pohang SteelersAWAY
Thu, Dec 11 · 12:15 UTCUnknownRefereeA. Al Athbah

◆ 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

Kaya

4-1-4-1
  1. Player 122496G
  2. Player 568552D
  3. Player 49197D
  4. Player 164257D
  5. Player 296788D
  6. Player 73193M
  7. Player 124212M
  8. Player 105466M
  9. Player 293451M
  10. Player 169146M
  11. Player 105465F

Pohang Steelers

4-4-2
  1. Hwang In-JaeG
  2. Kang Min-JunD
  3. Han Hyeon-SeoD
  4. Shin Kwang-HoonD
  5. Eo Jeong-WonD
  6. Baek Sung-DongM
  7. Kim Dong-JinM
  8. Lee Chang-WooM
  9. Kim In-SungM
  10. Lee Ho-JaeF
  11. An Jae-JunF

Pohang Steelers 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 2025-12-10T12:15: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.

54c1cc426462a8c052d2b29d5fab1058580ef106f247bc80135f4638f522b730
✓ 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.