Train Blauwnet A 3863 Zwolle – Hardenberg

Zwolle 19:22 → Hardenberg 19:49 Daily 0 h 27 min · 5 stops Blauwnet A

It has not run yet today

Last recorded run: Sunday 15 November +4 min

Next service: today 19:22 from Zwolle · Mon 16 Nov

Next departure 19:22 today · Zwolle
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 16 full · 1 partial · 8 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 22 full · 1 partial · 30 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 Hardenberg, 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 15 Nov Max en route +4 min · last fix heading to Mariënberg +4 min
  • Thu 12 Nov Max en route +3 min · last fix heading to — +3 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=4
  • 100% T n=3
  • 100% W n=3
  • 50% T n=2
  • 100% F n=3
  • 100% S n=4
  • 75% 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
19:22on time on time
19:29 / 19:30≈ on time ≈ on time
19:36 / 19:37≈ on time ≈ +1 min
19:44≈ on time ≈ +1 min
19:49on 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 NovMariënberg 20:02Partial coverage+4 min+4 min
Sat 14 NovMariënberg 19:580 min—
Fri 13 Nov— 20:19+2 min+2 min
Thu 12 Nov— 20:19+3 min+3 min
Wed 11 Nov— 20:140 min—
Tue 10 Nov— 19:240 min—
Mon 9 Nov— 20:190 min—
Sun 8 NovEmmen Zuid 20:24No data—
Sat 7 NovEmmen Zuid 20:24+1 min+1 min
Thu 5 Nov— 20:18No data—
Wed 4 Nov— 19:140 min—
Mon 2 Nov— 20:18No data—
Sun 1 NovEmmen Zuid 20:240 min+1 min
Sat 31 OctEmmen Zuid 20:26+1 min+1 min
Fri 30 Oct— 20:20No data—
Thu 29 Oct— 20:170 min—
Tue 27 Oct— 20:180 min—
Mon 26 OctMariënberg 20:20No data—
Sun 25 OctEmmen Zuid 20:26No data—
Sat 24 OctEmmen Zuid 20:25No data—
Fri 23 OctZwolle 20:180 min—
Thu 22 Oct— 20:26No data—
Tue 20 Oct— 20:190 min—
Mon 19 Oct— 20:170 min—
Sun 18 OctEmmen Zuid 20:260 min+2 min
Sat 17 OctEmmen Zuid 20:25No data—
Fri 16 OctHardenberg 20:19No data—
Thu 15 Oct— 20:19No data—
Wed 14 OctMariënberg 20:14No data—
Tue 13 Oct— 20:19No data—