Signal failure: Amersfoort-Amersfoort Vathorst (22 July 2019)
-
Disruption resolved Last update
Between Amersfoort and Amersfoort Vathorst the train traffic is fully resumed.
Train measures
- Sprinter 15800 Amsterdam C. - Vathorst is cancelled between Amersfoort Vathorst and Baarn
-
Update
Between Amersfoort and Amersfoort Vathorst fewer Sprinter trains are running due to a signal failure.
The extra travel time may be up to 15 minutes.
This will take until approximately 6:45 PM hours.Train measures
- Sprinter 15800 Amsterdam C. - Vathorst is cancelled between Amersfoort Vathorst and Baarn
-
Update
Between Amersfoort and Amersfoort Vathorst fewer Sprinter trains are running due to a signal failure.
The extra travel time may be up to 15 minutes.
This will take until approximately 6:15 PM hours.Train measures
- Sprinter 15800 Amsterdam C. - Vathorst is cancelled between Amersfoort Vathorst and Baarn
-
Update
Between Amersfoort and Amersfoort Vathorst fewer Sprinter trains are running due to a signal failure.
The extra travel time may be up to 15 minutes.
This will take until approximately 7:30 PM hours.Train measures
- Sprinter 15800 Amsterdam C. - Vathorst is cancelled between Amersfoort Vathorst and Baarn
-
Disruption
Between Amersfoort and Amersfoort Vathorst fewer Sprinter trains are running due to a signal failure.
The extra travel time may be up to 15 minutes.
This will take until approximately 7:30 PM hours.Train measures
- Intercity 140-149 Amsterdam C. - Hengelo - Hannover Hbf - Berlin Ostbhf is cancelled between Amsterdam Centraal and Amersfoort
- Intercity 1500 Amsterdam C. - Amersfoort is cancelled between Deventer and Hilversum
- Intercity 1600 Schiphol Airport - Amersfoort - Hengelo - Enschede is cancelled between Amersfoort and Hilversum
- Intercity 11600 Schiphol Airport - Amersfoort - Schothorst is cancelled between Amersfoort and Hilversum
- Sprinter 15800 Amsterdam C. - Vathorst is cancelled between Amersfoort Vathorst and Baarn
More about this disruption
Statistics
This disruption started at 5:18 PM on July 22, 2019 and took 1 hour, 16 minutes in total.
For statistics, this disruption is caused due to a signal failure.
Operators
This disruption affects trains operated by NS.
Got delayed due to this disruption? You may be reimbursed.