fintraffic - GTFS transit data for Finland
ActiveAbout This Feed
fintraffic is the GTFS feed FINAP publishes for Finland: 4,122 routes, 66,912 stops, 188 transit agencies. BusMaps checks and corrects it every week and serves the result through the API and as GTFS files.
Valid from August 1, 2018 to December 31, 2027.
Checked and corrected automatically. How we do it →
One API for this feed
The API behind this page serves the same 4,122 routes and 66,912 stops: stops near a point, departures, trips, timetables and the GTFS files. The requests below use the coordinates of this feed.
- Stops around a point Free
Stops within a radius of a coordinate.
GET /v1/stopsInRadius?location=62.0631,25.0554&radius=1000 - Next departures Free
Departures at the nearby stops, with real-time delays where the agency publishes them.
GET /v1/nextDepartures?location=62.0631,25.0554&radius=500&results=30 - A-to-B trip planning Free
Itineraries between two points on this network.
GET /v1/routes?origin=62.0631,25.0554&destination=64.0719,26.5324 - Route timetables Pro
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=fintraffic - AI agents (MCP) Free
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.
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 FINAP. The API returns either one for ?feedName=fintraffic. Documentation →
Enhanced & Validated Recommended
Updated 2026-08-21Cleaned, corrected, and validated against GTFS specifications. View corrections.
Original Source
Obtained 2026-08-20Unmodified GTFS data from official sources. May contain errors or inconsistencies.
Overlapping Feeds
Other feeds that share stops or routes with this one.
| Feed | Stops Overlap | Routes Overlap |
|---|---|---|
| trains-fin | 157 (0.24%) | 237 (5.75%) |
| fintraffic-kela-suuret2 | 3344 (5.01%) | 128 (3.11%) |
| oulun-joukkoliikenteen | 1629 (2.44%) | 78 (1.89%) |
| invataksi-niemi-oy | 141 (0.21%) | 46 (1.12%) |
| helsingin-seudun-liikenne-hsl | — | 40 (0.97%) |
| digital-ocean2 | 940 (1.41%) | 36 (0.87%) |
| yvaskyla | 1219 (1.83%) | 34 (0.82%) |
| kymen-charterline-oy | 699 (1.05%) | 33 (0.8%) |
| liikennevirasto | 602 (0.9%) | 22 (0.53%) |
| city-of-kajaani | 509 (0.76%) | 6 (0.15%) |
| flix-bus-eu | — | 3 (0.07%) |
| digital-ocean | 118 (0.18%) | 1 (0.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?
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.