Train Blauwnet A 8057 Zwolle – Hardenberg

Zwolle 17:52 → Hardenberg 18:19 Daily 0 h 27 min · 5 stops Blauwnet A

It has not run yet today

Last recorded run: Wednesday 18 November +3 min

Next service: today 17:52 from Zwolle · Thu 19 Nov

Next departure 17:52 today · Zwolle
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 16 full · 4 partial · 9 no data
On-time · 90 days
94%
29/31 runs under 3 min
RT coverage: 27 full · 4 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Hardenberg, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 15 Nov Max en route +4 min · last fix heading to Mariënberg +4 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Emmen Zuid +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=4
  • 100% T n=3
  • 100% F n=4
  • 100% S n=4
  • 50% S n=4

Stops and timetable

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

Last 90 days, 31 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
17:52on time on time
17:59 / 18:00≈ on time ≈ +1 min
18:06 / 18:07≈ on time ≈ +1 min
18:14≈ on time ≈ +2 min
18:19on time +2 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 NovMariënberg 18:28Partial coverage+3 min+3 min
Tue 17 NovMariënberg 18:28Partial coverage+1 min+1 min
Mon 16 NovMariënberg 18:28Partial coverage0 min—
Sun 15 NovMariënberg 18:32+4 min+4 min
Sat 14 NovMariënberg 18:28Partial coverage0 min—
Fri 13 NovEmmen Zuid 18:590 min+2 min
Thu 12 NovHardenberg 18:540 min+4 min
Wed 11 NovMariënberg 18:520 min—
Tue 10 NovHardenberg 18:520 min—
Mon 9 NovOmmen 18:19+1 min+1 min
Sun 8 NovDalfsen 18:14No data—
Sat 7 NovEmmen Zuid 18:59+1 min+1 min
Fri 6 NovCoevorden 18:590 min—
Thu 5 NovOmmen 18:53No data—
Wed 4 NovMariënberg 18:28No data—
Tue 3 NovOmmen 18:190 min—
Mon 2 NovOmmen 18:190 min—
Sun 1 NovEmmen Zuid 19:03+3 min+4 min
Sat 31 OctEmmen Zuid 19:00+1 min+2 min
Fri 30 OctEmmen Zuid 18:59No data—
Thu 29 OctDalfsen 18:53+1 min—
Wed 28 OctOmmen 18:520 min—
Tue 27 OctDalfsen 18:550 min—
Mon 26 OctOmmen 18:54No data—
Sun 25 OctEmmen Zuid 18:59No data—
Sat 24 OctEmmen Zuid 18:59No data—
Fri 23 OctEmmen Zuid 18:59+2 min+4 min
Thu 22 OctEmmen Zuid 18:59No data—
Wed 21 OctDalen 18:53No data—
Tue 20 OctEmmen Zuid 18:530 min—