J1 2026-27 -- round of 2026-09-11

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 11 10:00 Vissel Kobe Kashima Antlers 41.3% 27.5% 31.2% not yet played
Sep 11 10:00 Kyoto Kashiwa Reysol 39.4% 26.2% 34.4% not yet played
Sep 12 09:00 Mito Kawasaki Frontale 43.8% 21.3% 34.9% not yet played
Sep 12 09:30 Shimizu S-Pulse Avispa Fukuoka 34.5% 30.7% 34.7% not yet played
Sep 12 10:00 Sanfrecce Hiroshima Cerezo Osaka 54.7% 24.3% 21.0% not yet played
Sep 12 10:00 Machida Yokohama F. Marinos 52.8% 23.2% 24.0% not yet played
Sep 12 10:00 Gamba Osaka FC Tokyo 40.3% 25.3% 34.3% not yet played
Sep 12 10:00 V-Varen Nagasaki Nagoya Grampus 32.1% 23.6% 44.3% not yet played
Sep 13 09:00 Verdy Chiba 48.8% 26.9% 24.3% not yet played
Sep 13 09:30 Urawa Reds Okayama 47.8% 26.6% 25.6% 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-09-10 07:49 UTC
Trained as of (UTC)
2026-09-10 07:49 UTC
Model version
footy-ev-phase2-dc-tb-v1
params_hash
ea317b1dbde414553b28ff026b02ecdc2ba3b088e5d242b6cff416d721ed3f7f
File SHA-256
a56cf7b2b675307b0c94f18949a2893791c98e4695824fd7cf8a8b20281b037f
Market snapshot SHA-256
68b8d9474d40dfd3ff6e6d75a5852f5903d9d207375d4b66e0dbb913232b159e
Training window
1812 matches, 29 teams, since 2021
Publish gate
PASS

How to verify

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