Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1340996

Super League·Regular Season - 13
Yunnan Yukun crest
Yunnan YukunHOME
2:0
Match Finished
HT 1-0
Meizhou Kejia crest
Meizhou KejiaAWAY
Fri, May 16 · 12:00 UTCUnknown22°CRefereeKai He, China

◆ 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

Yunnan Yukun

4-3-2-1
  1. Player 117155G
  2. Tsui Wang KitD
  3. José MartínezD
  4. Player 370187D
  5. Dilmurat MawlanyazD
  6. O. Sæter
  7. NenéM
  8. Player 12942M
  9. Player 560830
  10. Alexandru Ioniţă IIM
  11. O. MarituF

Meizhou Kejia

4-4-2
  1. Player 12642G
  2. Player 12940D
  3. B. JočićD
  4. Player 13042D
  5. Yue Tze NamD
  6. J. MbekeliM
  7. Player 12490M
  8. Player 341385M
  9. Player 13052M
  10. Rodrigo Henrique
  11. Yang ChaoshengF

Yunnan Yukun named a notably 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-05-15T12: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.

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