gtfs-nl — GTFS Transit Data for Netherlands

Active
Ovapi Netherlands July 1, 2026 — December 13, 2026

About This Feed

The gtfs-nl GTFS feed by Ovapi provides structured public transit data for Netherlands, covering 2846 routes and 51468 stops operated by 40 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, 2026 to December 13, 2026. 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 gtfs-nl routes and stops in Netherlands
Explore 2,846 routes, 51,468 stops, 40 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
77.07 MB
Download GTFS
This work is licensed under a Busmaps_licence_v1. Content Hash: 5724833bd73ed51dbe5f59e432cf9bbbc4e35c3e
ZIP Validation Report
0.04 MB
Download
0Errors
602Warnings
357Info
Top Issues
mixed case recommended field221
stop too far from shape175
route short name too long158
GeoJSON GeoJSON Data
2.18 MB
Download

Original Source

Obtained 2026-07-02

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

ZIP GTFS Source Data
234.07 MB
Download
License: CC0_1.0 Content Hash: 568e2dc0b4ae2b84a82633e20d607e179a3a714f
ZIP Validation Report
0.19 MB
Download
17,878Errors
15,639Warnings
1,650Info
Top Issues
decreasing or equal stop time distance17,794
point near origin84
fast travel between consecutive stops8,269

Overlapping Feeds

Feeds that share stops or routes with this dataset.

Feed Stops Overlap Routes Overlap
de-lijn 1569 (3.08%) 295 (10.37%)
nrw 129 (4.53%)
avv 3 (0.01%) 108 (3.79%)
ulmer-eisenbahnfreunde 9 (0.02%) 10 (0.35%)
delfi 9 (0.02%) 9 (0.32%)
deutschen-all 9 (0.02%) 8 (0.28%)
bel-rail 7 (0.25%)
toplevel-dhid-siflecehpr 4 (0.14%)
nordrhein-westfalen-2 8 (0.02%) 3 (0.11%)
eurostar-railways 2 (0.07%)
bwspnv 1 (0.04%)
deutsche-bahn 1 (0.04%)
flix-bus-eu 1 (0.04%)
thalys 1 (0.04%)
Echtzeit-Abfahrten in Ihre App integrieren Kostenloser API-Zugang →

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.