Train Blauwnet A 3864 Hardenberg → Zwolle

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

Blauwnet A 3864 Hardenberg–Zwolle: final delay under 3 min on 19 of its 22 runs with data in the last 30 days (86%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 18:05 (GMT+1).

✓ Today’s run finished

Today, last fix heading to Dalfsen at 17:15 +1 min

  1. Hardenberg16:40
  2. Mariënberg16:46
  3. Ommen16:52
  4. Dalfsen17:00
  5. Zwolle17:08

Next service: tomorrow 16:40 from Hardenberg · Sun 22 Nov

Next departure 16:40 tomorrow · Hardenberg
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 20 full · 2 partial · 8 no data
On-time · 90 days
88%
29/33 runs under 3 min
RT coverage: 31 full · 2 partial · 56 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +7 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 6 Nov Max en route +32 min · last fix heading to Dalfsen +32 min
  • Mon 5 Oct Max en route +23 min · last fix heading to Dalfsen +23 min
  • Sun 8 Nov Max en route +14 min · last fix heading to Dalfsen +14 min
  • Thu 19 Nov Max en route +8 min · last fix heading to Dalfsen +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 29
  • 3–10 min 3% · 1
  • 10–30 min 6% · 2
  • 30+ min 3% · 1

On-time by weekday

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

Stops and timetable

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

Last 90 days, 33 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
16:40on time on time
16:46≈ on time ≈ +2 min
16:52 / 16:53≈ on time ≈ +3 min
17:00≈ on time ≈ +5 min
17:08on time +8 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
Sat 21 NovDalfsen 17:15Partial coverage+1 min+1 min
Fri 20 NovDalfsen 17:140 min—
Thu 19 NovDalfsen 17:17+8 min+8 min
Wed 18 NovDalfsen 17:14+2 min+2 min
Tue 17 NovDalfsen 17:14+3 min+3 min
Mon 16 NovDalfsen 17:150 min—
Sun 15 NovDalfsen 17:140 min—
Sat 14 NovDalfsen 17:14Partial coverage0 min—
Fri 13 NovDalfsen 17:140 min—
Thu 12 NovDalfsen 17:14+2 min+2 min
Wed 11 NovDalfsen 17:14+2 min+2 min
Tue 10 NovDalfsen 17:14+3 min+3 min
Mon 9 NovDalfsen 17:14+1 min+1 min
Sun 8 NovDalfsen 17:28+14 min+14 min
Sat 7 NovDalfsen 17:140 min—
Fri 6 NovDalfsen 17:47+32 min+32 min
Thu 5 NovDalfsen 17:14No data—
Wed 4 NovDalfsen 17:140 min—
Tue 3 NovDalfsen 17:14No data—
Mon 2 NovDalfsen 17:14No data—
Sun 1 NovDalfsen 17:16+1 min+1 min
Sat 31 OctDalfsen 17:140 min—
Fri 30 OctDalfsen 17:15No data—
Thu 29 OctDalfsen 17:140 min—
Wed 28 OctDalfsen 17:140 min—
Tue 27 OctDalfsen 17:14No data—
Mon 26 OctDalfsen 17:16No data—
Sun 25 OctDalfsen 17:15No data—
Sat 24 OctDalfsen 17:140 min—
Fri 23 OctDalfsen 17:14No data—