Disruption Zwolle-Almelo; Deventer-Almelo

Points failure
This disruption is resolved.

Current travel advice

Between Wierden and Almelo the train traffic is fully resumed.

Feb 8, 2017 9:29 AM

Earlier messages

Between Wierden and Almelo the restrictions are resolved.
Delays are diminishing.
Service is normal around 9:30 AM hours.

Feb 8, 2017 9:13 AM

Between Wierden and Almelo there are no trains running due to a points failure.
Service is normal around 9:30 AM hours.

Feb 8, 2017 9:02 AM

Between Wierden and Almelo there are no trains running due to a points failure.
Service is normal around 9:30 AM hours.

Advice

Express buses are running between Wierden and Almelo.

Train measures

  • Intercity 140 Amsterdam CS - Hengelo - Hannover Hbf - Berlin Ostbhf is cancelled between Deventer and Bad Bentheim
  • Intercity 240 Amsterdam CS - Hengelo - Hannover Hbf - Berlin Ostbhf is cancelled between Deventer and Bad Bentheim
  • Intercity 1600 Schiphol Airport - Amersfoort - Hengelo - Enschede is cancelled between Deventer and Almelo
  • Intercity 1700 Den Haag C. - Amersfoort - Hengelo - Enschede is cancelled between Deventer and Almelo
  • Sprinter 7000 Apeldoorn - Almelo - Enschede is cancelled between Wierden and Enschede
  • Sprinter 7900 Zwolle - Almelo - Enschede is cancelled between Wierden and Almelo
Feb 8, 2017 8:44 AM

Between Wierden and Almelo there are no trains running due to a points failure.
This will take until at least 10:00 AM hours.

Advice

Express buses are running between Wierden and Almelo.

Train measures

  • Intercity 140 Amsterdam CS - Hengelo - Hannover Hbf - Berlin Ostbhf is cancelled between Deventer and Bad Bentheim
  • Intercity 240 Amsterdam CS - Hengelo - Hannover Hbf - Berlin Ostbhf is cancelled between Deventer and Bad Bentheim
  • Intercity 1600 Schiphol Airport - Amersfoort - Hengelo - Enschede is cancelled between Deventer and Almelo
  • Intercity 1700 Den Haag C. - Amersfoort - Hengelo - Enschede is cancelled between Deventer and Almelo
  • Sprinter 7000 Apeldoorn - Almelo - Enschede is cancelled between Wierden and Enschede
  • Sprinter 7900 Zwolle - Almelo - Enschede is cancelled between Wierden and Almelo
Feb 8, 2017 8:22 AM

Between Wierden and Almelo there are no trains running due to a points failure.
This will take until at least 10:00 AM hours.

Train measures

  • Intercity 140 Amsterdam CS - Hengelo - Hannover Hbf - Berlin Ostbhf is cancelled between Deventer and Bad Bentheim
  • Intercity 240 Amsterdam CS - Hengelo - Hannover Hbf - Berlin Ostbhf is cancelled between Deventer and Bad Bentheim
  • Intercity 1600 Schiphol Airport - Amersfoort - Hengelo - Enschede is cancelled between Deventer and Almelo
  • Intercity 1700 Den Haag C. - Amersfoort - Hengelo - Enschede is cancelled between Deventer and Almelo
  • Sprinter 7000 Apeldoorn - Almelo - Enschede is cancelled between Wierden and Enschede
  • Sprinter 7900 Zwolle - Almelo - Enschede is cancelled between Wierden and Almelo
Feb 8, 2017 7:54 AM

Between Wierden and Almelo there are no trains running due to a points failure.
It is not known yet how long this will take.

Train measures

  • Intercity 140 Amsterdam CS - Hengelo - Hannover Hbf - Berlin Ostbhf is cancelled between Deventer and Bad Bentheim
  • Intercity 240 Amsterdam CS - Hengelo - Hannover Hbf - Berlin Ostbhf is cancelled between Deventer and Bad Bentheim
  • Intercity 1600 Schiphol Airport - Amersfoort - Hengelo - Enschede is cancelled between Deventer and Almelo
  • Intercity 1700 Den Haag C. - Amersfoort - Hengelo - Enschede is cancelled between Deventer and Almelo
  • Sprinter 7000 Apeldoorn - Almelo - Enschede is cancelled between Wierden and Enschede
  • Sprinter 7900 Zwolle - Almelo - Enschede is cancelled between Wierden and Almelo
Feb 8, 2017 7:44 AM

Between Wierden and Almelo there are no trains running due to a points failure.
It is not known yet how long this will take.

Feb 8, 2017 7:31 AM

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 7:31 AM on February 8, 2017 and took 1 hour, 58 minutes in total.

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