Train Blauwnet A 8042 Hardenberg – Zwolle

Hardenberg 11:10 → Zwolle 11:38 Daily 0 h 28 min · 5 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Dalfsen at 11:44 0 min

  1. Hardenberg11:10
  2. Mariënberg11:16
  3. Ommen11:22
  4. Dalfsen11:30
  5. Zwolle11:38

Next service: tomorrow 11:10 from Hardenberg · Thu 19 Nov

Next departure 11:10 tomorrow · Hardenberg
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 15 full · 3 partial · 12 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 21 full · 3 partial · 65 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 24
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
11:10on time on time
11:16≈ on time ≈ on time
11:22 / 11:23≈ on time ≈ +1 min
11:30≈ on time ≈ +1 min
11:38on 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
Wed 18 NovDalfsen 11:44Partial coverage0 min—
Tue 17 NovDalfsen 11:44Partial coverage+1 min—
Mon 16 NovDalfsen 11:44Partial coverage0 min—
Sun 15 NovDalfsen 11:450 min—
Sat 14 NovDalfsen 11:440 min—
Fri 13 NovDalfsen 11:440 min—
Thu 12 NovDalfsen 11:440 min—
Wed 11 NovDalfsen 11:440 min—
Tue 10 NovDalfsen 11:44+1 min+2 min
Mon 9 NovDalfsen 11:440 min—
Sun 8 NovDalfsen 11:44No data—
Sat 7 NovDalfsen 11:44+1 min+1 min
Fri 6 NovDalfsen 11:44No data—
Thu 5 NovDalfsen 11:44No data—
Wed 4 NovDalfsen 11:44+2 min+2 min
Tue 3 NovDalfsen 11:44No data—
Mon 2 NovDalfsen 11:44No data—
Sun 1 NovDalfsen 11:450 min—
Sat 31 OctDalfsen 11:440 min—
Fri 30 OctDalfsen 11:45No data—
Thu 29 OctDalfsen 11:440 min—
Wed 28 OctDalfsen 11:450 min—
Tue 27 OctDalfsen 11:44No data—
Mon 26 OctDalfsen 11:44No data—
Sun 25 OctDalfsen 11:45No data—
Sat 24 OctDalfsen 11:440 min—
Fri 23 OctDalfsen 11:45No data—
Thu 22 OctDalfsen 11:45No data—
Wed 21 OctDalfsen 11:44No data—
Tue 20 OctDalfsen 11:440 min—