Train Blauwnet A 8026 Hardenberg – Zwolle

Hardenberg 07:10 → Zwolle 07:38 Daily 0 h 28 min · 5 stops Blauwnet A

It has not run yet today

Last recorded run: Wednesday 18 November +3 min

Next service: today 07:10 from Hardenberg · Thu 19 Nov

Next departure 07:10 today · Hardenberg
On-time · 30 days
77%
17/22 runs under 3 min
RT coverage: 17 full · 5 partial · 7 no data
On-time · 90 days
83%
29/35 runs under 3 min
RT coverage: 30 full · 5 partial · 53 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: +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

  • Sun 15 Nov Max en route +27 min · last fix heading to Dalfsen +27 min
  • Sat 7 Nov Max en route +5 min · last fix heading to Dalfsen +5 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Coevorden +4 min
  • Fri 13 Nov Max en route +3 min · last fix heading to Dalfsen +3 min
  • Wed 18 Nov Max en route +3 min · last fix heading to Dalfsen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 29
  • 3–10 min 14% · 5
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 35 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
07:10on time on time
07:16≈ on time ≈ +1 min
07:22 / 07:23≈ on time ≈ +1 min
07:30≈ on time ≈ +2 min
07:38on 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
Wed 18 NovDalfsen 07:47Partial coverage+3 min+3 min
Tue 17 NovDalfsen 07:47Partial coverage+3 min+3 min
Mon 16 NovDalfsen 07:44Partial coverage0 min—
Sun 15 NovDalfsen 08:09Partial coverage+27 min+27 min
Sat 14 NovDalfsen 07:44Partial coverage+1 min+1 min
Fri 13 NovDalfsen 07:48+3 min+3 min
Thu 12 NovCoevorden 09:44+4 min+4 min
Wed 11 NovDalfsen 07:440 min—
Tue 10 NovDalfsen 07:44+1 min—
Mon 9 NovDalfsen 07:440 min—
Sun 8 NovDalfsen 07:44+1 min+1 min
Sat 7 NovDalfsen 07:48+5 min+5 min
Fri 6 NovDalfsen 07:44No data—
Thu 5 NovDalfsen 07:49No data—
Wed 4 NovDalfsen 07:44No data—
Tue 3 NovDalfsen 07:440 min—
Mon 2 NovDalfsen 07:44No data—
Sun 1 NovDalfsen 07:44No data—
Sat 31 OctDalfsen 07:440 min—
Fri 30 OctDalfsen 07:450 min—
Thu 29 OctDalfsen 07:450 min—
Wed 28 OctDalfsen 07:450 min—
Tue 27 OctDalfsen 07:450 min—
Mon 26 OctDalfsen 07:47+3 min+3 min
Sun 25 OctDalfsen 07:45No data—
Sat 24 OctDalfsen 07:44No data—
Fri 23 OctDalfsen 07:45+1 min—
Thu 22 OctDalfsen 07:450 min—
Wed 21 OctDalfsen 07:480 min—
Tue 20 OctDalfsen 07:460 min—