Collision: Zaandam-Enkhuizen (9 January 2020)
-
Disruption resolved Last update
Between Hoorn and Hoorn Kersenboogerd the train traffic is fully resumed.
Advice
Buses are still running between Hoorn and Hoorn Kersenboogerd.
-
Delays decreasing
Between Hoorn and Hoorn Kersenboogerd the restrictions are resolved.
Delays are decreasing.
Service is normal around 11:45 PM hours.Advice
Buses are still running between Hoorn and Hoorn Kersenboogerd.
-
Update
Between Hoorn and Hoorn Kersenboogerd no trains are running due to a collision.
The extra travel time may be up to 30 minutes.
This will take until approximately 11:45 PM hours.Advice
Buses are running between Hoorn and Hoorn Kersenboogerd.
Train measures
- Intercity 2900 Enkhuizen - Utrecht C. - Eindhoven C. - Maastricht is cancelled between Hoorn and Hoorn Kersenboogerd
- Sprinter 3300 Kersenboogerd - Zaandam - Schiphol Airport - Leiden C. is cancelled between Hoorn and Hoorn Kersenboogerd
-
Update
Between Hoorn and Hoorn Kersenboogerd no trains are running due to a collision.
The extra travel time is more than 60 minutes.
This will take until approximately 11:45 PM hours.Advice
Buses are running between Hoorn and Hoorn Kersenboogerd.
Train measures
- Intercity 2900 Enkhuizen - Utrecht C. - Eindhoven C. - Maastricht is cancelled between Hoorn and Hoorn Kersenboogerd
- Sprinter 3300 Kersenboogerd - Zaandam - Schiphol Airport - Leiden C. is cancelled between Hoorn and Hoorn Kersenboogerd
-
Update
Between Hoorn and Hoorn Kersenboogerd no trains are running due to a collision.
The extra travel time is more than 60 minutes.
This will take until approximately 11:45 PM hours.Train measures
- Intercity 2900 Enkhuizen - Utrecht C. - Eindhoven C. - Maastricht is cancelled between Hoorn and Hoorn Kersenboogerd
- Sprinter 3300 Kersenboogerd - Zaandam - Schiphol Airport - Leiden C. is cancelled between Hoorn and Hoorn Kersenboogerd
-
Disruption
Between Hoorn and Hoorn Kersenboogerd no trains are running due to a collision.
This will take until approximately 11:45 PM hours.
More about this disruption
Statistics
This disruption started at 8:38 PM on January 9, 2020 and took 3 hours, 11 minutes in total.
For statistics, this disruption is caused due to a collision.
Operators
This disruption affects trains operated by NS.
Got delayed due to this disruption? You may be reimbursed.