persoon op het spoor

Person on the railway track: Utrecht-Rotterdam (31 July 2019)

  1. Disruption resolved Last update

    Between Utrecht Centraal and Rotterdam Centraal the train traffic is fully resumed.

    Train measures

    • Intercity 500 Rotterdam C. - Utrecht C. - Zwolle - Groningen is cancelled between Rotterdam Centraal and Utrecht Centraal
    • Intercity 600 Rotterdam C. - Utrecht C. - Zwolle - Leeuwarden is cancelled between Rotterdam Centraal and Utrecht Centraal
    • Intercity 2800 Rotterdam C. - Utrecht C. is cancelled between Rotterdam Centraal and Utrecht Centraal
    • Sprinter 7700 Rotterdam C. - Goverwelle is cancelled between Rotterdam Centraal and Gouda Goverwelle
  2. Update

    Between Utrecht Centraal and Rotterdam Centraal far fewer trains are running due to a person on the railway track.
    It is not known yet how long this will take.

    Train measures

    • Intercity 500 Rotterdam C. - Utrecht C. - Zwolle - Groningen is cancelled between Rotterdam Centraal and Utrecht Centraal
    • Intercity 600 Rotterdam C. - Utrecht C. - Zwolle - Leeuwarden is cancelled between Rotterdam Centraal and Utrecht Centraal
    • Intercity 2800 Rotterdam C. - Utrecht C. is cancelled between Rotterdam Centraal and Utrecht Centraal
    • Sprinter 7700 Rotterdam C. - Goverwelle is cancelled between Rotterdam Centraal and Gouda Goverwelle
  3. Update

    Between Utrecht Centraal and Rotterdam Centraal far fewer trains are running due to a person on the railway track.
    Between Gouda and Rotterdam Alexander there are delays and fewer trains are running due to a person on the railway track.
    It is not known yet how long this will take.

  4. Disruption

    Between Gouda and Rotterdam Alexander there are delays and fewer trains are running due to a person on the railway track.
    Between Utrecht Centraal and Rotterdam Centraal far fewer trains are running due to a person on the railway track.
    Updates will follow as more information becomes available.

More about this disruption

Statistics

This disruption started at 10:09 AM on July 31, 2019 and took 13 minutes in total.

For statistics, this disruption is caused due to a person on the railway track.

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