Transit data by province
A first-pass source review of 81 provincial centres and metropolitan municipalities. Documented services, passenger portals and access blockers are listed separately. This is not a complete technical audit of every district or town municipality.
What does “live” mean?
For Istanbul vehicles, the municipality's GPS timestamp is checked. Izmir's live service doesn't send a GPS timestamp, so the fetch time is shown instead. In Gaziantep, the GAZİRAY timetable and GaziBis stations are connected; offline stations are never shown as available.
“No open API verified” doesn't mean no API exists. Tracking in Google Maps or in a municipality's own app doesn't by itself show that the data may be reused in another app.
The ULASAV national catalogue returned 403 during testing. These municipal services don't provide ticketing or payment for flights, intercity rail, private scooters or tours. ZUZU's wallet and booking flows are still demos.
| Province / municipality | Verification status | Findings and sources |
|---|---|---|
| Adana | Passenger portal found | The municipality's passenger portal lists lines, stops and metro information; no documented, reusable live data API has been verified. |
| Adıyaman | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Afyonkarahisar | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Ağrı | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Amasya | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Ankara | Passenger portal found | The EGO Cepte passenger service is available. Reuse terms and a documented open live data API have not been verified. |
| Antalya | Passenger portal found | The municipality has timetable and upcoming-vehicle pages; no documented live data API that other apps may reuse has been verified. |
| Artvin | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Aydın | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Balıkesir | Access not verified | The open data portal returned 502 during access testing. A live bus data API could not be verified. |
| Bilecik | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Bingöl | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Bitlis | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Bolu | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Burdur | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Bursa | Static data found | The Açık Yeşil catalogue is accessible. No reusable live bus service was verified in the transport category reviewed. |
| Çanakkale | Access not verified | The official catalogue includes bus stop and ÇABİS files. The catalogue API returned 502 during testing, so the data files could not be connected. |
| Çankırı | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Çorum | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Denizli | Static data found | Geographic and statistical files were found in the transport category. No live vehicle position or GTFS-RT service was verified. |
| Diyarbakır | Passenger portal found | A municipal passenger information or tracking service was found. A documented, reusable open live data service has not yet been verified. |
| Edirne | Passenger portal found | A municipal passenger information or tracking service was found. A documented, reusable open live data service has not yet been verified. |
| Elazığ | Passenger portal found | A municipal passenger information or tracking service was found. A documented, reusable open live data service has not yet been verified. |
| Erzincan | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Erzurum | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Eskişehir | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Gaziantep | Timetable / stations connected | GAZİRAY scheduled departures and stations are connected. The GaziBis station service is connected; all 7 stations were offline during testing. Live train and bus positions have not been verified. |
| Giresun | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Gümüşhane | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Hakkari | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Hatay | Passenger portal found | A municipal passenger information or tracking service was found. A documented, reusable open live data service has not yet been verified. |
| Isparta | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Mersin | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| İstanbul | Live feed | İETT: the line list, scheduled departures and per-line vehicle positions were tested and connected through a keyless SOAP service. |
| İzmir | Live feed | ESHOT live vehicles, upcoming buses, stops and timetables, plus İZDENİZ scheduled ferry departures and metro stations, are connected. The live bus response does not include a GPS timestamp. Tram lines, directions and station locations are also connected from the official open data API; this endpoint does not provide live tram positions. |
| Kars | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Kastamonu | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Kayseri | Static data found | The municipality's GTFS work and open data portal were found. An open download URL, the data calendar and a live API have not yet been verified. |
| Kırklareli | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Kırşehir | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Kocaeli | Access not verified | The open data portal returned 502 during access testing. Data contents and freshness could not be verified. |
| Konya | Static data found | An official GTFS feed was found. The catalogue holds a November 2025 package; as its validity for September 2026 services is unverified, it is not used for current departures. |
| Kütahya | Static data found | The open data portal includes transport location files. No live vehicle data has been verified. |
| Malatya | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Manisa | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Kahramanmaraş | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Mardin | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Muğla | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Muş | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Nevşehir | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Niğde | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Ordu | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Rize | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Sakarya | Passenger portal found | There is an official passenger tracking page and an open data catalogue. The public API root returned 403 during testing, so no live data integration was made. |
| Samsun | Passenger portal found | A municipal passenger information or tracking service was found. A documented, reusable open live data service has not yet been verified. |
| Siirt | Passenger portal found | A municipal passenger information or tracking service was found. A documented, reusable open live data service has not yet been verified. |
| Sinop | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Sivas | Passenger portal found | A municipal passenger information or tracking service was found. A documented, reusable open live data service has not yet been verified. |
| Tekirdağ | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Tokat | Passenger portal found | A municipal passenger information or tracking service was found. A documented, reusable open live data service has not yet been verified. |
| Trabzon | Passenger portal found | A municipal passenger information or tracking service was found. A documented, reusable open live data service has not yet been verified. |
| Tunceli | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Şanlıurfa | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Uşak | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Van | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Yozgat | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Zonguldak | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Aksaray | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Bayburt | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Karaman | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Kırıkkale | Passenger portal found | A municipal passenger information or tracking service was found. A documented, reusable open live data service has not yet been verified. |
| Batman | Passenger portal found | Municipal passenger guidance and announcements for the BATUS app were found. Check lines and times with the official service; no documented live data API that other apps may reuse has been verified. |
| Şırnak | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Bartın | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Ardahan | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Iğdır | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Yalova | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Karabük | Passenger portal found | A municipal passenger information or tracking service was found. A documented, reusable open live data service has not yet been verified. |
| Kilis | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Osmaniye | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
| Düzce | No open API verified | No documented, reusable open transit API was verified in the initial source review. This does not mean no such service exists. |
Statuses reflect findings on the research date; they are not ongoing monitoring or a service guarantee. The live screen shows the fetch time for every request. Source titles are shown as published, in Turkish.