Signal failure: Haarlem-Hoorn (18 June 2017)
-
Disruption resolved Last update
Between Heerhugowaard and Hoorn the train traffic is fully resumed.
Advice
Local buses are still running between Heerhugowaard, Obdam and Hoorn.
-
Delays decreasing
Between Heerhugowaard and Hoorn the restrictions are resolved.
Delays are decreasing.
Service is normal around 10:00 PM hours.Advice
Local buses are still running between Heerhugowaard, Obdam and Hoorn.
-
Update
Between Heerhugowaard and Hoorn no trains are running due to a signal failure.
This will take until approximately 10:00 PM hours.Advice
Local buses are running between Heerhugowaard, Obdam and Hoorn.
Passengers between Alkmaar and Hoorn travel via Zaandam. The extra travel time is up to 60 minutes.Train measures
- Sprinter 4800 Amsterdam C. - Haarlem - Hoorn is cancelled between Heerhugowaard and Hoorn
-
Update
Between Heerhugowaard and Hoorn no trains are running due to a signal failure.
It is not known yet how long this will take.Advice
Local buses are running between Heerhugowaard, Obdam and Hoorn.
Passengers between Alkmaar and Hoorn travel via Zaandam. The extra travel time is up to 60 minutes.Train measures
- Sprinter 4800 Amsterdam C. - Haarlem - Hoorn is cancelled between Heerhugowaard and Hoorn
-
Update
Between Heerhugowaard and Hoorn no trains are running due to a signal failure.
It is not known yet how long this will take.Advice
Passengers between Alkmaar and Hoorn travel via Zaandam. The extra travel time is up to 60 minutes.
Train measures
- Sprinter 4800 Amsterdam C. - Haarlem - Hoorn is cancelled between Heerhugowaard and Hoorn
-
Update
Between Heerhugowaard and Hoorn no trains are running due to a signal failure.
It is not known yet how long this will take.Advice
Passengers between Alkmaar and Hoorn travel via Zaandam. The extra travel time is up to 60 minutes.
-
Disruption
Between Heerhugowaard and Hoorn no trains are running due to a signal failure.
It is not known yet how long this will take.
More about this disruption
Statistics
This disruption started at 7:45 PM on June 18, 2017 and took 2 hours, 14 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.