Train Blauwnet A 8077 Zwolle – Hardenberg

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

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 22:52 from Zwolle · Sun 15 Nov

Next departure 22:52 today · Zwolle
On-time · 30 days
80%
12/15 runs under 3 min
RT coverage: 14 full · 1 partial · 11 no data
On-time · 90 days
81%
17/21 runs under 3 min
RT coverage: 20 full · 1 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Thu 12 Nov Max en route +7 min · last fix heading to — +7 min
  • Thu 29 Oct Max en route +4 min · last fix heading to — +4 min
  • Mon 2 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 9 Oct Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 17
  • 3–10 min 19% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=3
  • 100% W n=2
  • 33% T n=3
  • 50% F n=2
  • 100% S n=3
  • 100% S n=4

Stops and timetable

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

Last 90 days, 21 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
22:52on time on time
22:59 / 23:00≈ on time ≈ +1 min
23:06 / 23:07≈ on time ≈ +2 min
23:14≈ on time ≈ +3 min
23:19on time +4 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 23:19Partial coverage0 min—
Thu 12 Nov— 23:59+7 min+7 min
Wed 11 Nov— 23:520 min—
Tue 10 Nov— 23:520 min+1 min
Mon 9 Nov— 23:54+2 min+3 min
Sun 8 NovEmmen Zuid 23:59+1 min+3 min
Sat 7 NovHardenberg 23:54+2 min+3 min
Thu 5 Nov— 23:590 min—
Tue 3 Nov— 23:24No data—
Mon 2 Nov— 23:54+4 min+4 min
Sun 1 NovEmmen Zuid 23:590 min+2 min
Sat 31 OctHardenberg 23:33No data—
Fri 30 Oct— 23:53No data—
Thu 29 Oct— 23:56+4 min+4 min
Wed 28 Oct— 23:51No data—
Tue 27 Oct— 23:510 min—
Mon 26 Oct— 23:54No data—
Sun 25 OctEmmen Zuid 23:59No data—
Sat 24 Oct— 23:53No data—
Fri 23 Oct— 23:55+2 min+3 min
Thu 22 Oct— 23:55No data—
Wed 21 Oct— 23:50No data—
Tue 20 Oct— 23:57No data—
Mon 19 Oct— 23:530 min—
Sun 18 OctEmmen Zuid 00:060 min+9 min
Sat 17 OctEmmen Zuid 00:03No data—
Wed 14 Oct— 23:520 min—
Tue 13 Oct— 23:52No data—
Mon 12 Oct— 23:54+1 min+2 min
Sun 11 OctEmmen Zuid 23:590 min+3 min