Signal failure: Almelo-Hardenberg (13 May 2017)
-
Disruption resolved Last update
Between Almelo and Vroomshoop the train traffic is fully resumed.
-
Delays decreasing
Between Almelo and Vroomshoop the restrictions are resolved.
Delays are decreasing.
Service is normal around 7:30 PM hours. -
Delays decreasing
Between Almelo and Vroomshoop the restrictions are resolved.
Delays are decreasing.
Service is normal around 7:30 PM hours.Advice
Local buses are still running between Almelo, Vriezenveen, Daarlerveen and Vroomshoop.
-
Update
Between Almelo and Vroomshoop no trains are running due to a signal failure.
Service is normal around 7:30 PM hours.Advice
Local buses are running between Almelo, Vriezenveen, Daarlerveen and Vroomshoop.
Train measures
- Stoptrein 31000 Almelo - Mariënberg is cancelled between Almelo and Vroomshoop
-
Update
Between Almelo and Vroomshoop no trains are running due to a signal failure.
It is not known yet how long this will take.Advice
Local buses are running between Almelo, Vriezenveen, Daarlerveen and Vroomshoop.
Train measures
- Stoptrein 31000 Almelo - Mariënberg is cancelled between Almelo and Vroomshoop
-
Update
Between Almelo and Vroomshoop no trains are running due to a signal failure.
This will take until approximately 6:45 PM hours.Advice
Local buses are running between Almelo, Vriezenveen, Daarlerveen and Vroomshoop.
Train measures
- Stoptrein 31000 Almelo - Mariënberg is cancelled between Almelo and Vroomshoop
-
Update
Between Almelo and Vroomshoop no trains are running due to a signal failure.
This will take until approximately 6:45 PM hours.Train measures
- Stoptrein 31000 Almelo - Mariënberg is cancelled between Almelo and Vroomshoop
-
Update
Between Almelo and Vroomshoop no trains are running due to a signal failure.
It is not known yet how long this will take.Train measures
- Stoptrein 31000 Almelo - Mariënberg is cancelled between Almelo and Vroomshoop
-
Disruption
Between Almelo and Vroomshoop no trains are running due to a signal failure.
It is not known yet how long this will take.
More about this disruption
Statistics
This disruption started at 4:18 PM on May 13, 2017 and took 3 hours, 10 minutes in total.
For statistics, this disruption is caused due to a signal failure.
Operators
This disruption affects trains operated by Arriva.
Got delayed due to this disruption? You may be reimbursed.