Train Blauwnet A 3832 Hardenberg – Zwolle

Hardenberg 08:40 → Zwolle 09:08 Daily 0 h 28 min · 5 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Dalfsen at 09:14 +3 min

  1. Hardenberg08:40
  2. Mariënberg08:46
  3. Ommen08:52
  4. Dalfsen09:00
  5. Zwolle09:08

Next service: tomorrow 08:40 from Hardenberg · Wed 18 Nov

Next departure 08:40 tomorrow · Hardenberg
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 14 full · 4 partial · 12 no data
On-time · 90 days
85%
22/26 runs under 3 min
RT coverage: 22 full · 4 partial · 63 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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 +4 min · last fix heading to Dalfsen +4 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Dalfsen +3 min
  • Tue 10 Nov Max en route +3 min · last fix heading to Dalfsen +3 min
  • Fri 13 Nov Max en route +3 min · last fix heading to Dalfsen +3 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 85% · 22
  • 3–10 min 15% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
08:40on time on time
08:46≈ on time ≈ +1 min
08:52 / 08:53≈ on time ≈ +1 min
09:00≈ on time ≈ +2 min
09:08on time +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 NovDalfsen 09:14Partial coverage+3 min+3 min
Mon 16 NovDalfsen 09:14Partial coverage+2 min+2 min
Sun 15 NovDalfsen 09:14Partial coverage0 min—
Sat 14 NovDalfsen 09:14Partial coverage+1 min—
Fri 13 NovDalfsen 09:18+3 min+3 min
Thu 12 NovDalfsen 09:140 min—
Wed 11 NovDalfsen 09:140 min—
Tue 10 NovDalfsen 09:17+3 min+3 min
Mon 9 NovDalfsen 09:140 min—
Sun 8 NovDalfsen 09:14No data—
Sat 7 NovDalfsen 09:14+1 min+1 min
Fri 6 NovDalfsen 09:24No data—
Thu 5 NovDalfsen 09:17No data—
Wed 4 NovDalfsen 09:17+3 min+3 min
Tue 3 NovDalfsen 09:14No data—
Mon 2 NovDalfsen 09:14No data—
Sun 1 NovDalfsen 09:140 min—
Sat 31 OctDalfsen 09:140 min—
Fri 30 OctDalfsen 09:17No data—
Thu 29 OctDalfsen 09:15No data—
Wed 28 OctDalfsen 09:140 min—
Tue 27 OctDalfsen 09:150 min—
Mon 26 OctDalfsen 09:16No data—
Sun 25 OctDalfsen 09:18No data—
Sat 24 OctDalfsen 09:150 min—
Fri 23 OctDalfsen 09:15No data—
Thu 22 OctDalfsen 09:15No data—
Wed 21 OctDalfsen 09:18No data—
Tue 20 OctDalfsen 09:160 min—
Mon 19 OctDalfsen 09:160 min—