norsk - GTFS transit data for Norway

Active
Entur Norway December 14, 2025 — July 31, 2027

About This Feed

The norsk GTFS feed by Entur provides structured public transit data for Norway, covering 3,894 routes, 90,053 stops, and 58 transit agencies. Formatted according to the General Transit Feed Specification (GTFS), this dataset is ready for transit apps, routing engines, urban planning tools, and AI agents / LLM applications.

Valid from December 14, 2025 to July 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 norsk routes and stops in Norway
Explore 3,894 routes, 90,053 stops, and 58 agencies

Browse routes, stops, and agencies from this feed. Public pages show merged data from all feeds. Sign in for per-feed details useful for GTFS integration and debugging.

Sign in to access →

Download this feed through the BusMaps API

Enhanced GTFS, source GTFS, GeoJSON, and validation reports are available through the API.

Use ?feedName=norsk to request this feed. View API documentation.

Enhanced & Validated Recommended

Updated 2026-08-01

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

ZIP GTFS Feed - Corrected & Enriched
203.89 MB
Available through API only This work is licensed under Busmaps_licence_v1. Content Hash: cc671af22f6aa0ba
ZIP Validation Report
0.03 MB
Available through API only
0Errors
3,660Warnings
185Info
Top Issues
unexpected enum value3,571
mixed case recommended field61
expired calendar17
GeoJSON GeoJSON Data
4.44 MB
Available through API only

Original Source

Obtained 2026-07-31

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

ZIP GTFS Source Data
586.07 MB
Available through API only License: NLOD Content Hash: 72bc5a7640c78fae
ZIP Validation Report
0.2 MB
Available through API only
66Errors
61,312Warnings
242Info
Top Issues
decreasing or equal stop time distance46
transfer with invalid trip and stop12
duplicate key8

Use This Feed from AI Agents

This feed is also served through the BusMaps MCP server: point Claude, ChatGPT, Gemini or any MCP client at https://mcp.busmaps.com/mcp and your agent can plan routes, read departures, and query this network in plain language.

About the MCP server →

Overlapping Feeds

Feeds that share stops or routes with this dataset.

Feed Stops Overlap Routes Overlap
rkt-no-kolumbus-1 1240 (1.38%) 81 (2.08%)
sverige-3 9 (0.01%) 18 (0.46%)
sverige-sw 14 (0.36%)
flix-bus-eu 10 (0.26%)
rb-avi-aggregated-gtfs 13 (0.01%) 9 (0.23%)
deutschen-all 2 (0.05%)
rejseplanen-dk 2 (0.05%)
ulmer-eisenbahnfreunde 2 (0.05%)
delfi 1 (0.03%)
flixbus-eu 1 (0.03%)
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 enables transit agencies to publish interoperable data for applications, trip planners, and mobility analytics tools.

What is the difference between enhanced and source data?

Source data is the original GTFS feed obtained from the transit agency or official provider. The enhanced version has been processed to fix errors, remove inconsistencies, and ensure compliance with GTFS specifications. We recommend 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. Many GTFS feeds use open data licenses that allow free use with attribution. Always verify the license terms before integration.

How do I validate a GTFS feed?

Each feed includes a validation report documenting errors and warnings. You can also use the MobilityData GTFS Validator for independent validation. Enhanced feeds have already been processed to resolve the most critical validation issues.

All data on this site comes from publicly available sources. If a file was posted in error, has an incorrect license, or lacks correct source attribution, please contact us and we will correct it.