Disruption Roosendaal-Vlissingen

Points failure
This disruption is resolved.

Current travel advice

Between Roosendaal and Bergen op Zoom the train traffic is fully resumed.

Mar 6, 2017 9:14 AM

Earlier messages

Between Roosendaal and Bergen op Zoom the restrictions are resolved.
Delays are diminishing.
This will take until approximately 9:15 AM hours.

Mar 6, 2017 9:01 AM

Between Roosendaal and Bergen op Zoom the restrictions are resolved.
Delays are diminishing.
This will take until approximately 9:15 AM hours.

Advice

Express buses are still running between Roosendaal and Bergen op Zoom.

Mar 6, 2017 8:47 AM

Between Roosendaal and Bergen op Zoom no intercities are running due to a points failure.
This will take until approximately 9:15 AM hours.

Advice

Express buses are running between Roosendaal and Bergen op Zoom.
Express buses are running between Roosendaal and Essen.

Train measures

  • Intercity 2200 Amsterdam CS - Haarlem - Rotterdam C. - Vlissingen is cancelled between Roosendaal and Bergen op Zoom
Mar 6, 2017 8:03 AM

Between Roosendaal and Bergen op Zoom no intercities are running due to a points failure.
This will take until approximately 9:15 AM hours.

Train measures

  • Intercity 2200 Amsterdam CS - Haarlem - Rotterdam C. - Vlissingen is cancelled between Roosendaal and Bergen op Zoom
Mar 6, 2017 7:22 AM

Between Roosendaal and Bergen op Zoom no intercities are running due to a points failure.
This will take until approximately 9:15 AM hours.

Mar 6, 2017 7:19 AM

Between Roosendaal and Bergen op Zoom no intercities are running due to a points failure.
It is not known yet how long this will take.

Mar 6, 2017 6:46 AM

Between Roosendaal and Bergen op Zoom there is a service disruption due to a points failure.
Updates will follow as more information becomes available.

Mar 6, 2017 6:41 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:41 AM on March 6, 2017 and took 2 hours, 33 minutes in total.

For statistics, this disruption is caused due to a points failure.