Train Blauwnet A 13853 Zwolle – Hardenberg

Zwolle 17:09 → Hardenberg 17:34 Mon, Tue, Wed, Thu, Fri 0 h 25 min · 4 stops Blauwnet A

It has not run yet today

Last recorded run: Tuesday 17 November +3 min

Next service: today 17:09 from Zwolle · Wed 18 Nov

Next departure 17:09 today · Zwolle
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 9 full · 2 partial · 10 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 14 full · 2 partial · 41 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Tue 17 Nov Max en route +3 min · last fix heading to Ommen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 75% T n=4
  • 100% W n=3
  • 100% T n=2
  • 100% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 16 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
17:09on time on time
17:16≈ on time ≈ +1 min
17:22 / 17:23≈ on time ≈ +1 min
17:34+1 min +3 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 NovOmmen 17:39Partial coverage+3 min+3 min
Mon 16 NovOmmen 17:38Partial coverage0 min—
Fri 13 NovEmmen Zuid 18:07+2 min+2 min
Thu 12 NovEmmen Zuid 18:07+3 min+3 min
Wed 11 NovEmmen Zuid 18:07+2 min+2 min
Tue 10 NovEmmen Zuid 18:070 min+1 min
Mon 9 NovEmmen Zuid 18:07+1 min+1 min
Fri 6 NovEmmen Zuid 18:08No data—
Thu 5 NovEmmen Zuid 18:07No data—
Wed 4 NovEmmen Zuid 18:070 min—
Tue 3 NovEmmen Zuid 18:07No data—
Mon 2 NovEmmen Zuid 18:07No data—
Fri 30 OctEmmen Zuid 18:07No data—
Thu 29 OctEmmen Zuid 18:07No data—
Wed 28 OctEmmen Zuid 18:070 min—
Tue 27 OctEmmen Zuid 18:07No data—
Mon 26 OctEmmen Zuid 18:07+3 min+3 min
Fri 23 OctEmmen Zuid 18:09No data—
Thu 22 OctEmmen Zuid 18:07No data—
Wed 21 OctEmmen Zuid 18:07No data—
Tue 20 OctEmmen Zuid 18:070 min—
Mon 19 OctEmmen Zuid 18:070 min—
Fri 9 OctEmmen Zuid 18:070 min—
Thu 8 OctEmmen Zuid 18:08+1 min+2 min
Wed 7 OctEmmen Zuid 18:07No data—
Tue 6 OctEmmen Zuid 18:07+1 min—
Mon 5 OctEmmen Zuid 18:07+1 min+1 min
Fri 2 OctEmmen Zuid 18:07No data—
Thu 1 OctEmmen Zuid 18:08No data—
Wed 30 SeptEmmen Zuid 18:07No data—