een verstoring elders

Disruption elsewhere: Amsterdam Sloterdijk-Hoorn (4 July 2017)

  1. Disruption resolved Last update

    Between Amsterdam Sloterdijk and Hoorn the train traffic is fully resumed.

    Train measures

    • Sprinter 3300 Kersenboogerd - Zaandam - Schiphol Airport - Leiden C. is cancelled between Leiden Centraal and Hoorn Kersenboogerd
    • Intercity 4500 Enkhuizen - Zaandam - Amsterdam C. calls at all intermediate stations between Amsterdam Centraal and Hoorn
  2. Delays decreasing

    Between Amsterdam Sloterdijk and Hoorn the restrictions are resolved.
    Delays are diminishing.
    This will take until approximately 9:00 PM hours.

    Train measures

    • Sprinter 3300 Kersenboogerd - Zaandam - Schiphol Airport - Leiden C. is cancelled between Leiden Centraal and Hoorn Kersenboogerd
    • Intercity 4500 Enkhuizen - Zaandam - Amsterdam C. calls at all intermediate stations between Amsterdam Centraal and Hoorn
  3. Update

    Between Amsterdam Sloterdijk and Hoorn there are fewer trains running due to a disruption elsewhere.
    The extra travel time may be up to 30 minutes.
    This will take until approximately 9:00 PM hours.

    Train measures

    • Sprinter 3300 Kersenboogerd - Zaandam - Schiphol Airport - Leiden C. is cancelled between Leiden Centraal and Hoorn Kersenboogerd
    • Intercity 4500 Enkhuizen - Zaandam - Amsterdam C. calls at all intermediate stations between Amsterdam Centraal and Hoorn
  4. Update

    Between Amsterdam Sloterdijk and Hoorn there are fewer trains running due to a disruption elsewhere.
    The extra travel time may be up to 30 minutes.
    This will take until approximately 7:00 PM hours.

    Train measures

    • Sprinter 3300 Kersenboogerd - Zaandam - Schiphol Airport - Leiden C. is cancelled between Leiden Centraal and Hoorn Kersenboogerd
    • Intercity 4500 Enkhuizen - Zaandam - Amsterdam C. calls at all intermediate stations between Amsterdam Centraal and Hoorn
  5. Disruption

    Between Amsterdam Sloterdijk and Hoorn there are fewer trains running due to a disruption elsewhere.
    The extra travel time may be up to 30 minutes.
    This will take until approximately 7:00 PM hours.

More about this disruption

Statistics

This disruption started at 4:56 PM on July 4, 2017 and took 4 hours, 3 minutes in total.

For statistics, this disruption is caused due to a disruption elsewhere.

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by NS.

Got delayed due to this disruption? You may be reimbursed.

Refunds and passenger rights