J1 2026-27 -- round of 2026-08-29

Match probabilities for Japan's J1 League. 10 fixtures, fixed before kickoff. The market is measurably better than this model — a disagreement below is a question, not an answer. Full caveat & numbers.

Calibrated model probabilities. Kickoff times are UTC, 2026. No market odds are shown here — see Methodology for why.
Kickoff Home Away P(H) P(D) P(A) Result
Aug 29 09:00 Mito Machida 22.7% 24.4% 52.9% not yet played
Aug 29 09:00 Gamba Osaka Sanfrecce Hiroshima 29.1% 25.2% 45.7% not yet played
Aug 29 09:30 V-Varen Nagasaki FC Tokyo 38.0% 26.0% 36.1% not yet played
Aug 29 09:30 Shimizu S-Pulse Kashiwa Reysol 30.1% 26.8% 43.1% not yet played
Aug 29 10:00 Kyoto Avispa Fukuoka 44.2% 28.6% 27.2% not yet played
Aug 29 10:00 Vissel Kobe Cerezo Osaka 52.6% 24.2% 23.2% not yet played
Aug 29 10:00 Nagoya Grampus Okayama 40.3% 28.8% 30.9% not yet played
Aug 29 10:00 Kawasaki Frontale Chiba 74.8% 14.1% 11.1% not yet played
Aug 29 10:00 Verdy Kashima Antlers 23.1% 27.2% 49.7% not yet played
Aug 29 10:00 Urawa Reds Yokohama F. Marinos 39.8% 24.7% 35.5% not yet played

Over 3,882 backtested J1 matches (2014–2025-26), the closing betting market scored 0.0044 RPS points better than this model on average (95% CI [0.0026, 0.0060]) — see Methodology. This model has no information the market lacks: it does not see injuries, lineups, suspensions or travel. The bold figure in each row is only the most likely of three outcomes, not advice — in most football matches the most likely single outcome still loses more often than it wins.

Metadata & verification

Published (UTC)
2026-08-24 16:35 UTC
Trained as of (UTC)
2026-08-24 16:35 UTC
Model version
footy-ev-phase2-dc-tb-v1
params_hash
ea317b1dbde414553b28ff026b02ecdc2ba3b088e5d242b6cff416d721ed3f7f
File SHA-256
0b0a9b53abe230d26cd5d277909ba97053451b67be0312a8db066296a8d5df5d
Market snapshot SHA-256
f7d53a91669856ba71fe29d7c9479d66093752d8dc8912cea4dd868784395864
Training window
1772 matches, 29 teams, since 2021
Publish gate
PASS

How to verify

This file is committed as predictions/j1_2026_2026-08-29.json in the project's git repository, with the SHA-256 shown above. On its own, a git commit timestamp is not strong third-party evidence that a prediction existed before kickoff — the author can set it to any date. Independent timestamping (OpenTimestamps), Wayback Machine archiving and a GitHub Actions server-time witness are part of this project's published plan for closing that gap (design document, section 3) and are not yet wired into this build. Until they are, verify what you can today: recompute the SHA-256 of the committed file yourself and confirm it matches the value above, and read the raw JSON — nothing on this page is derived from anything else.