Sanko Bus (産交バス)

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

1. Add the required column named in the finding to the flagged file.

   A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.

   Effort: Often an export setting; ask your vendor if it recurs.

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   4612 of 4612 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

   Effort: A column in stops.txt; your scheduling software likely has it.

3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

   14158 of 14158 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

   Effort: A default or per-trip field in your export.

Key facts

Feed URL

https://api.gtfs-data.jp/v2/organizations/sankobus/feeds/sankobus/files/feed.zip?rid=current

Last checked

2026-07-19

Service window

93 days of service data remain. Last service date 2026-10-20.

Feed version

20260701_20260719

Location

Kumamoto, Japan