Disruption Ede-Wageningen-Arnhem

Person hit by a train
This disruption is resolved.

Current travel advice

Between Ede-Wageningen and Arnhem Centraal the train traffic is fully resumed.

Mar 21, 2017 1:20 AM

Earlier messages

Between Ede-Wageningen and Arnhem Centraal the restrictions are resolved.
Delays are diminishing.
Service is normal around 1:15 AM hours.

Mar 21, 2017 1:11 AM

Between Ede-Wageningen and Arnhem Centraal there are no trains running due to a person hit by a train.
This will take until at least 1:00 AM on Tuesday, March 21, 2017.

Advice

Local buses are running between Ede-Wageningen, Wolfheze, Oosterbeek and Arnhem Centraal.
Express buses are running between Ede-Wageningen and Arnhem Centraal.

Train measures

  • Intercity 3000 Den Helder - Amsterdam CS - Utrecht C. - Nijmegen is cancelled between Ede-Wageningen and Arnhem Centraal
  • Intercity 3100 Schiphol Airport - Utrecht C. - Nijmegen is cancelled between Ede-Wageningen and Nijmegen
  • Sprinter 7500 Arnhem C. - Ede-Wageningen is cancelled between Ede-Wageningen and Arnhem Centraal
Mar 20, 2017 11:14 PM

Between Ede-Wageningen and Arnhem Centraal there are no trains running due to a person hit by a train.
This will take until at least 12:15 AM on Tuesday, March 21, 2017.

Advice

Local buses are running between Ede-Wageningen, Wolfheze, Oosterbeek and Arnhem Centraal.
Express buses are running between Ede-Wageningen and Arnhem Centraal.

Train measures

  • Intercity 3000 Den Helder - Amsterdam CS - Utrecht C. - Nijmegen is cancelled between Ede-Wageningen and Arnhem Centraal
  • Intercity 3100 Schiphol Airport - Utrecht C. - Nijmegen is cancelled between Ede-Wageningen and Nijmegen
  • Sprinter 7500 Arnhem C. - Ede-Wageningen is cancelled between Ede-Wageningen and Arnhem Centraal
Mar 20, 2017 10:42 PM

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

Advice

Express buses are running between Ede-Wageningen and Arnhem Centraal.
Local buses are running between Ede-Wageningen, Wolfheze, Oosterbeek and Arnhem Centraal.

Train measures

  • Intercity 3000 Den Helder - Amsterdam CS - Utrecht C. - Nijmegen is cancelled between Ede-Wageningen and Arnhem Centraal
  • Intercity 3100 Schiphol Airport - Utrecht C. - Nijmegen is cancelled between Ede-Wageningen and Nijmegen
  • Sprinter 7500 Arnhem C. - Ede-Wageningen is cancelled between Ede-Wageningen and Arnhem Centraal
Mar 20, 2017 10:20 PM

Between Ede-Wageningen and Arnhem Centraal there are no trains running due to a person hit by a train.
This will take until at least 11:45 PM hours.

Advice

Local buses are running between Ede-Wageningen, Wolfheze, Oosterbeek and Arnhem Centraal.
Express buses are running between Ede-Wageningen and Arnhem Centraal.

Train measures

  • Intercity 3000 Den Helder - Amsterdam CS - Utrecht C. - Nijmegen is cancelled between Ede-Wageningen and Arnhem Centraal
  • Intercity 3100 Schiphol Airport - Utrecht C. - Nijmegen is cancelled between Ede-Wageningen and Nijmegen
  • Sprinter 7500 Arnhem C. - Ede-Wageningen is cancelled between Ede-Wageningen and Arnhem Centraal
Mar 20, 2017 9:50 PM

Between Ede-Wageningen and Arnhem Centraal there are no trains running due to a person hit by a train.
This will take until at least 11:45 PM hours.

Train measures

  • Intercity 3000 Den Helder - Amsterdam CS - Utrecht C. - Nijmegen is cancelled between Ede-Wageningen and Arnhem Centraal
  • Intercity 3100 Schiphol Airport - Utrecht C. - Nijmegen is cancelled between Ede-Wageningen and Nijmegen
  • Sprinter 7500 Arnhem C. - Ede-Wageningen is cancelled between Ede-Wageningen and Arnhem Centraal
Mar 20, 2017 8:38 PM

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

Mar 20, 2017 8:27 PM

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by NS and NS International.

Information

This disruption started at 8:27 PM on March 20, 2017 and took 4 hours, 53 minutes in total.

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