Train Blauwnet A 8055 Zwolle – Hardenberg

Zwolle 17:22 → Hardenberg 17:49 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 17:58 +1 min

  1. Zwolle17:22
  2. Dalfsen17:29
  3. Ommen17:36
  4. Mariënberg17:44
  5. Hardenberg17:49

Next service: tomorrow 17:22 from Zwolle · Thu 19 Nov

Next departure 17:22 tomorrow · Zwolle
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 10 full · 3 partial · 9 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 17 full · 3 partial · 43 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: +2 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

  • Mon 5 Oct Max en route +10 min · last fix heading to Nieuw Amsterdam +8 min
  • Tue 17 Nov Max en route +4 min · last fix heading to Mariënberg +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 18
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 75% T n=4
  • 100% W n=5
  • 100% T n=2
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 20 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:22on time on time
17:29 / 17:30≈ on time ≈ on time
17:36 / 17:37≈ on time ≈ on time
17:44≈ on time ≈ +1 min
17:49on 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
Wed 18 NovMariënberg 17:58Partial coverage+1 min+1 min
Tue 17 NovMariënberg 17:58Partial coverage+4 min+4 min
Mon 16 NovMariënberg 17:58Partial coverage+2 min+2 min
Fri 13 NovEmmen Zuid 18:29+1 min+3 min
Thu 12 NovEmmen Zuid 18:290 min+2 min
Wed 11 NovNieuw Amsterdam 18:24+1 min+2 min
Tue 10 NovEmmen Zuid 18:290 min+2 min
Mon 9 NovNieuw Amsterdam 18:240 min+1 min
Fri 6 NovCoevorden 18:340 min—
Thu 5 NovNieuw Amsterdam 18:24No data—
Wed 4 NovEmmen Zuid 18:290 min—
Tue 3 NovNieuw Amsterdam 18:24No data—
Mon 2 NovDalen 18:23No data—
Fri 30 OctEmmen Zuid 18:29No data—
Thu 29 OctCoevorden 18:22No data—
Wed 28 OctNieuw Amsterdam 18:250 min—
Tue 27 OctDalen 18:18No data—
Mon 26 OctDalen 18:250 min—
Fri 23 OctEmmen Zuid 18:29No data—
Thu 22 OctEmmen Zuid 18:32No data—
Wed 21 OctEmmen Zuid 18:29No data—
Tue 20 OctEmmen Zuid 18:290 min—
Mon 19 OctEmmen Zuid 18:290 min—
Fri 16 OctEmmen Zuid 18:30No data—
Thu 15 OctEmmen Zuid 18:29No data—
Wed 14 OctEmmen Zuid 18:31No data—
Tue 13 OctEmmen Zuid 18:29No data—
Mon 12 OctEmmen Zuid 18:290 min—
Fri 9 OctEmmen Zuid 18:290 min—
Thu 8 OctCoevorden 18:220 min+2 min