Train Blauwnet A 8068 Hardenberg – Zwolle

Hardenberg 17:40 → Zwolle 18:08 Mon, Tue, Wed, Thu, Fri 0 h 28 min · 5 stops Blauwnet A

It has not run yet today

Last recorded run: Tuesday 17 November +2 min

Next service: today 17:40 from Hardenberg · Wed 18 Nov

Next departure 17:40 today · Hardenberg
On-time · 30 days
83%
10/12 runs under 3 min
RT coverage: 10 full · 2 partial · 9 no data
On-time · 90 days
84%
16/19 runs under 3 min
RT coverage: 17 full · 2 partial · 43 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 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

  • Mon 5 Oct Max en route +4 min · last fix heading to Dalfsen +4 min
  • Mon 9 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 Dalfsen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 16
  • 3–10 min 16% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 100% T n=4
  • 100% W n=4
  • 50% T n=2
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 19 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
17:40on time on time
17:46≈ on time ≈ +1 min
17:52 / 17:53≈ on time ≈ +2 min
18:00≈ on time ≈ +2 min
18: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
Tue 17 NovDalfsen 18:14Partial coverage+2 min+2 min
Mon 16 NovDalfsen 18:14Partial coverage0 min—
Fri 13 NovDalfsen 18:14+1 min+1 min
Thu 12 NovDalfsen 18:14+3 min+3 min
Wed 11 NovDalfsen 18:140 min—
Tue 10 NovDalfsen 18:14+2 min+2 min
Mon 9 NovDalfsen 18:14+3 min+3 min
Fri 6 NovDalfsen 18:140 min—
Thu 5 NovDalfsen 18:14No data—
Wed 4 NovDalfsen 18:140 min—
Tue 3 NovDalfsen 18:14No data—
Mon 2 NovDalfsen 18:14No data—
Fri 30 OctDalfsen 18:14No data—
Thu 29 OctDalfsen 18:14No data—
Wed 28 OctDalfsen 18:140 min—
Tue 27 OctDalfsen 18:17No data—
Mon 26 OctDalfsen 18:15+3 min+3 min
Fri 23 OctDalfsen 18:16No data—
Thu 22 OctDalfsen 18:27No data—
Wed 21 OctDalfsen 18:14No data—
Tue 20 OctDalfsen 18:140 min—
Mon 19 OctDalfsen 18:140 min—
Fri 16 OctDalfsen 18:16No data—
Thu 15 OctDalfsen 18:14No data—
Wed 14 OctDalfsen 18:15No data—
Tue 13 OctDalfsen 18:14No data—
Mon 12 OctDalfsen 18:140 min—
Fri 9 OctDalfsen 18:14+1 min+1 min
Thu 8 OctDalfsen 18:14+2 min+2 min
Wed 7 OctDalfsen 18:140 min—