Train Arriva 8096 Hardenberg – Zwolle

Hardenberg 00:46 → Zwolle 01:14 Mon, Tue, Wed, Thu, Fri, Sat 0 h 28 min · 5 stops Arriva

✓ Today’s run finished

Today, last fix heading to — at 01:19 +2 min

  1. Hardenberg00:46
  2. Mariënberg00:52
  3. Ommen00:59
  4. Dalfsen01:06
  5. Zwolle01:14

Next service: tomorrow 00:46 from Hardenberg · Wed 18 Nov

Next departure 00:46 tomorrow · Hardenberg
On-time · 30 days
75%
12/16 runs under 3 min
RT coverage: 16 full · 0 partial · 4 no data
On-time · 90 days
83%
19/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Sat 14 Nov Max en route +15 min · last fix heading to — +15 min
  • Tue 3 Nov Max en route +6 min · last fix heading to — +6 min
  • Sat 7 Nov Max en route +5 min · last fix heading to — +5 min
  • Thu 5 Nov 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 83% · 19
  • 3–10 min 13% · 3
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 86% T n=7
  • 100% W n=3
  • 80% T n=5
  • 100% F n=2
  • 33% S n=3
  • 100% S n=3

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
00:46on time on time
00:52≈ on time ≈ +1 min
00:59≈ on time ≈ +2 min
01:06≈ on time ≈ +3 min
01:14on time +5 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— 01:19+2 min+2 min
Sun 15 Nov— 01:140 min—
Sat 14 Nov— 01:32+15 min+15 min
Thu 12 Nov— 01:140 min—
Wed 11 Nov— 01:090 min—
Tue 10 Nov— 01:18+1 min—
Sun 8 Nov— 01:19+1 min+1 min
Sat 7 Nov— 01:19+5 min+5 min
Fri 6 Nov— 01:19No data—
Thu 5 Nov— 01:19+3 min+3 min
Tue 3 Nov— 01:23+6 min+6 min
Fri 30 Oct— 01:170 min—
Thu 29 Oct— 01:170 min—
Wed 28 Oct— 01:160 min—
Tue 27 Oct— 01:130 min—
Sun 25 Oct— 01:16No data—
Sat 24 Oct— 01:180 min—
Fri 23 Oct— 01:19No data—
Thu 22 Oct— 01:18No data—
Tue 20 Oct— 01:18+1 min—
Sun 18 OctDalfsen 01:20No data—
Fri 16 Oct— 01:180 min—
Thu 15 Oct— 01:180 min—
Wed 14 Oct— 01:17No data—
Tue 13 Oct— 01:12+1 min—
Sun 11 Oct— 01:18+1 min+1 min
Thu 8 Oct— 01:150 min—
Wed 7 Oct— 01:140 min—
Tue 6 Oct— 01:160 min—
Sun 4 OctCoevorden 00:50No data—