Train Blauwnet A 8028 Hardenberg – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Dalfsen at 08:14 +1 min

  1. Hardenberg07:40
  2. Mariënberg07:46
  3. Ommen07:52
  4. Dalfsen08:00
  5. Zwolle08:08

Next service: tomorrow 07:40 from Hardenberg · Wed 18 Nov

Next departure 07:40 tomorrow · Hardenberg
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 17 full · 2 partial · 3 no data
On-time · 90 days
82%
23/28 runs under 3 min
RT coverage: 26 full · 2 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Fri 13 Nov Max en route +6 min · last fix heading to Dalfsen +6 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Dalfsen +4 min
  • Wed 7 Oct Max en route +4 min · last fix heading to Dalfsen +4 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Dalfsen +4 min
  • Mon 26 Oct Max en route +4 min · last fix heading to Dalfsen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 23
  • 3–10 min 18% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 86% T n=7
  • 83% W n=6
  • 100% T n=5
  • 60% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

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