Train Blauwnet A 13826 Hardenberg – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Dalfsen at 07:59 +4 min

  1. Hardenberg07:26
  2. Ommen07:36
  3. Dalfsen07:45
  4. Zwolle07:53

Next service: Monday 07:26 from Hardenberg · Mon 23 Nov

Next departure 07:26 Monday · Hardenberg
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 14 full · 5 partial · 3 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 21 full · 5 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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 20 Nov Max en route +4 min · last fix heading to Dalfsen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=6
  • 100% W n=6
  • 100% T n=5
  • 80% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 26 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:26on time on time
07:36 / 07:38≈ on time ≈ on time
07:45≈ on time ≈ +1 min
07:53on time +1 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
Fri 20 NovDalfsen 07:59Partial coverage+4 min+4 min
Thu 19 NovDalfsen 07:59Partial coverage0 min+1 min
Wed 18 NovDalfsen 07:59Partial coverage0 min—
Tue 17 NovDalfsen 07:59Partial coverage0 min—
Mon 16 NovDalfsen 07:59Partial coverage0 min—
Fri 13 NovDalfsen 07:590 min—
Thu 12 NovDalfsen 07:59+1 min+1 min
Wed 11 NovDalfsen 07:590 min—
Tue 10 NovDalfsen 07:590 min—
Mon 9 NovDalfsen 07:59+1 min+1 min
Fri 6 NovDalfsen 07:59No data—
Thu 5 NovDalfsen 08:02No data—
Wed 4 NovDalfsen 07:590 min—
Tue 3 NovDalfsen 07:590 min—
Mon 2 NovDalfsen 07:59No data—
Fri 30 OctDalfsen 07:590 min—
Thu 29 OctDalfsen 08:00+1 min—
Wed 28 OctDalfsen 07:590 min—
Tue 27 OctDalfsen 07:590 min—
Mon 26 OctDalfsen 08:01+1 min+1 min
Fri 23 OctDalfsen 07:590 min—
Thu 22 OctDalfsen 07:590 min—
Wed 21 OctDalfsen 08:010 min—
Tue 20 OctDalfsen 08:010 min—
Mon 19 OctDalfsen 07:590 min—
Fri 9 OctDalfsen 08:000 min+1 min
Thu 8 OctDalfsen 07:590 min—
Wed 7 OctDalfsen 08:000 min—
Tue 6 OctDalfsen 07:590 min—
Mon 5 OctDalfsen 08:01No data—