Railway data - Traffic Centre Area

Open data API in a single place

Provided by Lantmäteriet

Get early access to Railway data - Traffic Centre Area API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2024.11.12 00:00
Created
2013.04.08
Available languages
English
Keywords
trafikslag: järnväg, område: transport
Quality scoring

Dataset description

Sweden is divided into five geographical operating areas responsible for delivering train paths. Within these areas there are eight traffic center areas, from Boden in the north and to Malmö in the south. In each traffic centre area there is a control centre from which traffic is routed within the area. The main tasks of the Traffic Management Centres are to monitor and manage traffic in their traffic centre area. They are also responsible for traffic information. In a traffic centre area there are traffic points that can be controlled remotely from the control centre, but the area also includes equipment that can be monitored locally. The data product contains information on the geographical areas of responsibility for the Swedish Transport Administration's eight traffic centre areas and for Inlandsbanan. The data product has stretch distribution and connects to the network with reference from node to node in the direction of the track link. The data product is comprehensive on the Swedish railway network
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks