Train Arriva 8092 Hardenberg – Zwolle

Hardenberg 23:40 → Zwolle 00:12 Mon, Tue, Wed, Thu, Fri, Sat 0 h 32 min · 5 stops Arriva

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 23:40 from Hardenberg · Mon 16 Nov

Next departure 23:40 today · Hardenberg
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 14 full · 0 partial · 5 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 19 full · 0 partial · 13 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: +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

  • Fri 13 Nov Max en route +6 min · last fix heading to — +6 min
  • Thu 12 Nov Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=1
  • 100% W n=1
  • 67% T n=3
  • 80% F n=5
  • 100% S n=3
  • — S n=0

Stops and timetable

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

Last 90 days, 19 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
23:40on time on time
23:46≈ on time ≈ +1 min
23:55≈ on time ≈ +2 min
00:02≈ on time ≈ +2 min
00:12on 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
Sat 14 Nov— 00:130 min—
Fri 13 Nov— 00:19+6 min+6 min
Thu 12 Nov— 00:19+5 min+6 min
Wed 11 Nov— 00:130 min—
Mon 9 Nov— 00:120 min—
Sat 7 NovEmmen Zuid 00:140 min—
Fri 6 Nov— 00:18+3 min+4 min
Thu 5 Nov— 00:190 min—
Mon 2 Nov— 00:17+2 min+3 min
Sat 31 OctEmmen Zuid 00:16No data—
Fri 30 Oct— 00:14No data—
Thu 29 Oct— 00:140 min—
Tue 27 Oct— 00:150 min—
Mon 26 Oct— 00:120 min—
Sat 24 Oct— 00:19No data—
Fri 23 Oct— 00:14+1 min—
Thu 22 Oct— 00:15No data—
Tue 20 Oct— 00:17No data—
Mon 19 Oct— 00:130 min—
Sat 17 OctDalfsen 00:21No data—
Fri 16 Oct— 00:150 min+2 min
Thu 15 Oct— 00:16No data—
Tue 13 Oct— 00:14No data—
Mon 12 Oct— 00:150 min+1 min
Sat 10 Oct— 00:140 min—
Fri 9 Oct— 00:130 min—
Wed 7 Oct— 00:13No data—
Mon 5 Oct— 00:140 min—
Sat 3 OctDalfsen 00:16No data—
Sat 26 SeptHardenberg 23:57No data—