Disruption Den Haag-Rotterdam

Disruption elsewhere
This disruption is resolved.

Current travel advice

Between Den Haag Centraal and Rotterdam Centraal the train traffic is fully resumed.

Aug 11, 2017 8:45 AM

Earlier messages

Between Den Haag Centraal and Rotterdam Centraal the restrictions are resolved.
Delays are diminishing.
Service is normal around 9:00 AM hours.

Aug 11, 2017 8:20 AM

Between Den Haag Centraal and Rotterdam Centraal fewer intercities are running due to a disruption elsewhere.
The extra travel time may be up to 15 minutes.
This will take until approximately 9:00 AM hours.

Train measures

  • Intercity 1100 Den Haag C. - Rotterdam C. - Breda is cancelled between Den Haag Centraal and Rotterdam Centraal
Aug 11, 2017 8:08 AM

Between Den Haag Centraal and Rotterdam Centraal fewer intercities are running due to a disruption elsewhere.
The extra travel time may be up to 15 minutes.
This will take until approximately 8:30 AM hours.

Train measures

  • Intercity 1100 Den Haag C. - Rotterdam C. - Breda is cancelled between Den Haag Centraal and Rotterdam Centraal
Aug 11, 2017 7:34 AM

Between Den Haag Centraal and Rotterdam Centraal fewer intercities are running due to a disruption elsewhere.
The extra travel time may be up to 15 minutes.
It is not known yet how long this will take.

Train measures

  • Intercity 1100 Den Haag C. - Rotterdam C. - Breda is cancelled between Den Haag Centraal and Rotterdam Centraal
Aug 11, 2017 7:29 AM

Between Den Haag Centraal and Rotterdam Centraal fewer intercities are running due to a disruption elsewhere.
The extra travel time may be up to 15 minutes.
It is not known yet how long this will take.

Aug 11, 2017 7:03 AM

Between Den Haag Centraal and Rotterdam Centraal fewer intercities are running due to a broken down train.
The extra travel time may be up to 15 minutes.
It is not known yet how long this will take.

Aug 11, 2017 6:46 AM

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by NS.

Information

This disruption started at 6:46 AM on August 11, 2017 and took 1 hour, 59 minutes in total.

For statistics, this disruption is caused due to a disruption elsewhere.