Train Arriva 3888 Hardenberg – Zwolle

Hardenberg 22:40 → Zwolle 23:08 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:40 from Hardenberg · Tue 17 Nov

Next departure 22:40 today · Hardenberg
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 15 full · 0 partial · 7 no data
On-time · 90 days
86%
19/22 runs under 3 min
RT coverage: 22 full · 0 partial · 17 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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 13 Nov Max en route +8 min · last fix heading to — +8 min
  • Fri 6 Nov Max en route +5 min · last fix heading to — +5 min
  • Fri 9 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 19
  • 3–10 min 14% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=3
  • 100% W n=4
  • 100% T n=1
  • 25% F n=4
  • 100% S n=3
  • 100% S n=1

Stops and timetable

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

Last 90 days, 22 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:40on time on time
22:46≈ on time ≈ +1 min
22:52 / 22:53≈ +1 min ≈ +1 min
23:00≈ +1 min ≈ +2 min
23:08+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
Mon 16 Nov— 23:120 min—
Sun 15 NovDalfsen 23:140 min—
Sat 14 NovDalfsen 23:140 min—
Fri 13 Nov— 23:19+8 min+8 min
Wed 11 Nov— 23:090 min—
Tue 10 Nov— 23:13+2 min+2 min
Mon 9 Nov— 23:090 min—
Sat 7 NovDalfsen 23:14+2 min+2 min
Fri 6 Nov— 23:14+5 min+5 min
Thu 5 Nov— 23:13No data—
Wed 4 Nov— 23:13+2 min+2 min
Mon 2 Nov— 23:14+3 min+3 min
Sat 31 OctDalfsen 23:16No data—
Thu 29 Oct— 23:110 min—
Wed 28 Oct— 23:12No data—
Tue 27 Oct— 23:130 min—
Mon 26 Oct— 23:12No data—
Sat 24 OctCoevorden 23:13No data—
Fri 23 Oct— 23:13+2 min+2 min
Thu 22 Oct— 23:15No data—
Wed 21 Oct— 23:13No data—
Mon 19 Oct— 23:130 min—
Sat 17 OctDalfsen 23:18No data—
Thu 15 Oct— 23:13No data—
Wed 14 Oct— 23:12+1 min—
Tue 13 Oct— 23:12No data—
Mon 12 Oct— 23:12+1 min+1 min
Sat 10 Oct— 23:13+1 min+1 min
Fri 9 Oct— 23:14+3 min+3 min
Wed 7 Oct— 23:110 min—