Train Arriva 8074 Hardenberg – Zwolle

Hardenberg 19:10 → Zwolle 19:38 Daily 0 h 28 min · 5 stops Arriva

✓ Today’s run finished

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

  1. Hardenberg19:10
  2. Mariënberg19:16
  3. Ommen19:22
  4. Dalfsen19:30
  5. Zwolle19:38

Next service: tomorrow 19:10 from Hardenberg · Wed 18 Nov

Next departure 19:10 tomorrow · Hardenberg
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 21 full · 1 partial · 7 no data
On-time · 90 days
90%
28/31 runs under 3 min
RT coverage: 30 full · 1 partial · 36 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: +3 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

  • Sun 18 Oct Max en route +4 min · last fix heading to Dalfsen +4 min
  • Sun 15 Nov Max en route +3 min · last fix heading to Dalfsen +3 min
  • Thu 12 Nov Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 28
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 100% W n=3
  • 75% T n=4
  • 100% F n=4
  • 100% S n=4
  • 60% S n=5

Stops and timetable

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

Last 90 days, 31 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
19:10on time on time
19:16≈ on time ≈ +1 min
19:22 / 19:23≈ on time ≈ +1 min
19:30≈ on time ≈ +2 min
19:38on time +2 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— 19:43+2 min+2 min
Mon 16 Nov— 19:390 min—
Sun 15 NovDalfsen 19:48Partial coverage+3 min+3 min
Sat 14 NovDalfsen 19:440 min—
Fri 13 NovDalen 19:43+2 min+2 min
Thu 12 Nov— 19:44+3 min+3 min
Wed 11 Nov— 19:390 min—
Tue 10 Nov— 19:24+1 min+1 min
Mon 9 Nov— 19:39+1 min—
Sun 8 NovDalfsen 19:47+3 min+3 min
Sat 7 NovDalfsen 19:44+2 min+2 min
Fri 6 NovEmmen Zuid 19:540 min—
Thu 5 Nov— 19:390 min—
Wed 4 Nov— 19:39No data—
Mon 2 Nov— 19:390 min—
Sun 1 NovDalfsen 19:47+2 min+2 min
Sat 31 OctDalfsen 19:440 min—
Fri 30 OctNieuw Amsterdam 19:41No data—
Thu 29 Oct— 19:410 min—
Wed 28 Oct— 19:400 min—
Tue 27 Oct— 19:440 min—
Mon 26 Oct— 19:44No data—
Sun 25 OctDalfsen 19:45No data—
Sat 24 OctDalfsen 19:45No data—
Fri 23 OctOmmen 19:42+2 min+2 min
Thu 22 OctEmmen 18:55No data—
Wed 21 Oct— 19:43No data—
Tue 20 OctEmmen Zuid 19:410 min—
Mon 19 OctEmmen 19:420 min—
Sun 18 OctDalfsen 19:47+4 min+4 min