vrn — GTFS Transit Data for Germany

Active
Rhein-Neckar-Verkehr Germany April 26, 2026 — December 13, 2026

About This Feed

The vrn GTFS feed by Rhein-Neckar-Verkehr provides structured public transit data for Germany, covering 1152 routes and 18020 stops operated by 52 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 April 26, 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 vrn routes and stops in Germany
Explore 1,152 routes, 18,020 stops, 52 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-05-09

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

ZIP GTFS Feed — Corrected & Enriched
60.98 MB
Download GTFS
The license for this work is not specified Content Hash: f25d51196906e9598c6017261c7ab889595f8c0b
ZIP Validation Report
0.04 MB
Download
0Errors
1,083Warnings
30Info
Top Issues
non ascii or non printable char736
fast travel between far stops168
stop too far from shape136
GeoJSON GeoJSON Data
0.59 MB
Download

Original Source

Obtained 2026-05-07

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

ZIP GTFS Source Data
189.7 MB
Download
Source: Official download The license for this work is not specified Content Hash: b567df596bd3ded8327598dfd7ae3310ee0b8ca5
ZIP Validation Report
0.28 MB
Download
13,035Errors
293,957Warnings
40Info
Top Issues
decreasing or equal stop time distance13,032
point near origin3
equal shape distance same coordinates286,876

Overlapping Feeds

Feeds that share stops or routes with this dataset.

Feed Stops Overlap Routes Overlap
delfi 13982 (77.6%) 1080 (93.75%)
ulmer-eisenbahnfreunde 13455 (74.68%) 1063 (92.27%)
deutschen-all 12732 (70.66%) 898 (77.95%)
bwgesamt 5314 (29.49%) 346 (30.03%)
rnv 85 (7.38%)
rhein-neckar-verkehrgmbhrnv 2 (0.01%) 59 (5.12%)
geops-chl 2 (0.17%)
horaires-des-lignes-ter-sncf 2 (0.17%)
odp-swiss 2 (0.17%)
region-grandest-gtfs 2 (0.17%)
ter-sncf 2 (0.17%)
bwspnv 1 (0.09%)
nrw 11 (0.06%)
nvbw-rbs 6 (0.03%)
kvv 3 (0.02%)
verkehrsverbund 3 (0.02%)
Build real-time departures into your app Free API Access →

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 or an incorrect license has been attributed, please contact us.