aanrijding

Collision with a vehicle: Zwolle-Groningen (13 June 2017)

  1. Disruption resolved Last update

    Between Meppel and Hoogeveen the train traffic is fully resumed.

  2. Update

    Between Meppel and Hoogeveen no trains are running due to a collision with a vehicle.
    The extra travel time may be up to 45 minutes.
    This will take the rest of the day.

    Advice

    Express buses are running between Meppel and Hoogeveen.

    Train measures

    • Intercity 500 Rotterdam C. - Utrecht C. - Zwolle - Groningen is cancelled between Meppel and Hoogeveen
    • Intercity 700 Den Haag C. - Schiphol Airport - Lelystad C. - Groningen is cancelled between Meppel and Hoogeveen
    • Sprinter 8100 Zwolle - Groningen is cancelled between Meppel and Hoogeveen
  3. Update

    Between Meppel and Hoogeveen no trains are running due to a collision with a vehicle.
    The extra travel time may be up to 60 minutes.
    This will take the rest of the day.

    Train measures

    • Intercity 500 Rotterdam C. - Utrecht C. - Zwolle - Groningen is cancelled between Meppel and Hoogeveen
    • Intercity 700 Den Haag C. - Schiphol Airport - Lelystad C. - Groningen is cancelled between Meppel and Hoogeveen
    • Sprinter 8100 Zwolle - Groningen is cancelled between Meppel and Hoogeveen
  4. Update

    Between Meppel and Hoogeveen no trains are running due to a collision with a vehicle.
    This will take the rest of the day.

    Train measures

    • Intercity 500 Rotterdam C. - Utrecht C. - Zwolle - Groningen is cancelled between Meppel and Hoogeveen
    • Intercity 700 Den Haag C. - Schiphol Airport - Lelystad C. - Groningen is cancelled between Meppel and Hoogeveen
    • Sprinter 8100 Zwolle - Groningen is cancelled between Meppel and Hoogeveen
  5. Update

    Between Meppel and Hoogeveen no trains are running due to a collision with a vehicle.
    It is not known yet how long this will take.

  6. Disruption

    Between Meppel and Hoogeveen there is a service disruption due to a collision with a vehicle.
    Updates will follow as more information becomes available.

More about this disruption

Statistics

This disruption started at 9:58 PM on June 13, 2017 and took 4 hours, 1 minute in total.

For statistics, this disruption is caused due to a collision with a vehicle.

Affected lines

The following lines are affected by this disruption:

Operators

This disruption affects trains operated by NS.

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

Refunds and passenger rights