Train Arriva 8078 Hardenberg – Zwolle

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

✓ Today’s run finished

Today, last fix heading to — at 20:42 +1 min

  1. Hardenberg20:10
  2. Mariënberg20:16
  3. Ommen20:22
  4. Dalfsen20:30
  5. Zwolle20:38

Next service: tomorrow 20:10 from Hardenberg · Wed 18 Nov

Next departure 20:10 tomorrow · Hardenberg
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 18 full · 1 partial · 7 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 25 full · 1 partial · 27 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

  • Mon 9 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 13 Nov Max en route +4 min · last fix heading to — +4 min
  • Wed 4 Nov Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 23
  • 3–10 min 12% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=3
  • 75% W n=4
  • 100% T n=1
  • 75% F n=4
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 26 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
20:10on time on time
20:16≈ on time ≈ +1 min
20:22 / 20:23≈ on time ≈ +1 min
20:30≈ +1 min ≈ +2 min
20:38+1 min +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
Tue 17 Nov— 20:42+1 min—
Mon 16 Nov— 20:390 min—
Sun 15 NovDalfsen 20:44+1 min+1 min
Sat 14 NovDalfsen 20:44Partial coverage+1 min+1 min
Fri 13 Nov— 20:44+4 min+4 min
Wed 11 Nov— 20:39+1 min+1 min
Tue 10 Nov— 20:42+1 min+1 min
Mon 9 Nov— 20:44+4 min+4 min
Sun 8 NovDalfsen 20:440 min—
Sat 7 NovDalfsen 20:44+1 min+1 min
Fri 6 Nov— 20:440 min—
Thu 5 Nov— 20:39No data—
Wed 4 Nov— 20:44+3 min+3 min
Mon 2 Nov— 20:43No data—
Sun 1 NovDalfsen 20:440 min—
Sat 31 OctDalfsen 20:46+1 min+1 min
Thu 29 Oct— 20:420 min—
Wed 28 Oct— 20:410 min—
Tue 27 Oct— 20:420 min—
Mon 26 OctEmmen Zuid 20:44No data—
Sun 25 OctDalfsen 20:45No data—
Sat 24 OctDalfsen 20:48No data—
Fri 23 Oct— 20:43+3 min+3 min
Thu 22 Oct— 20:48No data—
Wed 21 Oct— 20:42No data—
Mon 19 Oct— 20:420 min—
Sun 18 OctDalfsen 20:47+3 min+3 min
Sat 17 OctDalfsen 20:45No data—
Fri 16 OctDalen 20:09No data—
Thu 15 Oct— 20:40No data—