Disruption Alkmaar-Hoorn

Signal and level crossing failure
This disruption is resolved.

Current travel advice

Between Heerhugowaard and Hoorn the train traffic is fully resumed.

Advice

Local buses are still running between Heerhugowaard, Obdam and Hoorn.

Sep 24, 2017 6:43 PM

Earlier messages

Between Heerhugowaard and Hoorn the restrictions are resolved.
Delays are diminishing.
Service is normal around 6:45 PM hours.

Advice

Local buses are still running between Heerhugowaard, Obdam and Hoorn.

Sep 24, 2017 6:15 PM

Between Heerhugowaard and Hoorn there are no trains running due to a signal and level crossing failure.
Service is normal around 6:45 PM hours.

Advice

Local buses are running between Heerhugowaard, Obdam and Hoorn.

Train measures

  • Sprinter 4800 Amsterdam C. - Haarlem - Hoorn is cancelled between Heerhugowaard and Hoorn
Sep 24, 2017 6:00 PM

Between Heerhugowaard and Hoorn there are no trains running due to a signal and level crossing failure.
Service is normal around 6:45 PM hours.

Train measures

  • Sprinter 4800 Amsterdam C. - Haarlem - Hoorn is cancelled between Heerhugowaard and Hoorn
Sep 24, 2017 5:49 PM

Between Heerhugowaard and Hoorn there are no trains running due to a signal and level crossing failure.
This will take until approximately 7:30 PM hours.

Train measures

  • Sprinter 4800 Amsterdam C. - Haarlem - Hoorn is cancelled between Heerhugowaard and Hoorn
Sep 24, 2017 5:08 PM

Between Heerhugowaard and Hoorn there are no trains running due to a signal and level crossing failure.
It is not known yet how long this will take.

Train measures

  • Sprinter 4800 Amsterdam C. - Haarlem - Hoorn is cancelled between Heerhugowaard and Hoorn
Sep 24, 2017 5:00 PM

Between Heerhugowaard and Hoorn there are no trains running due to a signal and level crossing failure.
It is not known yet how long this will take.

Sep 24, 2017 4:45 PM

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by NS.

Information

This disruption started at 4:45 PM on September 24, 2017 and took 1 hour, 58 minutes in total.

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