Train Blauwnet A 8090 Hardenberg – Zwolle

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 23:10 from Hardenberg · Mon 16 Nov

Next departure 23:10 today · Hardenberg
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 14 full · 1 partial · 10 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 22 full · 1 partial · 28 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

  • Sun 18 Oct Max en route +6 min · last fix heading to Dalfsen +6 min
  • Thu 12 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=1
  • 100% W n=4
  • 75% T n=4
  • 100% F n=2
  • 100% S n=2
  • 80% S n=5

Stops and timetable

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

Last 90 days, 23 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
23:10on time on time
23:16≈ on time ≈ +1 min
23:22 / 23:23≈ on time ≈ +1 min
23:30≈ on time ≈ +2 min
23: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
Sun 15 NovDalfsen 23:44Partial coverage0 min—
Sat 14 Nov— 23:390 min—
Thu 12 Nov— 23:44+4 min+4 min
Wed 11 Nov— 23:390 min—
Mon 9 Nov— 23:390 min—
Sun 8 NovDalfsen 23:44+1 min+1 min
Sat 7 NovMariënberg 23:240 min—
Thu 5 Nov— 23:440 min—
Wed 4 Nov— 23:43+2 min+2 min
Mon 2 Nov— 23:390 min—
Sun 1 NovDalfsen 23:44+2 min+2 min
Sat 31 OctMariënberg 23:44No data—
Fri 30 Oct— 23:42No data—
Thu 29 Oct— 23:42+1 min+1 min
Wed 28 Oct— 23:41No data—
Tue 27 Oct— 23:42No data—
Mon 26 Oct— 23:400 min—
Sun 25 OctDalfsen 23:45No data—
Sat 24 Oct— 23:43No data—
Fri 23 Oct— 23:410 min—
Thu 22 Oct— 23:41No data—
Wed 21 Oct— 23:42No data—
Tue 20 Oct— 23:45No data—
Mon 19 Oct— 23:42No data—
Sun 18 OctDalfsen 23:50+6 min+6 min
Sat 17 OctDalfsen 23:48No data—
Fri 16 Oct— 23:41No data—
Thu 15 Oct— 23:40No data—
Wed 14 Oct— 23:420 min—
Tue 13 Oct— 23:41No data—