Disruption Arnhem-Nijmegen

Person hit by a train
This disruption is resolved.

Current travel advice

Between Arnhem Centraal and Nijmegen the train traffic is fully resumed.

Train measures

  • Intercity 3000 Den Helder - Amsterdam C. - Utrecht C. - Nijmegen is cancelled between Arnhem Centraal and Nijmegen
  • Intercity 3100 Schiphol Airport - Utrecht C. - Nijmegen is cancelled between Arnhem Centraal and Nijmegen
  • Intercity 3600 Zwolle - Deventer - Nijmegen - Roosendaal is cancelled between Arnhem Centraal and Nijmegen
  • Sprinter 4400 's-Hertogenbosch - Nijmegen - Arnhem C. is cancelled between Abcoude and Nijmegen
Jul 15, 2017 2:42 AM

Earlier messages

Between Arnhem Centraal and Nijmegen there are no trains running due to a person hit by a train.
This will take the rest of the day.

Train measures

  • Intercity 3000 Den Helder - Amsterdam C. - Utrecht C. - Nijmegen is cancelled between Arnhem Centraal and Nijmegen
  • Intercity 3100 Schiphol Airport - Utrecht C. - Nijmegen is cancelled between Arnhem Centraal and Nijmegen
  • Intercity 3600 Zwolle - Deventer - Nijmegen - Roosendaal is cancelled between Arnhem Centraal and Nijmegen
  • Sprinter 4400 's-Hertogenbosch - Nijmegen - Arnhem C. is cancelled between Abcoude and Nijmegen
Jul 15, 2017 12:13 AM

Between Arnhem Centraal and Nijmegen there are no trains running due to a person hit by a train.
This will take the rest of the day.

Jul 15, 2017 12:11 AM

Between Arnhem Centraal and Elst there are no trains running due to a person hit by a train.
This will take the rest of the day.

Jul 15, 2017 12:08 AM

Between Arnhem Centraal and Nijmegen there are no trains running due to a person hit by a train.
This will take the rest of the day.

Jul 14, 2017 11:55 PM

Between Arnhem Centraal and Nijmegen there are no trains running due to a person hit by a train.
It is not known yet how long this will take.

Jul 14, 2017 11:52 PM

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by NS.

Information

This disruption started at 11:52 PM on July 14, 2017 and took 2 hours, 50 minutes in total.

For statistics, this disruption is caused due to a person hit by a train.