Disruption Utrecht-Amersfoort

Unexpected engineering works
This disruption is resolved.

Current travel advice

Between Utrecht Centraal and Amersfoort the train traffic is fully resumed.

Train measures

  • Intercity 500 Rotterdam C. - Utrecht C. - Zwolle - Groningen is cancelled between Utrecht Centraal and Amersfoort (only in direction of Amersfoort)
  • Intercity 600 Rotterdam C. - Utrecht C. - Zwolle - Leeuwarden is cancelled between Amersfoort and Utrecht Centraal (only in direction of Utrecht Centraal)
  • Intercity 1700 Den Haag C. - Amersfoort - Hengelo - Enschede is cancelled between Utrecht Centraal and Amersfoort
Jun 26, 2017 12:58 AM

Earlier messages

Between Utrecht Centraal and Amersfoort the restrictions are resolved.
Delays are diminishing.
Service is normal around 1:00 AM hours.

Train measures

  • Intercity 500 Rotterdam C. - Utrecht C. - Zwolle - Groningen is cancelled between Utrecht Centraal and Amersfoort (only in direction of Amersfoort)
  • Intercity 600 Rotterdam C. - Utrecht C. - Zwolle - Leeuwarden is cancelled between Amersfoort and Utrecht Centraal (only in direction of Utrecht Centraal)
  • Intercity 1700 Den Haag C. - Amersfoort - Hengelo - Enschede is cancelled between Utrecht Centraal and Amersfoort
Jun 26, 2017 12:46 AM

Between Utrecht Centraal and Amersfoort fewer intercities are running due to unexpected engineering works.
This will take the rest of the day.

Train measures

  • Intercity 500 Rotterdam C. - Utrecht C. - Zwolle - Groningen is cancelled between Utrecht Centraal and Amersfoort (only in direction of Amersfoort)
  • Intercity 600 Rotterdam C. - Utrecht C. - Zwolle - Leeuwarden is cancelled between Amersfoort and Utrecht Centraal (only in direction of Utrecht Centraal)
  • Intercity 1700 Den Haag C. - Amersfoort - Hengelo - Enschede is cancelled between Utrecht Centraal and Amersfoort
Jun 25, 2017 10:00 PM

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by NS.

Information

This disruption started at 10:00 PM on June 25, 2017 and took 2 hours, 58 minutes in total.

For statistics, this disruption is caused due to unexpected engineering works.