seoul-bus - GTFS transit data for South Korea

Active
Seoul-Bus South Korea 2026년 8월 4일 — 2027년 12월 31일

About This Feed

seoul-bus is the GTFS feed Seoul-Bus publishes for South Korea: 718 routes, 12,616 stops, 264 transit agencies. BusMaps provides the original source through the API. Corrected and validated builds are not available in the API and require the data request form.

Valid from 2026년 8월 4일 to 2027년 12월 31일.

Checked and corrected automatically. How we do it →

One API for this feed

The API behind this page serves the same 718 routes and 12,616 stops: stops near a point, departures, trips, timetables and source GTFS files. The requests below use the coordinates of this feed.

  • Stops within a radius of a coordinate.

    GET /v1/stopsInRadius?location=37.5468,126.9803&radius=1000
  • Departures at the nearby stops, with real-time delays where the agency publishes them.

    GET /v1/nextDepartures?location=37.5468,126.9803&radius=500&results=30
  • Itineraries between two points on this network.

    GET /v1/routes?origin=37.5468,126.9803&destination=37.6197,127.0349
  • Directions, stop order and the schedule of one route.

    GET /v1/line?routeId={routeId}
  • The original source feed, source validation report, and provider links. Processed data is not returned.

    GET /v1/getGtfsFeedsDownloads?feedName=seoul-bus
  • Claude, ChatGPT or any MCP client asks this network questions in plain language.

    https://mcp.busmaps.com/mcp

Base URL https://capi.busmaps.com:8443. Send the key in the capi-key header. Route ids come from the responses above.

718
경로
12,616
Stops
264
Agencies

GTFS Data Products

Request enhanced data access

The API provides source files only. Submit the data request form to discuss enhanced or custom data, coverage, and delivery terms.

Open the data request form →

Enhanced & Validated Recommended

Updated 2026-09-02

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

ZIP GTFS Feed - Corrected & Enriched
1.78 MB
Access: Submit the data request form This work is licensed under Custom_license. Content Hash: ed10493496ab1643
ZIP Validation Report
0.03 MB
0 Errors
5,843 Warnings
5 Info
Top Issues
mixed case recommended field 5,843
trip headsign matches intermediate stop 5
GeoJSON GeoJSON Data
0.33 MB

Original Source

Obtained 1980-01-01

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

ZIP GTFS Source Data
2.19 MB
Available through API License: Custom_license Content Hash: 938f3523b69c7cb9
ZIP Validation Report
0.03 MB
Available through API
0 Errors
6,027 Warnings
8 Info
Top Issues
mixed case recommended field 6,018
missing bike allowance 9
trip headsign matches intermediate stop 5

Overlapping Feeds

Other feeds that share stops or routes with this one.

Feed Stops Overlap Routes Overlap
ktdb-korea 4377 (34.69%) 553 (77.02%)

Frequently Asked Questions

What is GTFS data?

GTFS, the General Transit Feed Specification, is the open format transit agencies use to publish schedules, stops and route shapes. Trip planners, routing engines and analytics tools read it directly.

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. API plans include source data only. Enhanced data requires a separate request through the data request form. Request access through the form →

Can I use this data in my application?

Source-data use depends on the licence set by the publisher; check it before integration. Enhanced and custom data is supplied under terms agreed for your coverage, delivery, and intended use.

How do I validate a GTFS feed?

Every feed here ships with a validation report of errors and warnings. For an independent check, run the MobilityData GTFS Validator. The enhanced feed has the critical issues resolved.

All data comes from public sources. If a file was posted in error, carries a wrong licence or lacks attribution, we will fix it.

Contact us →