Disruption Leiden-Schiphol-Zaandam

Defective railway track
This disruption is resolved.

Current travel advice

Between Leiden Centraal and Hoofddorp the train traffic is fully resumed.

Mar 23, 2017 9:00 PM

Earlier messages

Between Leiden Centraal and Hoofddorp the restrictions are resolved.
Delays are diminishing.
Service is normal around 9:00 PM hours.

Mar 23, 2017 8:25 PM

Between Leiden Centraal and Hoofddorp fewer Sprinter trains are running due to a defective railway track.
The extra travel time is about 15 minutes.
Service is normal around 9:00 PM hours.

Train measures

  • Sprinter 3300 Kersenboogerd - Zaandam - Schiphol Airport - Leiden C. is cancelled between Leiden Centraal and Hoofddorp
Mar 23, 2017 5:08 PM

Between Leiden Centraal and Hoofddorp fewer Sprinter trains are running due to a defective railway track.
The extra travel time is about 15 minutes.
Service is normal around 9:00 PM hours.

Train measures

  • Sprinter 3300 Kersenboogerd - Zaandam - Schiphol Airport - Leiden C. is cancelled between Leiden Centraal and Hoofddorp
  • Intercity 9200 Amsterdam CS - Rotterdam C. - Antwerpen-C. - Brussel Z./Midi is diverted and will not call at Schiphol Airport between Amsterdam Centraal and Leiden Centraal (only in direction of Leiden Centraal)
Mar 23, 2017 5:29 AM

Between Leiden Centraal and Hoofddorp fewer Sprinter trains are running due to a defective railway track.
The extra travel time is about 15 minutes.
Service is normal around 9:15 PM hours.

Train measures

  • Sprinter 3300 Kersenboogerd - Zaandam - Schiphol Airport - Leiden C. is cancelled between Leiden Centraal and Hoofddorp
  • Intercity 9200 Amsterdam CS - Rotterdam C. - Antwerpen-C. - Brussel Z./Midi is diverted and will not call at Schiphol Airport between Amsterdam Centraal and Leiden Centraal (only in direction of Leiden Centraal)
Mar 23, 2017 5:13 AM

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by NS.

Information

This disruption started at 5:13 AM on March 23, 2017 and took 15 hours, 46 minutes in total.

For statistics, this disruption is caused due to a defective railway track.