Train Blauwnet A 3860 Hardenberg – Zwolle

Hardenberg 15:40 → Zwolle 16:08 Daily 0 h 28 min · 5 stops Blauwnet A

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 15:40 from Hardenberg · Tue 17 Nov

Next departure 15:40 today · Hardenberg
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 15 full · 2 partial · 12 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 24 full · 2 partial · 62 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: +2 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 12 Nov Max en route +6 min · last fix heading to Dalfsen +6 min
  • Sun 11 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
  • 100% T n=4
  • 100% W n=3
  • 50% T n=2
  • 100% F n=2
  • 100% S n=5
  • 80% S n=5

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