Train Blauwnet A 8020 Hardenberg – Zwolle

Hardenberg 05:40 → Zwolle 06: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 06:14 +2 min

  1. Hardenberg05:40
  2. Mariënberg05:46
  3. Ommen05:52
  4. Dalfsen06:00
  5. Zwolle06:08

Next service: tomorrow 05:40 from Hardenberg · Tue 17 Nov

Next departure 05:40 tomorrow · Hardenberg
On-time · 30 days
79%
15/19 runs under 3 min
RT coverage: 18 full · 1 partial · 2 no data
On-time · 90 days
86%
24/28 runs under 3 min
RT coverage: 27 full · 1 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 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

  • Thu 29 Oct Max en route +7 min · last fix heading to Dalfsen +7 min
  • Mon 26 Oct Max en route +4 min · last fix heading to Dalfsen +4 min
  • Tue 3 Nov Max en route +4 min · last fix heading to Dalfsen +4 min
  • Thu 12 Nov Max en route +3 min · last fix heading to Dalfsen +3 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 86% · 24
  • 3–10 min 14% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 83% T n=6
  • 100% W n=6
  • 67% T n=6
  • 100% 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
05:40on time on time
05:46≈ on time ≈ +1 min
05:52 / 05:53≈ on time ≈ +1 min
06:00≈ on time ≈ +2 min
06:08on 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
Mon 16 NovDalfsen 06:14Partial coverage+2 min+2 min
Fri 13 NovDalfsen 06:14+1 min+1 min
Thu 12 NovDalfsen 06:18+3 min+3 min
Wed 11 NovDalfsen 06:140 min—
Tue 10 NovDalfsen 06:15+1 min+1 min
Mon 9 NovDalfsen 06:14+2 min+2 min
Fri 6 NovDalfsen 06:14No data—
Thu 5 NovDalfsen 06:17+3 min+3 min
Wed 4 NovDalfsen 06:140 min—
Tue 3 NovDalfsen 06:17+4 min+4 min
Mon 2 NovDalfsen 06:14No data—
Fri 30 OctDalfsen 06:16+2 min+2 min
Thu 29 OctDalfsen 06:20+7 min+7 min
Wed 28 OctDalfsen 06:150 min—
Tue 27 OctDalfsen 06:150 min—
Mon 26 OctDalfsen 06:17+4 min+4 min
Fri 23 OctDalfsen 06:140 min—
Thu 22 OctDalfsen 06:140 min—
Wed 21 OctDalfsen 06:140 min—
Tue 20 OctDalfsen 06:140 min—
Mon 19 OctDalfsen 06:140 min—
Fri 16 OctDalfsen 06:140 min—
Thu 15 OctDalfsen 06:140 min—
Wed 14 OctDalfsen 06:140 min—
Tue 13 OctDalfsen 06:16+2 min+2 min
Mon 12 OctDalfsen 06:140 min—
Fri 9 OctDalfsen 06:15+2 min+2 min
Thu 8 OctDalfsen 06:140 min—
Wed 7 OctDalfsen 06:15+1 min+1 min
Tue 6 OctDalfsen 06:140 min—