Papers › Unveiling connectivity patterns of railway timetables through complex network theory...
Unveiling connectivity patterns of railway timetables through complex network theory and Infomap clustering
Fabio Lamanna, Michele Prisma, Giorgio Medeossi
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
This paper presents a novel approach to analysing railway timetable connectivity using complex network theory and the Infomap clustering algorithm. By transforming railway timetables into network representations, we examine the connectivity and efficiency of the Norwegian railway system for the timetables of the current 2024 year and for a future timetable of year 2033. We define and apply the Timetable Connectivity Index, a comprehensive measure that evaluates the overall connectivity based on the number of services, travel times, and the hierarchical structure of the network. The analysis is conducted across three distinct network spaces: Stops, Stations, and Changes, with both unweighted and weighted networks. Our results reveal key insights into how infrastructural developments, service frequencies, and travel time adjustments influence network connectivity. The findings provide valuable insights for railway planners and operators, aiming to improve the efficiency and reliability of train networks.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections