Train Blauwnet A 3836 Hardenberg – Zwolle

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

It has not run yet today

Last recorded run: Tuesday 17 November +5 min

Next service: today 09:40 from Hardenberg · Wed 18 Nov

Next departure 09:40 today · Hardenberg
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 16 full · 2 partial · 11 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 25 full · 2 partial · 61 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: +3 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 +13 min · last fix heading to Dalfsen +13 min
  • Tue 17 Nov Max en route +5 min · last fix heading to Dalfsen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 25
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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