Signal failure: Utrecht-Rhenen (19 June 2017)
-
Disruption resolved Last update
Between Driebergen-Zeist and Rhenen the train traffic is fully resumed.
-
Delays decreasing
Between Driebergen-Zeist and Rhenen the restrictions are resolved.
Delays are decreasing.
Service is normal around 6:45 PM hours.Advice
Local buses are still running between Driebergen-Zeist, Maarn, Veenendaal West, Veenendaal Centrum and Rhenen.
Local buses are still running between Bunnik and Driebergen-Zeist.
Passengers between Utrecht Centraal and Bunnik travel via Driebergen-Zeist. The extra travel time is up to 30 minutes. -
Update
Between Driebergen-Zeist and Rhenen no trains are running due to a signal failure.
The extra travel time may be up to 60 minutes.
This will take until approximately 7:00 PM hours.Advice
Local buses are running between Driebergen-Zeist, Maarn, Veenendaal West, Veenendaal Centrum and Rhenen.
Local buses are running between Bunnik and Driebergen-Zeist.
Passengers between Utrecht Centraal and Bunnik travel via Driebergen-Zeist. The extra travel time is up to 30 minutes.Train measures
- Sprinter 7300 Veenendaal C. - Utrecht C. - Breukelen is cancelled between Breukelen and Veenendaal Centrum
- Sprinter 7400 Amsterdam C. - Utrecht C. - Rhenen is cancelled between Utrecht Centraal and Rhenen
-
Update
Between Driebergen-Zeist and Rhenen no trains are running due to a signal failure.
The extra travel time is more than 60 minutes.
It is not known yet how long this will take.Train measures
- Sprinter 7300 Veenendaal C. - Utrecht C. - Breukelen is cancelled between Breukelen and Veenendaal Centrum
- Sprinter 7400 Amsterdam C. - Utrecht C. - Rhenen is cancelled between Utrecht Centraal and Rhenen
-
Update
Between Driebergen-Zeist and Rhenen no trains are running due to a signal failure.
The extra travel time is more than 60 minutes.
It is not known yet how long this will take. -
Disruption
Between Veenendaal West and Rhenen there is a service disruption due to a signal failure.
Updates will follow as more information becomes available.
More about this disruption
Statistics
This disruption started at 4:21 PM on June 19, 2017 and took 2 hours, 24 minutes in total.
For statistics, this disruption is caused due to a signal failure.
Operators
This disruption affects trains operated by NS.
Got delayed due to this disruption? You may be reimbursed.