Stranded train: Weesp (26 September 2017)
-
Disruption resolved Last update
From and to Weesp the train traffic is fully resumed.
-
Delays decreasing
From and to Weesp the restrictions are resolved.
Delays are decreasing.
Service is normal around 4:00 PM hours. -
Update
From and to Weesp far fewer trains are running due to a stranded train.
It is not known yet how long this will take.Train measures
- Intercity 700 Den Haag C. - Schiphol Airport - Lelystad C. - Groningen is cancelled between Almere Centrum and Amsterdam Zuid
- Intercity 1800 Den Haag C. - Schiphol Airport - Lelystad C. - Leeuwarden is cancelled between Almere Centrum and Amsterdam Zuid
- Intercity 2400 Lelystad C. - Schiphol Airport - Rotterdam C. - Dordrecht is cancelled between Almere Centrum and Leiden Centraal
- Intercity 2600 Amsterdam C. - Almere C. is cancelled between Almere Centrum and Amsterdam Centraal
- Sprinter 4300 Oostvaarders - Schiphol Airport - Hoofddorp is cancelled between Almere Oostvaarders and Hoofddorp
-
Update
Between Weesp and Almere Centrum far fewer trains are running due to a stranded train.
It is not known yet how long this will take.Train measures
- Intercity 700 Den Haag C. - Schiphol Airport - Lelystad C. - Groningen is cancelled between Almere Centrum and Amsterdam Zuid
- Intercity 1800 Den Haag C. - Schiphol Airport - Lelystad C. - Leeuwarden is cancelled between Almere Centrum and Amsterdam Zuid
- Intercity 2400 Lelystad C. - Schiphol Airport - Rotterdam C. - Dordrecht is cancelled between Almere Centrum and Leiden Centraal
- Intercity 2600 Amsterdam C. - Almere C. is cancelled between Almere Centrum and Amsterdam Centraal
- Sprinter 4300 Oostvaarders - Schiphol Airport - Hoofddorp is cancelled between Almere Oostvaarders and Hoofddorp
-
Update
Between Weesp and Almere Centrum far fewer trains are running due to a stranded train.
It is not known yet how long this will take. -
Disruption
Between Almere Poort and Almere Centrum there is a service disruption due to a stranded train.
Updates will follow as more information becomes available.
More about this disruption
Statistics
This disruption started at 1:12 PM on September 26, 2017 and took 2 hours, 46 minutes in total.
For statistics, this disruption is caused due to a stranded train.
Affected lines
The following lines are affected by this disruption:
Operators
This disruption affects trains operated by NS and NS International.
Got delayed due to this disruption? You may be reimbursed.