Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #1181156

League One·Regular Season - 29
Guangzhou Evergrande FC crest
Guangzhou Evergrande FCHOME
3:1
Match Finished
HT 2-0
Yanbian Longding crest
Yanbian LongdingAWAY
Sat, Oct 26 · 06:30 UTCUnknown11°CRefereeGu Zhongchao

◆ 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

Guangzhou Evergrande FC

  1. Player 368279
  2. R. Sadauskas
  3. Player 402511
  4. Player 277687
  5. Player 292446
  6. Player 311059
  7. Player 386750
  8. Player 425865
  9. Player 460905
  10. J. Alegría
  11. Player 417043

Yanbian Longding

  1. Player 78974
  2. Player 12662
  3. Player 79025
  4. Player 12481
  5. Player 417692
  6. Player 78938
  7. Player 78751
  8. Player 417152
  9. V. Arboleda
  10. Player 12881
  11. Player 461743

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-10-25T06: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.

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