Train Blauwnet A 3880 Hardenberg – Zwolle

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

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 20:40 from Hardenberg · Sun 15 Nov

Next departure 20:40 today · Hardenberg
On-time · 30 days
80%
12/15 runs under 3 min
RT coverage: 14 full · 1 partial · 7 no data
On-time · 90 days
87%
20/23 runs under 3 min
RT coverage: 22 full · 1 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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 +8 min · last fix heading to — +8 min
  • Mon 9 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 23 Oct 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 87% · 20
  • 3–10 min 13% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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