Train Blauwnet A 8070 Hardenberg – Zwolle

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

✓ Today’s run finished

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

  1. Hardenberg18:10
  2. Mariënberg18:16
  3. Ommen18:22
  4. Dalfsen18:30
  5. Zwolle18:38

Next service: tomorrow 18:10 from Hardenberg · Sun 15 Nov

Next departure 18:10 tomorrow · Hardenberg
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 18 full · 1 partial · 11 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 25 full · 1 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: +4 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 13 Nov Max en route +6 min · last fix heading to Dalfsen +6 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Dalfsen +4 min
  • Fri 23 Oct 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 88% · 23
  • 3–10 min 12% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=3
  • 100% W n=3
  • 100% T n=2
  • 50% F n=4
  • 100% S n=4
  • 75% 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
18:10on time on time
18:16≈ on time ≈ +1 min
18:22 / 18:23≈ on time ≈ +2 min
18:30≈ on time ≈ +3 min
18:38on 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
Sat 14 NovDalfsen 18:44Partial coverage0 min—
Fri 13 NovDalfsen 18:44+6 min+6 min
Thu 12 NovMariënberg 18:44+3 min+3 min
Wed 11 NovHardenberg 18:24+1 min+1 min
Tue 10 NovMariënberg 18:290 min+1 min
Mon 9 NovHardenberg 18:43+2 min+2 min
Sun 8 NovDalfsen 18:47+3 min+3 min
Sat 7 NovDalfsen 18:44+1 min+1 min
Fri 6 NovDalfsen 18:590 min—
Thu 5 NovHardenberg 18:43No data—
Wed 4 NovHardenberg 18:440 min—
Tue 3 NovHardenberg 18:24No data—
Mon 2 NovHardenberg 18:390 min—
Sun 1 NovDalfsen 18:49+4 min+4 min
Sat 31 OctDalfsen 18:450 min—
Fri 30 OctDalfsen 18:44No data—
Thu 29 OctCoevorden 18:43No data—
Wed 28 OctHardenberg 18:380 min—
Tue 27 OctCoevorden 18:45No data—
Mon 26 OctGramsbergen 18:460 min—
Sun 25 OctDalfsen 18:44No data—
Sat 24 OctDalfsen 18:45No data—
Fri 23 OctDalfsen 18:44+3 min+3 min
Thu 22 OctDalfsen 19:02No data—
Wed 21 OctDalfsen 18:44No data—
Tue 20 OctDalfsen 18:440 min—
Mon 19 OctDalfsen 18:440 min—
Sun 18 OctDalfsen 18:45+1 min—
Sat 17 OctDalfsen 18:45No data—
Fri 16 OctDalfsen 18:47No data—