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

Disruption Gouda-Den Haag

Person hit by a train
This disruption is resolved.

Current travel advice

Between Zoetermeer Oost and Den Haag Ypenburg the train traffic is fully resumed.

Jun 23, 2017 4:59 PM

Earlier messages

Between Zoetermeer Oost and Den Haag Ypenburg the restrictions are resolved.
Delays are diminishing.
Service is normal around 5:00 PM hours.

Jun 23, 2017 4:29 PM

Between Zoetermeer Oost and Den Haag Ypenburg there are no trains running due to a person hit by a train.
This will take until approximately 5:00 PM hours.

Advice

Passengers between Utrecht Centraal and Den Haag Centraal travel via Rotterdam Centraal. The extra travel time is up to 30 minutes.

Train measures

  • Intercity 1700 Den Haag C. - Amersfoort - Hengelo - Enschede is cancelled between Den Haag Centraal and Utrecht Centraal
  • Intercity 2000 Den Haag C. - Utrecht C. is cancelled between Den Haag Centraal and Utrecht Centraal
  • Sprinter 6800 Den Haag C. - Gouda Goverwelle is cancelled between Den Haag Centraal and Gouda Goverwelle
  • Sprinter 7800 Den Haag C. - Utrecht C. is cancelled between Zoetermeer Oost and Den Haag Ypenburg
  • Intercity 11700 Den Haag C. - Utrecht C. - Schothorst is cancelled between Den Haag Centraal and Utrecht Centraal
Jun 23, 2017 3:59 PM

Between Zoetermeer Oost and Den Haag Ypenburg there are no trains running due to a person hit by a train.
This will take until approximately 4:15 PM hours.

Advice

Passengers between Utrecht Centraal and Den Haag Centraal travel via Rotterdam Centraal. The extra travel time is up to 30 minutes.

Train measures

  • Intercity 1700 Den Haag C. - Amersfoort - Hengelo - Enschede is cancelled between Den Haag Centraal and Utrecht Centraal
  • Intercity 2000 Den Haag C. - Utrecht C. is cancelled between Den Haag Centraal and Utrecht Centraal
  • Sprinter 6800 Den Haag C. - Gouda Goverwelle is cancelled between Den Haag Centraal and Gouda Goverwelle
  • Sprinter 7800 Den Haag C. - Utrecht C. is cancelled between Zoetermeer Oost and Den Haag Ypenburg
  • Intercity 11700 Den Haag C. - Utrecht C. - Schothorst is cancelled between Den Haag Centraal and Utrecht Centraal
Jun 23, 2017 1:29 PM

Between Zoetermeer Oost and Den Haag Ypenburg there are no trains running due to a person hit by a train.
It is not known yet how long this will take.

Advice

Passengers between Utrecht Centraal and Den Haag Centraal travel via Rotterdam Centraal. The extra travel time is up to 30 minutes.

Train measures

  • Intercity 1700 Den Haag C. - Amersfoort - Hengelo - Enschede is cancelled between Den Haag Centraal and Utrecht Centraal
  • Intercity 2000 Den Haag C. - Utrecht C. is cancelled between Den Haag Centraal and Utrecht Centraal
  • Sprinter 6800 Den Haag C. - Gouda Goverwelle is cancelled between Den Haag Centraal and Gouda Goverwelle
  • Sprinter 7800 Den Haag C. - Utrecht C. is cancelled between Zoetermeer Oost and Den Haag Ypenburg
  • Intercity 11700 Den Haag C. - Utrecht C. - Schothorst is cancelled between Den Haag Centraal and Utrecht Centraal
Jun 23, 2017 1:28 PM

Between Zoetermeer Oost and Den Haag Ypenburg there are no trains running due to a person hit by a train.
It is not known yet how long this will take.

Advice

Passengers between Utrecht Centraal and Den Haag Centraal travel via Rotterdam Centraal. The extra travel time is up to 30 minutes.

Jun 23, 2017 1:05 PM

Between Gouda and Den Haag Centraal there are no trains running due to a person hit by a train.
It is not known yet how long this will take.

Advice

Passengers between Utrecht Centraal and Den Haag Centraal travel via Rotterdam Centraal. The extra travel time is up to 30 minutes.

Jun 23, 2017 12:52 PM

Between Gouda and Den Haag Centraal there are no trains running due to a person hit by a train.
It is not known yet how long this will take.

Jun 23, 2017 12:48 PM

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by NS.

Information

This disruption started at 12:48 PM on June 23, 2017 and took 4 hours, 11 minutes in total.

For statistics, this disruption is caused due to a person hit by a train.