Train Blauwnet A 8054 Hardenberg – Zwolle

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

Running now · updated 14:13

Position estimated from the timetable

Heading to Zwolle +3 min

Estimated arrival at Zwolle 14:41 14:38 · 80 km/h

  1. Hardenberg14:10
  2. Mariënberg14:16
  3. Ommen14:22
  4. Dalfsen14:30
  5. Zwolle14:38

Today it is running worse than usual: typical arrival delay is 0 min; 100% of the last 19 runs arrived on time.

On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 17 full · 2 partial · 11 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 24 full · 2 partial · 63 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

  • Thu 8 Oct Max en route +6 min · last fix heading to Dalfsen +6 min
  • Tue 6 Oct Max en route +3 min · last fix heading to Dalfsen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 24
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 75% T n=4
  • 100% W n=4
  • 67% T n=3
  • 100% F n=2
  • 100% S n=5
  • 100% S n=3

Stops and timetable

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

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