Train Blauwnet A 13828 Hardenberg – Zwolle

Hardenberg 07:56 → Zwolle 08:23 Mon, Tue, Wed, Thu, Fri 0 h 27 min · 4 stops Blauwnet A

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 07:56 from Hardenberg · Wed 18 Nov

Next departure 07:56 today · Hardenberg
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 12 full · 2 partial · 7 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 17 full · 2 partial · 38 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: +1 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

  • Fri 9 Oct Max en route +5 min · last fix heading to Dalfsen +5 min
  • Fri 13 Nov Max en route +3 min · last fix heading to Dalfsen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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
07:56on time on time
08:06 / 08:08≈ on time ≈ +1 min
08:15≈ on time ≈ +2 min
08:23on 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
Tue 17 NovDalfsen 08:29Partial coverage0 min—
Mon 16 NovDalfsen 08:29Partial coverage0 min—
Fri 13 NovDalfsen 08:32+3 min+3 min
Thu 12 NovDalfsen 08:290 min—
Wed 11 NovDalfsen 08:290 min—
Tue 10 NovDalfsen 08:29+1 min+2 min
Mon 9 NovDalfsen 08:29No data—
Fri 6 NovDalfsen 08:34No data—
Thu 5 NovDalfsen 08:32No data—
Wed 4 NovDalfsen 08:290 min—
Tue 3 NovDalfsen 08:29No data—
Mon 2 NovDalfsen 08:29No data—
Fri 30 OctDalfsen 08:290 min—
Thu 29 OctDalfsen 08:290 min—
Wed 28 OctDalfsen 08:300 min—
Tue 27 OctDalfsen 08:290 min—
Mon 26 OctDalfsen 08:32+1 min—
Fri 23 OctDalfsen 08:310 min—
Thu 22 OctDalfsen 08:30No data—
Wed 21 OctDalfsen 08:32No data—
Tue 20 OctDalfsen 08:310 min—
Mon 19 OctDalfsen 08:300 min—
Fri 9 OctDalfsen 08:34+5 min+5 min
Thu 8 OctDalfsen 08:30+1 min+1 min
Wed 7 OctDalfsen 08:31+2 min+2 min
Tue 6 OctDalfsen 08:290 min—
Mon 5 OctDalfsen 08:31No data—
Fri 2 OctDalfsen 08:31No data—
Thu 1 OctDalfsen 08:29No data—
Wed 30 SeptDalfsen 08:32No data—