Train Arriva 8086 Hardenberg – Zwolle

Hardenberg 22:10 → Zwolle 22:38 Daily 0 h 28 min · 5 stops Arriva

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 22:10 from Hardenberg · Tue 17 Nov

Next departure 22:10 today · Hardenberg
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 17 full · 0 partial · 10 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 23 full · 0 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Zwolle, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 12 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 23 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

23 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=1
  • 50% T n=2
  • 67% F n=3
  • 100% S n=3
  • 100% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 stops).

Last 90 days, 23 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.

StopSched.Usually 9 days in 10
22:10on time on time
22:16≈ on time ≈ +1 min
22:22 / 22:23≈ on time ≈ +1 min
22:30≈ on time ≈ +2 min
22:38on time +3 min

Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 11 July 2026.

Will I make my connection?

Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.

Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.

Recent runs

DateLast stopFinalMax
Mon 16 Nov— 22:390 min—
Sun 15 NovDalfsen 22:440 min—
Sat 14 NovDalfsen 22:440 min—
Thu 12 Nov— 22:44+4 min+4 min
Wed 11 Nov— 22:390 min—
Tue 10 Nov— 22:390 min—
Mon 9 Nov— 22:43+2 min+2 min
Sun 8 NovDalfsen 22:440 min—
Sat 7 NovDalfsen 22:440 min—
Fri 6 Nov— 22:44+3 min+3 min
Thu 5 Nov— 22:43No data—
Tue 3 Nov— 22:45No data—
Mon 2 Nov— 22:42+2 min+2 min
Sun 1 NovDalfsen 22:440 min—
Sat 31 OctDalfsen 22:44No data—
Fri 30 Oct— 22:42No data—
Thu 29 Oct— 22:420 min—
Wed 28 Oct— 22:42No data—
Tue 27 Oct— 22:450 min—
Mon 26 Oct— 22:42No data—
Sun 25 OctDalfsen 22:44No data—
Sat 24 OctDalfsen 22:45No data—
Fri 23 Oct— 22:45+3 min+3 min
Thu 22 Oct— 22:44No data—
Wed 21 Oct— 22:42No data—
Tue 20 Oct— 22:430 min—
Mon 19 Oct— 22:420 min—
Sun 18 OctDalfsen 22:46+1 min+1 min
Sat 17 OctDalfsen 22:45No data—
Wed 14 Oct— 22:40No data—