Train Arriva 8083 Zwolle – Hardenberg

Zwolle 00:22 → Hardenberg 00:49 Mon, Tue, Wed, Thu, Fri, Sat 0 h 27 min · 5 stops Arriva

✓ Today’s run finished

Today, last fix heading to — at 00:54 +3 min

  1. Zwolle00:22
  2. Dalfsen00:29
  3. Ommen00:36
  4. Mariënberg00:44
  5. Hardenberg00:49

Next service: tomorrow 00:22 from Zwolle · Wed 18 Nov

Next departure 00:22 tomorrow · Zwolle
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 14 full · 0 partial · 6 no data
On-time · 90 days
77%
17/22 runs under 3 min
RT coverage: 22 full · 0 partial · 9 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
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

  • Sat 7 Nov Max en route +7 min · last fix heading to — +7 min
  • Fri 9 Oct Max en route +4 min · last fix heading to — +4 min
  • Sat 24 Oct Max en route +4 min · last fix heading to — +4 min
  • Sat 17 Oct Max en route +4 min · last fix heading to — +4 min
  • Tue 13 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 77% · 17
  • 3–10 min 23% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 83% T n=6
  • 100% W n=1
  • 100% T n=2
  • 75% F n=4
  • 40% S n=5
  • 100% S n=3

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
00:22on time on time
00:29 / 00:30≈ on time ≈ +1 min
00:36 / 00:37≈ +1 min ≈ +2 min
00:44≈ +1 min ≈ +3 min
00:49+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
Tue 17 Nov— 00:54+3 min+3 min
Sun 15 Nov— 00:54+2 min+2 min
Sat 14 Nov— 01:24+3 min+4 min
Fri 13 Nov— 01:240 min—
Thu 12 Nov— 01:220 min—
Tue 10 Nov— 01:22+2 min+2 min
Sun 8 Nov— 01:190 min—
Sat 7 Nov— 01:28+7 min+7 min
Fri 6 Nov— 01:24No data—
Tue 3 Nov— 01:19+2 min+2 min
Sun 1 Nov— 01:22No data—
Sat 31 Oct— 01:22No data—
Fri 30 Oct— 01:180 min—
Wed 28 Oct— 01:300 min—
Tue 27 Oct— 01:220 min—
Sun 25 Oct— 01:26No data—
Sat 24 Oct— 01:25+4 min+4 min
Fri 23 Oct— 01:22No data—
Wed 21 Oct— 01:22No data—
Tue 20 Oct— 01:22+1 min+1 min
Sun 18 OctEmmen Zuid 01:27No data—
Sat 17 Oct— 01:25+4 min+4 min
Fri 16 Oct— 01:220 min—
Wed 14 Oct— 01:19No data—
Tue 13 Oct— 01:24+3 min+3 min
Sun 11 Oct— 01:23+1 min+1 min
Sat 10 Oct— 01:22+1 min—
Fri 9 Oct— 01:25+4 min+4 min
Thu 8 Oct— 01:220 min—
Mon 5 Oct— 01:210 min—