Power failure: Hilversum (5 July 2017)

This disruption is resolved.

Disruption resolved Last update

From and to Hilversum the train traffic is fully resumed.

Advice

Passengers between Amersfoort and Schiphol Airport travel via Utrecht Centraal. The extra travel time is up to 30 minutes.
July 5, 2017, 4:29 PM
Show complete timeline…
Delays decreasing

From and to Hilversum the restrictions are resolved.
Delays are decreasing.
Service is normal around 4:45 PM hours.

Advice

Passengers between Amersfoort and Schiphol Airport travel via Utrecht Centraal. The extra travel time is up to 30 minutes.
July 5, 2017, 4:15 PM
Update

From and to Hilversum far fewer trains are running due to a power failure.
It is not known yet how long this will take.

Advice

Passengers between Amersfoort and Schiphol Airport travel via Utrecht Centraal. The extra travel time is up to 30 minutes.

Train measures
- Intercity 140-149 Amsterdam C. - Hengelo - Hannover Hbf - Berlin Ostbhf is cancelled between Amsterdam Centraal and Amersfoort
- Intercity 1500 Amsterdam C. - Amersfoort is cancelled between Amersfoort and Amsterdam Centraal
- Intercity 1600 Schiphol Airport - Amersfoort - Hengelo - Enschede is cancelled between Amersfoort and Schiphol Airport
- Sprinter 4900 Utrecht C. - Hilversum - Almere C. is cancelled between Utrecht Centraal and Naarden-Bussum
- Sprinter 5500 Utrecht C. - Baarn is cancelled between Baarn and Soest
- Sprinter 5700 Utrecht C. - Hilversum - Hoofddorp is cancelled between Naarden-Bussum and Utrecht Centraal
- Intercity 11600 Schiphol Airport - Amersfoort - Schothorst is cancelled between Amersfoort Schothorst and Schiphol Airport
- Sprinter 15800 Amsterdam C. - Vathorst is cancelled between Naarden-Bussum and Amersfoort Vathorst
July 5, 2017, 3:53 PM
Update

From and to Hilversum there are fewer trains running due to a power failure.
It is not known yet how long this will take.

Advice

Passengers between Amersfoort and Schiphol Airport travel via Utrecht Centraal. The extra travel time is up to 30 minutes.

Train measures
- Intercity 140-149 Amsterdam C. - Hengelo - Hannover Hbf - Berlin Ostbhf is cancelled between Amsterdam Centraal and Amersfoort
- Intercity 1500 Amsterdam C. - Amersfoort is cancelled between Amersfoort and Amsterdam Centraal
- Intercity 1600 Schiphol Airport - Amersfoort - Hengelo - Enschede is cancelled between Amersfoort and Schiphol Airport
- Sprinter 4900 Utrecht C. - Hilversum - Almere C. is cancelled between Utrecht Centraal and Naarden-Bussum
- Sprinter 5500 Utrecht C. - Baarn is cancelled between Baarn and Soest
- Sprinter 5700 Utrecht C. - Hilversum - Hoofddorp is cancelled between Naarden-Bussum and Utrecht Centraal
- Intercity 11600 Schiphol Airport - Amersfoort - Schothorst is cancelled between Amersfoort Schothorst and Schiphol Airport
- Sprinter 15800 Amsterdam C. - Vathorst is cancelled between Naarden-Bussum and Amersfoort Vathorst
July 5, 2017, 3:48 PM
Update

From and to Hilversum no trains are running due to a power failure.
It is not known yet how long this will take.

Advice

Passengers between Amersfoort and Schiphol Airport travel via Utrecht Centraal. The extra travel time is up to 30 minutes.

Train measures
- Intercity 140-149 Amsterdam C. - Hengelo - Hannover Hbf - Berlin Ostbhf is cancelled between Amsterdam Centraal and Amersfoort
- Intercity 1500 Amsterdam C. - Amersfoort is cancelled between Amersfoort and Amsterdam Centraal
- Intercity 1600 Schiphol Airport - Amersfoort - Hengelo - Enschede is cancelled between Amersfoort and Schiphol Airport
- Sprinter 4900 Utrecht C. - Hilversum - Almere C. is cancelled between Utrecht Centraal and Naarden-Bussum
- Sprinter 5500 Utrecht C. - Baarn is cancelled between Baarn and Soest
- Sprinter 5700 Utrecht C. - Hilversum - Hoofddorp is cancelled between Naarden-Bussum and Utrecht Centraal
- Intercity 11600 Schiphol Airport - Amersfoort - Schothorst is cancelled between Amersfoort Schothorst and Schiphol Airport
- Sprinter 15800 Amsterdam C. - Vathorst is cancelled between Naarden-Bussum and Amersfoort Vathorst
July 5, 2017, 3:47 PM
Update

From and to Hilversum no trains are running due to a power failure.
It is not known yet how long this will take.

Advice

Passengers between Amersfoort and Schiphol Airport travel via Utrecht Centraal. The extra travel time is up to 30 minutes.
July 5, 2017, 3:06 PM
Update

From and to Hilversum no trains are running due to a power failure.
The extra travel time is more than 60 minutes.
It is not known yet how long this will take.

Advice

Passengers between Amersfoort and Schiphol Airport travel via Utrecht Centraal. The extra travel time is up to 30 minutes.
July 5, 2017, 2:51 PM
Update

From and to Hilversum no trains are running due to a power failure.
The extra travel time is more than 60 minutes.
It is not known yet how long this will take.
July 5, 2017, 2:49 PM
Update

From and to Hilversum no trains are running due to a power failure.
It is not known yet how long this will take.
July 5, 2017, 2:45 PM
Update

Between Hilversum and Baarn no trains are running due to a power failure.
It is not known yet how long this will take.
July 5, 2017, 2:33 PM
Disruption reported

Between Hilversum and Baarn there is a service disruption due to a signalling and points failure.
Updates will follow as more information becomes available.
July 5, 2017, 2:26 PM

Location of this disruption

This disruption is around Hilversum.

More about this disruption

Statistics

This disruption started at 2:26 PM on July 5, 2017 and took 2 hours, 3 minutes in total.

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

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by NS and NS International.

Got delayed due to this disruption? You may be reimbursed.

Refunds and passenger rights

Power failure: Hilversum (5 July 2017)

Disruption resolved Last update

Advice

Delays decreasing

Advice

Update

Advice

Train measures

Update

Advice

Train measures

Update

Advice

Train measures

Update

Advice

Update

Advice

Update

Update

Update

Disruption reported

Location of this disruption

More about this disruption

Statistics

Affected lines

Operators