Collision: Amersfoort-Deventer; Amsterdam-Hannover-Berlin (12 July 2017)
-
Disruption resolved Last update
Between Amersfoort and Apeldoorn the train traffic is fully resumed.
-
Delays decreasing
Between Amersfoort and Apeldoorn the restrictions are resolved.
Delays are decreasing.
Service is normal around 12:15 AM hours. -
Update
Between Amersfoort and Apeldoorn no trains are running due to a collision.
This will take until approximately 12:30 AM on Thursday, July 13, 2017.Train measures
- Intercity 140-149 Amsterdam C. - Hengelo - Hannover Hbf - Berlin Ostbhf is diverted between Amsterdam Centraal and Deventer
- Intercity 240 Amsterdam C. - Hengelo - Hannover Hbf - Berlin Ostbhf is diverted between Amsterdam Centraal and Deventer
- Intercity 1500 Amsterdam C. - Amersfoort is cancelled between Amersfoort and Deventer
- Intercity 1600 Schiphol Airport - Amersfoort - Hengelo - Enschede is cancelled between Apeldoorn and Amersfoort
- Intercity 1700 Den Haag C. - Amersfoort - Hengelo - Enschede is cancelled between Apeldoorn and Amersfoort
-
Update
Between Amersfoort and Apeldoorn no trains are running due to a collision.
It is not known yet how long this will take.Train measures
- Intercity 140-149 Amsterdam C. - Hengelo - Hannover Hbf - Berlin Ostbhf is diverted between Amsterdam Centraal and Deventer
- Intercity 240 Amsterdam C. - Hengelo - Hannover Hbf - Berlin Ostbhf is diverted between Amsterdam Centraal and Deventer
- Intercity 1500 Amsterdam C. - Amersfoort is cancelled between Amersfoort and Deventer
- Intercity 1600 Schiphol Airport - Amersfoort - Hengelo - Enschede is cancelled between Apeldoorn and Amersfoort
- Intercity 1700 Den Haag C. - Amersfoort - Hengelo - Enschede is cancelled between Apeldoorn and Amersfoort
-
Update
Between Amersfoort and Apeldoorn no trains are running due to a collision.
It is not known yet how long this will take. -
Disruption
Between Amersfoort and Apeldoorn 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 11:29 PM on July 12, 2017 and took 48 minutes in total.
For statistics, this disruption is caused due to a collision.
Operators
This disruption affects trains operated by NS and NS International.
Got delayed due to this disruption? You may be reimbursed.