J1 2026-27 -- round of 2026-09-02

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
Sep 02 10:00 Avispa Fukuoka Urawa Reds 37.2% 29.4% 33.4% not yet played
Sep 02 10:00 Cerezo Osaka Kashiwa Reysol 35.1% 24.7% 40.2% not yet played
Sep 02 10:00 Machida Kawasaki Frontale 53.3% 21.5% 25.2% not yet played
Sep 02 10:00 Shimizu S-Pulse FC Tokyo 37.4% 27.0% 35.6% not yet played
Sep 02 10:00 Chiba Okayama 24.1% 27.0% 48.9% not yet played
Sep 02 10:00 V-Varen Nagasaki Gamba Osaka 34.3% 23.0% 42.7% not yet played
Sep 02 10:00 Sanfrecce Hiroshima Nagoya Grampus 56.4% 24.2% 19.5% not yet played
Sep 02 10:00 Mito Kashima Antlers 29.3% 24.4% 46.3% not yet played
Sep 02 10:00 Yokohama F. Marinos Kyoto 45.1% 23.7% 31.2% not yet played
Sep 02 10:00 Verdy Vissel Kobe 24.7% 30.1% 45.2% 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-31 09:47 UTC
Trained as of (UTC)
2026-08-31 09:47 UTC
Model version
footy-ev-phase2-dc-tb-v1
params_hash
ea317b1dbde414553b28ff026b02ecdc2ba3b088e5d242b6cff416d721ed3f7f
File SHA-256
dd8eb930034ccf5e172500d40c6a9030fd2662dc1f039d15936da4fb54565393
Market snapshot SHA-256
4af3dd925130e5fe3e4baa5cdb23026eaab3986ca5d38c69b517748aefdfafff
Training window
1782 matches, 29 teams, since 2021
Publish gate
PASS

How to verify

This file is committed as predictions/j1_2026_2026-09-02.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.