seinstoring

Signal failure: Utrecht-Leiden (1 June 2017)

  1. Disruption resolved Last update

    Between Alphen a/d Rijn and Bodegraven the train traffic is fully resumed.

  2. Delays decreasing

    Between Alphen a/d Rijn and Bodegraven the restrictions are resolved.
    Delays are decreasing.
    Service is normal around 3:15 PM hours.

  3. Update

    Between Alphen a/d Rijn and Bodegraven no trains are running due to a signal failure.
    This will take until at least 4:00 PM hours.

    Advice

    Buses are running between Alphen a/d Rijn and Bodegraven.

    Train measures

    • Intercity 8800 Leiden C. - Utrecht C. is cancelled between Alphen a/d Rijn and Bodegraven
  4. Update

    Between Alphen a/d Rijn and Bodegraven no trains are running due to a signal failure.
    This will take until at least 3:00 PM hours.

    Advice

    Buses are running between Alphen a/d Rijn and Bodegraven.

    Train measures

    • Intercity 8800 Leiden C. - Utrecht C. is cancelled between Alphen a/d Rijn and Bodegraven
  5. Update

    Between Alphen a/d Rijn and Bodegraven no trains are running due to a signal failure.
    This will take until at least 2:00 PM hours.

    Advice

    Buses are running between Alphen a/d Rijn and Bodegraven.

    Train measures

    • Intercity 8800 Leiden C. - Utrecht C. is cancelled between Alphen a/d Rijn and Bodegraven
  6. Update

    Between Alphen a/d Rijn and Bodegraven no trains are running due to a signal failure.
    This will take until at least 2:00 PM hours.

    Train measures

    • Intercity 8800 Leiden C. - Utrecht C. is cancelled between Alphen a/d Rijn and Bodegraven
  7. Update

    Between Alphen a/d Rijn and Bodegraven no trains are running due to a signal failure.
    This will take until at least 2:00 PM hours.

  8. Disruption

    Between Alphen a/d Rijn and Bodegraven no trains are running due to a signal failure.
    It is not known yet how long this will take.

  9. Update

    Between Alphen a/d Rijn and Bodegraven there is a service disruption due to a signal failure.
    Updates will follow as more information becomes available.

More about this disruption

Statistics

This disruption started at 11:08 AM on June 1, 2017 and took 4 hours, 6 minutes in total.

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

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