Train Blauwnet A 3884 Hardenberg – Zwolle

Hardenberg 21:40 → Zwolle 22:08 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 21:40 from Hardenberg · Mon 16 Nov

Next departure 21:40 today · Hardenberg
On-time · 30 days
68%
13/19 runs under 3 min
RT coverage: 17 full · 2 partial · 7 no data
On-time · 90 days
68%
19/28 runs under 3 min
RT coverage: 26 full · 2 partial · 25 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +5 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 +16 min · last fix heading to — +16 min
  • Tue 6 Oct Max en route +14 min · last fix heading to — +14 min
  • Fri 6 Nov Max en route +8 min · last fix heading to — +8 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Dalfsen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 68% · 19
  • 3–10 min 25% · 7
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 67% T n=3
  • 100% W n=4
  • 67% T n=3
  • 20% F n=5
  • 100% S n=3
  • 40% S n=5

Stops and timetable

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

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