GTFS Scorecard
← All agencies

Japan

379 feed scorecards · 74.8 out of 100 average · 44 need attention

The average and grade distribution use 353 canonical, non-duplicate feed scorecards under one producer contract: rubric 1.3, scoring profile gtfs-scorecard-1.3, MobilityData gtfs-validator 8.0.1, reader archive profile raw-v1, and measured categories Correctness, Freshness, Rider experience. Every member remains listed below.

Scope: 379 reviewed feed records tracked in Japan. This page measures those records, not operators, routes, or all public transport in Japan, and it is not a claim that GTFS Scorecard covers Japan.

Realtime health 26 monitored

All 26 feed records here with a realtime endpoint configured have been sampled by the monitor. Least reliable first. Reachability, how far behind each feed's own timestamp runs, and how much of the scheduled service appears in it. Sampled on a schedule rather than continuously, and it changes no grade.

Across the monitored feeds: median uptime 100.0%, median lag 14s.

Fixes shared across this group

The same fix shows up in more than one agency's top 3 here, often the same export setting or scheduling-software step. Worth raising once with every agency it touches.

2 more shared fixes not shown here; see the full list at country-jp.json.

Feed scorecards: attention first, then alphabetical