great-britain — GTFS Transit Data for United Kingdom
ActiveAbout This Feed
The great-britain GTFS feed by Datafeeds provides structured public transit data for United Kingdom, covering 17801 routes and 325099 stops operated by 810 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 11, 2002 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 →
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-10Cleaned, corrected, and validated against GTFS specifications. View corrections.
Original Source
Obtained 2026-07-10Unmodified GTFS data from official sources. May contain errors or inconsistencies.
Overlapping Feeds
Feeds that share stops or routes with this dataset.
| Feed | Stops Overlap | Routes Overlap |
|---|---|---|
| dft-gtfs | 187695 (58.2%) | 12231 (68.71%) |
| discoverpassenger-intalink | 13 (0%) | 287 (1.61%) |
| discoverpassenger-gonortheast | 2213 (0.69%) | 223 (1.25%) |
| gtfs-7 | 3113 (0.97%) | 123 (0.69%) |
| discoverpassenger-morebus | 2151 (0.67%) | 112 (0.63%) |
| discoverpassenger-eyms | 2429 (0.75%) | 90 (0.51%) |
| flix-bus-eu | 43 (0.01%) | 85 (0.48%) |
| discoverpassenger-newportbus | 1177 (0.36%) | 76 (0.43%) |
| discoverpassenger-swindonbus | 1596 (0.49%) | 69 (0.39%) |
| discoverpassenger-metrobus | 72 (0.02%) | 68 (0.38%) |
| discoverpassenger-carouselbuses | 259 (0.08%) | 64 (0.36%) |
| discoverpassenger-bluestar | 1324 (0.41%) | 61 (0.34%) |
| discoverpassenger-westcoastmotors | 1561 (0.48%) | 51 (0.29%) |
| discoverpassenger-konectbus | 3 (0%) | 45 (0.25%) |
| discoverpassenger-courtney | 905 (0.28%) | 34 (0.19%) |
| discoverpassenger-bordersbuses | 446 (0.14%) | 23 (0.13%) |
| discoverpassenger-godevonbus | 555 (0.17%) | 16 (0.09%) |
| tflgtfs-nobus | 3 (0%) | 12 (0.07%) |
| blablacar | — | 5 (0.03%) |
| flixbus-eu | — | 5 (0.03%) |
| idbus | — | 5 (0.03%) |
| delfi | 18 (0.01%) | 3 (0.02%) |
| ulmer-eisenbahnfreunde | 16 (0%) | 3 (0.02%) |
| colectivos | — | 1 (0.01%) |
| deutschen-all | 25 (0.01%) | — |
| sverige-3 | 7 (0%) | — |
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.