Skip to main content
← All reports

SPX Quant Engine · Match Research Note · #893597

3. Lig - Group 2·
Kırıkkale Büyük Anadolu crest
Kırıkkale Büyük AnadoluHOME
1:1
Match Finished
HT 0-0
Bayrampaşaspor crest
BayrampaşasporAWAY
Sun, Apr 2 · 12:00 UTCKırklareli Atatürk Stadyumu18°CRefereeH. Erdoğan

◆ 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

Kırıkkale Büyük Anadolu

  1. Player 195234
  2. Player 142998
  3. Player 62776
  4. Player 143129
  5. Player 291517
  6. Player 144078
  7. Player 143270
  8. Player 107301
  9. Player 61909
  10. Player 107615
  11. Player 143078

Bayrampaşaspor

  1. Player 62707
  2. Player 62148
  3. T. Kalender
  4. Player 199555
  5. Player 63076
  6. Player 62452
  7. Player 62247
  8. Player 162002
  9. Player 70527
  10. Player 279746
  11. Player 351347

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 2026-06-09T02:36:46.517Z 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.

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