This feed has expired Service dates: 2019-01-01 - 2024-12-31

ibb-istanbul - GTFS transit data for Turkey

Expired
IBB Turkey 1 Ocak 2019 — 31 Aralık 2024

About This Feed

ibb-istanbul is the GTFS feed IBB publishes for Turkey: 468 routes, 6,901 stops, 6 transit agencies. BusMaps checks and corrects it every week and serves the result through the API and as GTFS files.

Active from 1 Ocak 2019 to 31 Aralık 2024; the schedule has ended. The files stay available for analysis.

Checked and corrected automatically. How we do it →

One API for this feed

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

  • Stops within a radius of a coordinate.

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

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

    GET /v1/routes?origin=41.0183,28.9913&destination=41.0895,29.2228
  • Directions, stop order and the schedule of one route.

    GET /v1/line?routeId={routeId}
  • GTFS files Free

    The corrected feed, the source feed, GeoJSON and the validation reports.

    GET /v1/getGtfsFeedsDownloads?feedName=ibb-istanbul
  • 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.

Per-feed pages: 468 routes, 6,901 stops, 6 agencies

Public pages merge every feed. Sign in to browse this feed on its own, which helps when you integrate or debug it.

Sign in →

GTFS files of this feed

Two builds: the copy BusMaps corrected and validated, and the original from IBB. The API returns either one for ?feedName=ibb-istanbul. Documentation →

Enhanced & Validated Recommended

Updated 2026-08-21

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

ZIP GTFS Feed - Corrected & Enriched
3.38 MB
Available through API only This work is licensed under Custom_license. Content Hash: 4f6242707a78aa08
ZIP Validation Report
0.02 MB
Available through API only
0Errors
397Warnings
0Info
Top Issues
route short name too long372
expired calendar16
mixed case recommended field5
GeoJSON GeoJSON Data
0.22 MB
Available through API only

Original Source

Obtained 2026-08-18

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

ZIP GTFS Source Data
4.46 MB
Available through API only License: Custom_license Content Hash: 61581de05c2983e1
ZIP Validation Report
0.06 MB
Available through API only
148,115Errors
1,022Warnings
0Info
Top Issues
invalid character147,859
decreasing shape distance184
start and end range out of order64

Overlapping Feeds

Other feeds that share stops or routes with this one.

Feed Stops Overlap Routes Overlap
iett 2 (0.03%) 29 (6.2%)

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?

The source feed is what the agency published. The enhanced feed is the same data after BusMaps fixed the errors and inconsistencies and checked it against the GTFS specification. Use the enhanced feed in production.

Can I use this data in my application?

That depends on the licence the publisher set; you find it next to the files above. Most GTFS feeds allow free use with attribution. Check the licence before you integrate.

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, contact us and we will fix it.