Train Blauwnet A 8049 Zwolle – Hardenberg

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

Running now · updated 16:02

Heading to Hardenberg 0 min

Estimated arrival at Hardenberg 16:19 · 142 km/h

  1. Zwolle15:52
  2. Dalfsen15:59
  3. Ommen16:06
  4. Mariënberg16:14
  5. Hardenberg16:19

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 20 runs arrived on time.

On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 16 full · 4 partial · 10 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 26 full · 4 partial · 59 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 30
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=2
  • 100% F n=3
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 30 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 10Today
15:52on time on time
15:59 / 16:00≈ on time ≈ +1 min
16:06 / 16:07≈ on time ≈ +1 min
16:14≈ on time ≈ +2 min
16: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 NovDalfsen 15:59Partial coverage0 min—
Tue 17 NovMariënberg 16:29Partial coverage+2 min+2 min
Mon 16 NovMariënberg 16:29Partial coverage+1 min+1 min
Sun 15 NovMariënberg 16:28Partial coverage0 min—
Sat 14 NovMariënberg 16:280 min—
Fri 13 NovEmmen Zuid 16:590 min—
Thu 12 NovEmmen Zuid 17:02+3 min+4 min
Wed 11 NovEmmen Zuid 16:590 min+1 min
Tue 10 NovEmmen Zuid 17:02+2 min+3 min
Mon 9 NovEmmen Zuid 16:59+2 min+2 min
Sun 8 NovEmmen Zuid 17:03+2 min+5 min
Sat 7 NovEmmen Zuid 16:590 min—
Fri 6 NovGramsbergen 17:040 min—
Thu 5 NovEmmen Zuid 16:59No data—
Wed 4 NovEmmen Zuid 16:590 min—
Tue 3 NovEmmen Zuid 16:59No data—
Mon 2 NovEmmen Zuid 16:59No data—
Sun 1 NovEmmen Zuid 17:00+1 min+2 min
Sat 31 OctEmmen Zuid 16:590 min—
Fri 30 OctEmmen Zuid 16:59No data—
Thu 29 OctEmmen Zuid 16:59No data—
Wed 28 OctEmmen Zuid 16:590 min—
Tue 27 OctEmmen Zuid 16:590 min—
Mon 26 OctEmmen Zuid 16:59No data—
Sun 25 OctEmmen Zuid 16:59No data—
Sat 24 OctEmmen Zuid 16:590 min—
Fri 23 OctEmmen Zuid 16:59No data—
Thu 22 OctEmmen Zuid 17:13No data—
Wed 21 OctEmmen Zuid 17:00No data—
Tue 20 OctEmmen Zuid 16:590 min—