Points failure: Zwolle-Groningen (24 July 2017)
-
Disruption resolved Last update
Between Meppel and Hoogeveen the train traffic is fully resumed.
-
Delays decreasing
Between Meppel and Hoogeveen the restrictions are resolved.
Delays are decreasing.
Service is normal around 5:00 PM hours. -
Update
Between Meppel and Hoogeveen no trains are running due to a points failure.
The extra travel time may be up to 60 minutes.
It is not known yet how long this will take.Train measures
- Intercity 500 Rotterdam C. - Utrecht C. - Zwolle - Groningen is cancelled between Meppel and Hoogeveen
- Intercity 700 Den Haag C. - Schiphol Airport - Lelystad C. - Groningen is cancelled between Meppel and Hoogeveen
- Sprinter 8100 Zwolle - Groningen is cancelled between Meppel and Hoogeveen
-
Update
Between Meppel and Assen no trains are running due to a points failure.
The extra travel time may be up to 60 minutes.
It is not known yet how long this will take.Train measures
- Intercity 500 Rotterdam C. - Utrecht C. - Zwolle - Groningen is cancelled between Meppel and Hoogeveen
- Intercity 700 Den Haag C. - Schiphol Airport - Lelystad C. - Groningen is cancelled between Meppel and Hoogeveen
- Sprinter 8100 Zwolle - Groningen is cancelled between Meppel and Hoogeveen
-
Update
Between Meppel and Assen no trains are running due to a points failure.
It is not known yet how long this will take.Train measures
- Intercity 500 Rotterdam C. - Utrecht C. - Zwolle - Groningen is cancelled between Meppel and Hoogeveen
- Intercity 700 Den Haag C. - Schiphol Airport - Lelystad C. - Groningen is cancelled between Meppel and Hoogeveen
- Sprinter 8100 Zwolle - Groningen is cancelled between Meppel and Hoogeveen
-
Update
Between Meppel and Assen no trains are running due to a points failure.
It is not known yet how long this will take. -
Disruption
Between Meppel and Assen there is a service disruption due to a cause yet unknown.
Updates will follow as more information becomes available.
More about this disruption
Statistics
This disruption started at 3:53 PM on July 24, 2017 and took 1 hour, 7 minutes in total.
For statistics, this disruption is caused due to a points failure.
Operators
This disruption affects trains operated by NS.
Got delayed due to this disruption? You may be reimbursed.