Disruption Amsterdam-Enkhuizen

Level crossing failure
This disruption is resolved.

Current travel advice

Between Purmerend Overwhere and Hoorn the train traffic is fully resumed.

Mar 23, 2017 1:21 AM

Earlier messages

Between Purmerend Overwhere and Hoorn there are no trains running due to a level crossing failure.
The extra travel time is more than 60 minutes.
This will take the rest of the day.

Advice

Local buses are running between Purmerend Overwhere and Hoorn.

Train measures

  • Sprinter 3300 Kersenboogerd - Zaandam - Schiphol Airport - Leiden C. is cancelled between Purmerend Overwhere and Hoorn Kersenboogerd
  • Intercity 4500 Enkhuizen - Zaandam - Amsterdam CS is cancelled between Amsterdam Centraal and Hoorn
  • Intercity 14500 Amsterdam CS - Enkhuizen is cancelled between Amsterdam Centraal and Enkhuizen
Mar 23, 2017 12:20 AM

Between Purmerend Overwhere and Hoorn there are no trains running due to a level crossing failure.
The extra travel time is more than 60 minutes.
It is not known yet how long this will take.

Train measures

  • Sprinter 3300 Kersenboogerd - Zaandam - Schiphol Airport - Leiden C. is cancelled between Purmerend Overwhere and Hoorn Kersenboogerd
  • Intercity 4500 Enkhuizen - Zaandam - Amsterdam CS is cancelled between Amsterdam Centraal and Hoorn
  • Intercity 14500 Amsterdam CS - Enkhuizen is cancelled between Amsterdam Centraal and Enkhuizen
Mar 22, 2017 11:27 PM

Between Purmerend Overwhere and Hoorn there are no trains running due to a level crossing failure.
The extra travel time is more than 60 minutes.
It is not known yet how long this will take.

Mar 22, 2017 11:09 PM

Between Zaandam and Hoorn there are delays and fewer trains are running due to a level crossing failure.
The extra travel time may be up to 30 minutes.
It is not known yet how long this will take.

Mar 22, 2017 10:55 PM

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by NS.

Information

This disruption started at 10:55 PM on March 22, 2017 and took 2 hours, 26 minutes in total.

For statistics, this disruption is caused due to a level crossing failure.