Train Arriva 8072 Hardenberg – Zwolle

Hardenberg 18:40 → Zwolle 19:08 Mon, Tue, Wed, Thu, Fri 0 h 28 min · 5 stops Arriva

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 18:40 from Hardenberg · Tue 17 Nov

Next departure 18:40 today · Hardenberg
On-time · 30 days
71%
10/14 runs under 3 min
RT coverage: 14 full · 0 partial · 7 no data
On-time · 90 days
78%
14/18 runs under 3 min
RT coverage: 18 full · 0 partial · 29 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Fri 23 Oct Max en route +5 min · last fix heading to Dalfsen +5 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Ommen +5 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Nieuw Amsterdam +4 min
  • Mon 9 Nov Max en route +3 min · last fix heading to Emmen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 14
  • 3–10 min 22% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=3
  • 100% W n=3
  • 50% T n=2
  • 50% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 18 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
18:40on time on time
18:46≈ on time ≈ +1 min
18:52 / 18:53≈ on time ≈ +2 min
19:00≈ on time ≈ +3 min
19:08+1 min +4 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— 19:090 min—
Fri 13 NovOmmen 19:14+5 min+5 min
Thu 12 NovNieuw Amsterdam 19:14+4 min+4 min
Wed 11 NovEmmen 19:09+1 min+1 min
Tue 10 NovNieuw Amsterdam 18:340 min—
Mon 9 NovEmmen 19:14+3 min+3 min
Fri 6 NovMariënberg 19:340 min—
Thu 5 NovEmmen 19:12No data—
Wed 4 NovEmmen 19:14No data—
Tue 3 NovEmmen 18:24No data—
Mon 2 Nov— 19:13+2 min+2 min
Fri 30 OctOmmen 19:14No data—
Thu 29 Oct— 19:11+1 min—
Wed 28 OctEmmen 18:250 min—
Tue 27 Oct— 19:140 min—
Mon 26 Oct— 19:15No data—
Fri 23 OctDalfsen 19:16+5 min+5 min
Thu 22 OctHardenberg 19:16No data—
Wed 21 OctHardenberg 18:54No data—
Tue 20 OctMariënberg 19:110 min—
Mon 19 OctHardenberg 19:100 min—
Fri 16 OctDalfsen 19:14No data—
Thu 15 OctCoevorden 19:12No data—
Wed 14 OctDalfsen 19:12No data—
Tue 13 OctHardenberg 19:11No data—
Mon 12 OctHardenberg 19:130 min—
Fri 9 OctGramsbergen 19:110 min—
Wed 7 Oct— 19:12+1 min+1 min
Mon 5 OctEmmen 19:13+2 min+2 min
Fri 2 OctMariënberg 19:00No data—