keiobus - GTFS transit data for Japan

Active
Public-transport-open-data-center Japan July 31, 2026 — December 31, 2026

About This Feed

The keiobus GTFS feed by Public-transport-open-data-center provides structured public transit data for Japan, covering 254 routes, 2,892 stops, and 1 transit agencies. Formatted according to the General Transit Feed Specification (GTFS), this dataset is ready for transit apps, routing engines, urban planning tools, and AI agents / LLM applications.

Valid from July 31, 2026 to December 31, 2026. Suitable for production use in transit applications, GTFS editors, and GTFS-RT integrations.

Data is automatically validated and corrected. View our quality pipeline →

Transit map showing keiobus routes and stops in Japan
Explore 254 routes, 2,892 stops, and 1 agencies

Browse routes, stops, and agencies from this feed. Public pages show merged data from all feeds. Sign in for per-feed details useful for GTFS integration and debugging.

Sign in to access →

Download this feed through the BusMaps API

Enhanced GTFS, source GTFS, GeoJSON, and validation reports are available through the API.

Use ?feedName=keiobus to request this feed. View API documentation.

Enhanced & Validated Recommended

Updated 2026-08-01

Cleaned, corrected, and validated against GTFS specifications. View corrections.

ZIP GTFS Feed - Corrected & Enriched
6.28 MB
Available through API only This work is licensed under Custom_license. Content Hash: c4d17c6671dd6d3c
ZIP Validation Report
0.04 MB
Available through API only
0Errors
30,626Warnings
3,127Info
Top Issues
non ascii or non printable char30,302
mixed case recommended field181
missing recommended field143
GeoJSON GeoJSON Data
0.06 MB
Available through API only

Original Source

Obtained 2026-07-23

Unmodified GTFS data from official sources. May contain errors or inconsistencies.

ZIP GTFS Source Data
5.55 MB
Available through API only License: Custom_license Content Hash: c6b457e53a77f984
ZIP Validation Report
0.05 MB
Available through API only
0Errors
478,158Warnings
2,915Info
Top Issues
missing timepoint value447,013
non ascii or non printable char30,854
missing recommended field143

Use This Feed from AI Agents

This feed is also served through the BusMaps MCP server: point Claude, ChatGPT, Gemini or any MCP client at https://mcp.busmaps.com/mcp and your agent can plan routes, read departures, and query this network in plain language.

About the MCP server →

Overlapping Feeds

Feeds that share stops or routes with this dataset.

Feed Stops Overlap Routes Overlap
odakyubus-aiis 2 (0.07%) 8 (3.15%)
kantobus 2 (0.79%)
seibubus 1 (0.39%)
toei 1 (0.39%)
kokubunjicity-kokubunji-city-bunbus 4 (0.14%)
Build real-time departures into your app Free API Access →

Frequently Asked Questions

What is GTFS data?

General Transit Feed Specification (GTFS) is an open data format for public transit schedules and geographic information. Created by Google and TriMet, it enables transit agencies to publish interoperable data for applications, trip planners, and mobility analytics tools.

What is the difference between enhanced and source data?

Source data is the original GTFS feed obtained from the transit agency or official provider. The enhanced version has been processed to fix errors, remove inconsistencies, and ensure compliance with GTFS specifications. We recommend the enhanced version for production applications.

Can I use this data in my application?

Data usage depends on the license specified by the original provider. Check the license information in the download section. Many GTFS feeds use open data licenses that allow free use with attribution. Always verify the license terms before integration.

How do I validate a GTFS feed?

Each feed includes a validation report documenting errors and warnings. You can also use the MobilityData GTFS Validator for independent validation. Enhanced feeds have already been processed to resolve the most critical validation issues.

All data on this site comes from publicly available sources. If a file was posted in error, has an incorrect license, or lacks correct source attribution, please contact us and we will correct it.