Disruption Hengelo-Enschede

Points failure
This disruption is resolved.

Current travel advice

Between Hengelo and Enschede the train traffic is fully resumed.

May 30, 2017 12:29 AM

Earlier messages

Between Hengelo and Enschede the restrictions are resolved.
Delays are diminishing.
Service is normal around 12:30 AM hours.

May 30, 2017 12:14 AM

Between Hengelo and Enschede the restrictions are resolved.
Delays are diminishing.
Service is normal around 12:30 AM on Tuesday, May 30, 2017.

Advice

Local buses are running between Hengelo, Enschede Kennispark and Enschede.

May 29, 2017 11:37 PM

Between Hengelo and Enschede no Sprinters are running due to a points failure.
The extra travel time is more than 60 minutes.
This will take until approximately 12:30 AM on Tuesday, May 30, 2017.

Advice

Local buses are running between Hengelo, Enschede Kennispark and Enschede.

Train measures

  • Sprinter 7000 Apeldoorn - Almelo - Enschede is cancelled between Hengelo and Enschede
  • Sprinter 7900 Zwolle - Almelo - Enschede is cancelled between Hengelo and Enschede
May 29, 2017 10:23 PM

Between Hengelo and Enschede no Sprinters are running due to a points failure.
The extra travel time is more than 60 minutes.
This will take until approximately 12:30 AM on Tuesday, May 30, 2017.

Train measures

  • Sprinter 7000 Apeldoorn - Almelo - Enschede is cancelled between Hengelo and Enschede
  • Sprinter 7900 Zwolle - Almelo - Enschede is cancelled between Hengelo and Enschede
May 29, 2017 10:13 PM

Between Hengelo and Enschede no Sprinters are running due to a points failure.
The extra travel time is more than 60 minutes.
It is not known yet how long this will take.

Train measures

  • Sprinter 7000 Apeldoorn - Almelo - Enschede is cancelled between Hengelo and Enschede
  • Sprinter 7900 Zwolle - Almelo - Enschede is cancelled between Hengelo and Enschede
May 29, 2017 9:55 PM

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by NS.

Information

This disruption started at 9:55 PM on May 29, 2017 and took 2 hours, 34 minutes in total.

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