A new timetable will be introduced on Sunday, December 9. More information about the 2019 timetable

Disruption Utrecht-Baarn

Defective point
This disruption is resolved.

Current travel advice

Between Den Dolder and Soest the train traffic is fully resumed.

Advice

Local buses are running between Den Dolder, Soest Zuid and Soest.

Train measures

  • Sprinter 5500 Utrecht C. - Baarn is cancelled between Utrecht Centraal and Soest
Sep 9, 2017 12:44 AM

Earlier messages

Between Den Dolder and Soest there are no trains running due to a defective point.
This will take the rest of the day.

Advice

Local buses are running between Den Dolder, Soest Zuid and Soest.

Train measures

  • Sprinter 5500 Utrecht C. - Baarn is cancelled between Utrecht Centraal and Soest
Sep 8, 2017 5:02 PM

Between Den Dolder and Soest there are no trains running due to a defective point.
This will take until at least 5:30 PM hours.

Advice

Local buses are running between Den Dolder, Soest Zuid and Soest.

Train measures

  • Sprinter 5500 Utrecht C. - Baarn is cancelled between Utrecht Centraal and Soest
Sep 8, 2017 4:23 PM

Between Den Dolder and Soest there are no trains running due to a defective point.
This will take until at least 5:30 PM hours.

Train measures

  • Sprinter 5500 Utrecht C. - Baarn is cancelled between Utrecht Centraal and Soest
Sep 8, 2017 3:42 PM

Between Den Dolder and Soest there are no trains running due to a defective point.
This will take until at least 6:30 PM hours.

Train measures

  • Sprinter 5500 Utrecht C. - Baarn is cancelled between Utrecht Centraal and Soest
Sep 8, 2017 3:09 PM

Between Den Dolder and Soest there are no trains running due to a defective point.
It is not known yet how long this will take.

Train measures

  • Sprinter 5500 Utrecht C. - Baarn is cancelled between Utrecht Centraal and Soest
Sep 8, 2017 2:41 PM

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by NS.

Information

This disruption started at 2:41 PM on September 8, 2017 and took 10 hours, 4 minutes in total.

For statistics, this disruption is caused due to a defective point.