Train Blauwnet A 8009 Zwolle – Hardenberg

Zwolle 05:52 → Hardenberg 06:19 Mon, Tue, Wed, Thu, Fri 0 h 27 min · 5 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Mariënberg at 06:29 +1 min

  1. Zwolle05:52
  2. Dalfsen05:59
  3. Ommen06:06
  4. Mariënberg06:14
  5. Hardenberg06:19

Next service: tomorrow 05:52 from Zwolle · Wed 18 Nov

Next departure 05:52 tomorrow · Zwolle
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 18 full · 2 partial · 2 no data
On-time · 90 days
93%
27/29 runs under 3 min
RT coverage: 27 full · 2 partial · 34 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: +1 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 29 Oct Max en route +9 min · last fix heading to Emmen Zuid +7 min
  • Wed 7 Oct Max en route +6 min · last fix heading to Emmen Zuid +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 27
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=7
  • 83% W n=6
  • 83% T n=6
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 29 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
05:52on time on time
05:59 / 06:00≈ on time ≈ on time
06:06 / 06:07≈ on time ≈ +1 min
06:14≈ on time ≈ +1 min
06:19on time +1 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 NovMariënberg 06:29Partial coverage+1 min+1 min
Mon 16 NovMariënberg 06:29Partial coverage+2 min+2 min
Fri 13 NovEmmen Zuid 06:59+1 min+3 min
Thu 12 NovEmmen Zuid 06:59+1 min—
Wed 11 NovEmmen Zuid 06:590 min+1 min
Tue 10 NovEmmen Zuid 06:590 min+1 min
Mon 9 NovEmmen Zuid 06:590 min+2 min
Fri 6 NovEmmen Zuid 06:59No data—
Thu 5 NovEmmen Zuid 07:030 min—
Wed 4 NovEmmen Zuid 06:590 min+2 min
Tue 3 NovEmmen Zuid 06:590 min+2 min
Mon 2 NovEmmen Zuid 06:59No data—
Fri 30 OctEmmen Zuid 06:590 min—
Thu 29 OctEmmen Zuid 07:07+7 min+9 min
Wed 28 OctEmmen Zuid 06:590 min—
Tue 27 OctEmmen Zuid 06:590 min—
Mon 26 OctEmmen Zuid 07:01+1 min+3 min
Fri 23 OctEmmen Zuid 07:00+1 min—
Thu 22 OctEmmen Zuid 07:00+1 min+1 min
Wed 21 OctEmmen Zuid 06:590 min+1 min
Tue 20 OctEmmen Zuid 06:590 min+2 min
Mon 19 OctEmmen Zuid 06:590 min+3 min
Fri 16 OctEmmen Zuid 06:590 min—
Thu 15 OctEmmen Zuid 07:00+1 min+2 min
Wed 14 OctEmmen Zuid 06:590 min+1 min
Tue 13 OctEmmen Zuid 07:00+1 min+2 min
Mon 12 OctEmmen Zuid 07:000 min+2 min
Fri 9 OctEmmen Zuid 07:01+2 min+3 min
Thu 8 OctEmmen Zuid 07:00+1 min—
Wed 7 OctEmmen Zuid 07:03+4 min+6 min