Person hit by a train: Eindhoven-Roermond (4 January 2017)
-
Disruption resolved Last update
Between Weert and Roermond the train traffic is fully resumed.
-
Delays decreasing
Between Weert and Roermond the restrictions are resolved.
Delays are decreasing.
Service is normal around 12:15 AM on Thursday, January 5, 2017. -
Update
Between Weert and Roermond no trains are running due to a person hit by a train.
This will take until at least 12:15 AM on Thursday, January 5, 2017.Advice
Express buses are running between Weert and Roermond.
Train measures
- Intercity 800 Alkmaar - Utrecht C. - Eindhoven - Maastricht is cancelled between Weert and Roermond
- Intercity 3500 Schiphol Airport - Utrecht C. - Eindhoven - Heerlen is cancelled between Weert and Sittard
-
Update
Between Weert and Roermond no trains are running due to a person hit by a train.
It is not known yet how long this will take.Advice
Express buses are running between Weert and Roermond.
Train measures
- Intercity 800 Alkmaar - Utrecht C. - Eindhoven - Maastricht is cancelled between Weert and Roermond
- Intercity 3500 Schiphol Airport - Utrecht C. - Eindhoven - Heerlen is cancelled between Weert and Sittard
-
Update
Between Weert and Roermond no trains are running due to a person hit by a train.
It is not known yet how long this will take.Train measures
- Intercity 800 Alkmaar - Utrecht C. - Eindhoven - Maastricht is cancelled between Weert and Roermond
- Intercity 3500 Schiphol Airport - Utrecht C. - Eindhoven - Heerlen is cancelled between Weert and Sittard
-
Update
Between Weert and Roermond no trains are running due to a person hit by a train.
The extra travel time may be up to 60 minutes.
It is not known yet how long this will take.Train measures
- Intercity 800 Alkmaar - Utrecht C. - Eindhoven - Maastricht is cancelled between Weert and Roermond
- Intercity 3500 Schiphol Airport - Utrecht C. - Eindhoven - Heerlen is cancelled between Weert and Sittard
-
Disruption
Between Weert and Roermond there is a service disruption due to a stranded train.
Updates will follow as more information becomes available.
More about this disruption
Statistics
This disruption started at 8:41 PM on January 4, 2017 and took 3 hours, 35 minutes in total.
For statistics, this disruption is caused due to a person hit by a train.
Operators
This disruption affects trains operated by NS.
Got delayed due to this disruption? You may be reimbursed.