Train Blauwnet A 8022 Hardenberg – Zwolle

Hardenberg 06:10 → Zwolle 06:38 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:44 0 min

  1. Hardenberg06:10
  2. Mariënberg06:16
  3. Ommen06:22
  4. Dalfsen06:30
  5. Zwolle06:38

Next service: tomorrow 06:10 from Hardenberg · Tue 17 Nov

Next departure 06:10 tomorrow · Hardenberg
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 18 full · 1 partial · 2 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 27 full · 1 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 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 9 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 96% · 27
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 80% 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
06:10on time on time
06:16≈ on time ≈ on time
06:22 / 06:23≈ on time ≈ +1 min
06:30≈ on time ≈ +1 min
06: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
Mon 16 NovDalfsen 06:44Partial coverage0 min—
Fri 13 NovDalfsen 06:44+1 min+1 min
Thu 12 NovDalfsen 06:440 min—
Wed 11 NovDalfsen 06:440 min—
Tue 10 NovDalfsen 06:44+1 min+1 min
Mon 9 NovDalfsen 06:440 min—
Fri 6 NovDalfsen 06:44No data—
Thu 5 NovDalfsen 06:440 min—
Wed 4 NovDalfsen 06:44+1 min+1 min
Tue 3 NovDalfsen 06:440 min—
Mon 2 NovDalfsen 06:44No data—
Fri 30 OctDalfsen 06:45+1 min+1 min
Thu 29 OctDalfsen 06:450 min—
Wed 28 OctDalfsen 06:45+2 min+2 min
Tue 27 OctDalfsen 06:440 min—
Mon 26 OctDalfsen 06:450 min—
Fri 23 OctDalfsen 06:440 min—
Thu 22 OctDalfsen 06:440 min—
Wed 21 OctDalfsen 06:45+1 min—
Tue 20 OctDalfsen 06:440 min—
Mon 19 OctDalfsen 06:440 min—
Fri 16 OctDalfsen 06:440 min—
Thu 15 OctDalfsen 06:450 min—
Wed 14 OctDalfsen 06:46+2 min+2 min
Tue 13 OctDalfsen 06:440 min—
Mon 12 OctDalfsen 06:440 min—
Fri 9 OctDalfsen 06:48+4 min+4 min
Thu 8 OctDalfsen 06:440 min—
Wed 7 OctDalfsen 06:48+3 min+4 min
Tue 6 OctDalfsen 06:440 min—