fintraffic — GTFS Transit Data for Finland

Active
FINAP Finland July 1, 2014 — December 31, 2027

About This Feed

The fintraffic GTFS feed by FINAP provides structured public transit data for Finland, covering 3340 routes and 59252 stops operated by 174 transit agencies. Formatted in the General Transit Feed Specification (GTFS) standard, this dataset is ready for integration with transit apps, routing engines, and urban planning tools.

Valid from July 1, 2014 to December 31, 2027. 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 fintraffic routes and stops in Finland
Explore 3,340 routes, 59,252 stops, 174 agencies

Browse routes, stops, and agencies from this specific feed. Public pages show merged data from all feeds — sign in to access per-feed breakdowns useful for GTFS integration and debugging.

Sign in to access →

Download Data

Enhanced & Validated Recommended

Updated 2026-07-03

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

ZIP GTFS Feed — Corrected & Enriched
123.86 MB
Download GTFS
This work is licensed under a Busmaps_licence_v1. Content Hash: 1dfb547889a64cf66895f236a29491a581a2f66a
ZIP Validation Report
0.12 MB
Download
1Errors
660,831Warnings
740Info
Top Issues
block trips with overlapping stop times1
non ascii or non printable char659,548
unexpected enum value989
GeoJSON GeoJSON Data
2.16 MB
Download

Original Source

Obtained 2026-07-02

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

ZIP GTFS Source Data
200.63 MB
Download
License: CC_BY_4.0 Content Hash: 639a0ee880469774dc75920344090a8b7e517f3f
ZIP Validation Report
0.3 MB
Download
303Errors
1,238,688Warnings
1,070Info
Top Issues
decreasing or equal stop time distance265
equal shape distance diff coordinates35
invalid character3

Overlapping Feeds

Feeds that share stops or routes with this dataset.

Feed Stops Overlap Routes Overlap
trains-fin 169 (0.29%) 189 (5.66%)
invataksi-niemi-oy 143 (0.24%) 47 (1.41%)
oulun-joukkoliikenteen 1429 (2.42%) 43 (1.29%)
helsingin-seudun-liikenne-hsl 40 (1.2%)
yvaskyla 1227 (2.07%) 36 (1.08%)
digital-ocean2 681 (1.15%) 30 (0.9%)
kymen-charterline-oy 604 (1.02%) 27 (0.81%)
hameenlinna 5 (0.01%) 26 (0.78%)
fintraffic-kela-suuret2 1250 (2.11%) 20 (0.6%)
liikennevirasto 603 (1.02%) 17 (0.51%)
flix-bus-eu 3 (0.09%)
city-of-kajaani 247 (0.42%) 1 (0.03%)
Integroi reaaliaikaiset lähdöt sovellukseesi Ilmainen API-käyttöoikeus →

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 defines a common format for transit agencies to publish their data, enabling developers to build interoperable transit applications, trip planners, and mobility analytics tools.

What is the difference between enhanced and source data?

Source data is the original GTFS feed obtained directly from the transit agency or official provider. The enhanced version has been processed by our team to fix common errors, remove inconsistencies, and ensure compliance with GTFS specifications. We recommend using 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 above. Many GTFS feeds are published under open data licenses that allow free use with attribution. Always verify the license terms before integrating data into your project.

How do I validate a GTFS feed?

Each feed includes a validation report that documents errors and warnings. You can also use tools like the MobilityData GTFS Validator to independently validate the data. Our enhanced feeds have already been processed to resolve the most critical validation issues.

All data on this site is sourced from publicly available sources. If you believe a file has been posted in error, an incorrect license has been attributed, or attribution to the original source is missing or incorrect, please contact us and we will correct it.