Skip to main content
← All predictions

J1 League · Regular Season - 13

Avispa Fukuoka crestAvispa FukuokavsSanfrecce Hiroshima crestSanfrecce Hiroshima

Kickoff: Wednesday, April 29, 2026 at 1:00 AM ET · Best Denki Stadium, Fukuoka

Outcome Probabilities

Confidence 5 out of 5 confidence

Home

Avispa Fukuoka

34%

Draw

Draw

29%

Away

Sanfrecce Hiroshima

37%

Lean: Sanfrecce Hiroshima · close call (3pp margin)

Expected goals: 1.31.4(total 2.7)
Upset risk: 5/10

Prediction Evolution

How the model's confidence changes as new info arrives

HomeDrawAway
25%50%75%?34%??T−48hT−24hPre-matchHalf-time

One snapshot logged so far · 3 more stages will appear as the kickoff approaches

Avispa's recent form (2 consecutive 0-2 home losses) is concerning, but the three component models show sharp disagreement (xG heavily favors away at 47.5%, Elo favors draw at 44.3%, Dixon-Coles anchors home at 33.6%), signaling low conviction overall. No injuries on either side. Modest upward adjustment to home win probability (+1.4pp) reflects home-venue stability in J1, but the disagreement between models and Avispa's poor recent scoring (0 goals in last 2 matches) warrant staying close to baseline and keeping confidence low.

SPX AI Quant Prediction Model (DC 0.81 / Elo 0.19 / xG 0) + Claude Haiku 4.5 · 55/45

T−24h stage hash · locked 4/28/2026, 1:05:29 AM

709a6e91e0498cc04a13adb460278b1356e517542e32a9cf126b0c02ca19ebe5

SPX AI Quant Prediction Model

DC 0.81 · Elo 0.19 · xG 0

H 33%D 30%A 37%

Dixon-Coles (Poisson)

H 34%D 26%A 40%

xG: 1.26 — 1.40

Elo (Davidson 3-way)

H 31%D 44%A 25%

Elo gap: +40 pts

xG-Poisson

H 27%D 25%A 48%

Expected goals: 1.13 — 1.57

LLM contextual review

H 35%D 28%A 37%

Based on recent form, news, injuries

Data quality score: 62/100 · verdict publish

Integrity Lock

This prediction's latest stage was generated at 2026-04-28T01:05:29.637Z 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.

709a6e91e0498cc04a13adb460278b1356e517542e32a9cf126b0c02ca19ebe5
✗ Hash mismatch — investigate

Verify yourself via the API.