Disruption Zutphen-Winterswijk

Level crossing failure
This disruption is resolved.

Current travel advice

Between Vorden and Winterswijk the train traffic is fully resumed.

Aug 15, 2017 4:43 PM

Earlier messages

Between Vorden and Winterswijk the restrictions are resolved.
Delays are diminishing.
Service is normal around 4:45 PM hours.

Advice

Local buses are still running between Vorden, Ruurlo, Lichtenvoorde-Groenlo, Winterswijk West and Winterswijk.

Aug 15, 2017 4:19 PM

Between Vorden and Winterswijk there are no trains running due to a level crossing failure.
This will take until approximately 5:00 PM hours.

Advice

Local buses are running between Vorden, Ruurlo, Lichtenvoorde-Groenlo, Winterswijk West and Winterswijk.

Train measures

  • Stoptrein 30800 Zutphen - Vorden - Winterswijk is cancelled between Vorden and Winterswijk
Aug 15, 2017 3:26 PM

Between Vorden and Winterswijk there are no trains running due to a level crossing failure.
This will take until approximately 5:00 PM hours.

Train measures

  • Stoptrein 30800 Zutphen - Vorden - Winterswijk is cancelled between Vorden and Winterswijk
Aug 15, 2017 3:06 PM

Between Vorden and Winterswijk there are no trains running due to a level crossing failure.
It is not known yet how long this will take.

Train measures

  • Stoptrein 30800 Zutphen - Vorden - Winterswijk is cancelled between Vorden and Winterswijk
Aug 15, 2017 3:03 PM

Between Vorden and Winterswijk there are no trains running due to a level crossing failure.
It is not known yet how long this will take.

Aug 15, 2017 2:50 PM

Between Zutphen and Winterswijk there are no trains running due to a level crossing failure.
It is not known yet how long this will take.

Aug 15, 2017 2:46 PM

Between Zutphen and Winterswijk there is a service disruption due to a level crossing failure.
Updates will follow as more information becomes available.

Aug 15, 2017 2:25 PM

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by Arriva.

Information

This disruption started at 2:25 PM on August 15, 2017 and took 2 hours, 18 minutes in total.

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