Train Arriva 3867 Zwolle – Hardenberg

Zwolle 20:22 → Hardenberg 20:49 Daily 0 h 27 min · 5 stops Arriva

It has not run yet today

Last recorded run: Monday 16 November +1 min

Next service: today 20:22 from Zwolle · Tue 17 Nov

Next departure 20:22 today · Zwolle
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 18 full · 0 partial · 7 no data
On-time · 90 days
92%
22/24 runs under 3 min
RT coverage: 24 full · 0 partial · 25 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 Hardenberg, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 8 Nov Max en route +3 min · last fix heading to Emmen Zuid +3 min
  • Fri 23 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 22
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=2
  • 100% T n=2
  • 67% F n=3
  • 100% S n=4
  • 80% S n=5

Stops and timetable

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

Last 90 days, 24 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:22on time on time
20:29 / 20:30≈ on time ≈ +1 min
20:36 / 20:37≈ +1 min ≈ +2 min
20:44≈ +1 min ≈ +2 min
20:49+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— 20:53+1 min+1 min
Sun 15 NovMariënberg 20:59+1 min+1 min
Sat 14 NovMariënberg 20:59+1 min+1 min
Thu 12 Nov— 21:19+2 min+2 min
Wed 11 Nov— 21:170 min—
Tue 10 Nov— 21:190 min—
Mon 9 Nov— 21:19+2 min+2 min
Sun 8 NovEmmen Zuid 21:28+3 min+3 min
Sat 7 NovEmmen Zuid 21:24+1 min+1 min
Fri 6 Nov— 21:18+3 min+3 min
Thu 5 Nov— 21:19No data—
Sun 1 NovEmmen Zuid 21:240 min—
Sat 31 OctEmmen Zuid 21:260 min—
Fri 30 Oct— 21:20No data—
Thu 29 Oct— 21:180 min—
Wed 28 Oct— 21:180 min—
Tue 27 Oct— 21:190 min—
Mon 26 Oct— 21:19No data—
Sun 25 OctEmmen Zuid 21:25No data—
Sat 24 OctEmmen Zuid 21:25No data—
Fri 23 Oct— 21:21+3 min+3 min
Thu 22 Oct— 21:27No data—
Wed 21 Oct— 21:19No data—
Tue 20 Oct— 21:180 min—
Mon 19 Oct— 21:190 min—
Sun 18 OctEmmen Zuid 21:28+3 min+3 min
Sat 17 OctEmmen Zuid 21:25No data—
Wed 14 Oct— 21:19No data—
Tue 13 Oct— 21:19No data—
Mon 12 Oct— 21:190 min—