Disruption Sittard-Maastricht

Signal failure
This disruption is resolved.

Current travel advice

Between Sittard and Maastricht the train traffic is fully resumed.

Advice

Local buses are running between Sittard, Geleen-Lutterade, Beek-Elsloo, Bunde and Maastricht.

Train measures

  • Stoptrein 32400 Roermond - Maastricht - Maastricht Randw is cancelled between Sittard and Maastricht
May 27, 2018 12:33 AM

Earlier messages

Between Sittard and Maastricht no local trains are running due to a signal failure.
This will take until approximately 1:00 AM on Sunday, May 27, 2018.

Advice

Local buses are running between Sittard, Geleen-Lutterade, Beek-Elsloo, Bunde and Maastricht.

Train measures

  • Stoptrein 32400 Roermond - Maastricht - Maastricht Randw is cancelled between Sittard and Maastricht
May 26, 2018 11:47 PM

Between Sittard and Maastricht no local trains are running due to a signal failure.
It is not known yet how long this will take.

Advice

Local buses are running between Sittard, Geleen-Lutterade, Beek-Elsloo, Bunde and Maastricht.

Train measures

  • Stoptrein 32400 Roermond - Maastricht - Maastricht Randw is cancelled between Sittard and Maastricht
May 26, 2018 9:22 PM

Between Sittard and Maastricht no local trains are running due to a signal failure.
This will take until approximately 10:30 PM hours.

Advice

Local buses are running between Sittard, Geleen-Lutterade, Beek-Elsloo, Bunde and Maastricht.

Train measures

  • Stoptrein 32400 Roermond - Maastricht - Maastricht Randw is cancelled between Sittard and Maastricht
May 26, 2018 9:19 PM

Between Sittard and Maastricht no local trains are running due to a signal failure.
This will take until approximately 10:00 PM hours.

Advice

Local buses are running between Sittard, Geleen-Lutterade, Beek-Elsloo, Bunde and Maastricht.

Train measures

  • Stoptrein 32400 Roermond - Maastricht - Maastricht Randw is cancelled between Sittard and Maastricht
May 26, 2018 8:36 PM

Between Sittard and Maastricht no local trains are running due to a signal failure.
This will take until approximately 9:30 PM hours.

Advice

Local buses are running between Sittard, Geleen-Lutterade, Beek-Elsloo, Bunde and Maastricht.

Train measures

  • Stoptrein 32400 Roermond - Maastricht - Maastricht Randw is cancelled between Sittard and Maastricht
May 26, 2018 8:22 PM

Between Sittard and Maastricht no local trains are running due to a signal failure.
This will take until approximately 9:30 PM hours.

Train measures

  • Stoptrein 32400 Roermond - Maastricht - Maastricht Randw is cancelled between Sittard and Maastricht
May 26, 2018 8:01 PM

Between Sittard and Maastricht no local trains are running due to a signal failure.
This will take until approximately 9:00 PM hours.

Train measures

  • Stoptrein 32400 Roermond - Maastricht - Maastricht Randw is cancelled between Sittard and Maastricht
May 26, 2018 7:48 PM

Between Sittard and Maastricht no local trains are running due to a signal failure.
This will take until approximately 8:30 PM hours.

Train measures

  • Stoptrein 32400 Roermond - Maastricht - Maastricht Randw is cancelled between Sittard and Maastricht
May 26, 2018 7:22 PM

Between Sittard and Maastricht no local trains are running due to a signal failure.
This will take until approximately 8:00 PM hours.

Train measures

  • Stoptrein 32400 Roermond - Maastricht - Maastricht Randw is cancelled between Sittard and Maastricht
May 26, 2018 6:44 PM

Between Sittard and Maastricht no local trains are running due to a signal failure.
It is not known yet how long this will take.

Train measures

  • Stoptrein 32400 Roermond - Maastricht - Maastricht Randw is cancelled between Sittard and Maastricht
May 26, 2018 6:39 PM

Between Sittard and Maastricht no local trains are running due to a signal failure.
It is not known yet how long this will take.

May 26, 2018 6:38 PM

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by NS and Arriva.

Information

This disruption started at 6:38 PM on May 26, 2018 and took 5 hours, 55 minutes in total.

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