Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #816302

Super League·Relegation Round - 3
Tianjin Teda crest
Tianjin TedaHOME
1:2
Match Finished
HT 0-1
Qingdao Huanghai crest
Qingdao HuanghaiAWAY
Sat, Dec 18 · 07:30 UTCUnknown4°CRefereeLiang Caiwei

◆ 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

Tianjin Teda

5-3-2
  1. Fang JingqiG
  2. Player 13061M
  3. Player 34770F
  4. M. VejinovićM
  5. T. KádárD
  6. Player 12833D
  7. Player 12846D
  8. Player 12751M
  9. Player 12658F
  10. Song YueD
  11. Player 80923D

Qingdao Huanghai

4-4-2
  1. Player 78906G
  2. Player 12664M
  3. Player 78843D
  4. Player 13103D
  5. Player 12992D
  6. Player 20853M
  7. Player 12571M
  8. Player 51059F
  9. Player 78789D
  10. Player 12977M
  11. Player 14403F

Qingdao Huanghai 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 2021-12-17T07: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.

072398fc2308322e277527a9c55f7f180de41a285a7345a1e2b4913d614869ce
✓ 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.