Train Blauwnet A 8069 Zwolle – Hardenberg

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

✓ Today’s run finished

Today, last fix heading to Mariënberg at 21:29 +2 min

  1. Zwolle20:52
  2. Dalfsen20:59
  3. Ommen21:06
  4. Mariënberg21:14
  5. Hardenberg21:19

Next service: tomorrow 20:52 from Zwolle · Sun 15 Nov

Next departure 20:52 tomorrow · Zwolle
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 16 full · 1 partial · 8 no data
On-time · 90 days
88%
21/24 runs under 3 min
RT coverage: 23 full · 1 partial · 25 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
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

  • Tue 6 Oct Max en route +11 min · last fix heading to — +9 min
  • Fri 23 Oct Max en route +8 min · last fix heading to — +7 min
  • Fri 6 Nov Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 21
  • 3–10 min 13% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 67% T n=3
  • 100% W n=4
  • 100% T n=1
  • 50% F n=4
  • 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, 24 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
20:52on time on time
20:59 / 21:00≈ on time ≈ +1 min
21:06 / 21:07≈ on time ≈ +2 min
21:14≈ +1 min ≈ +4 min
21:19+1 min +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 NovMariënberg 21:29Partial coverage+2 min+2 min
Fri 13 Nov— 21:54+2 min+3 min
Wed 11 Nov— 21:520 min—
Tue 10 Nov— 21:530 min—
Mon 9 Nov— 21:540 min+2 min
Sun 8 NovEmmen Zuid 21:590 min+3 min
Sat 7 NovEmmen Zuid 21:59+1 min+2 min
Fri 6 Nov— 21:59+5 min+5 min
Thu 5 Nov— 21:54No data—
Wed 4 Nov— 21:53+1 min+1 min
Mon 2 Nov— 21:54+1 min+2 min
Sun 1 NovEmmen Zuid 21:59+1 min+1 min
Sat 31 OctEmmen Zuid 22:01No data—
Thu 29 Oct— 21:53+1 min+2 min
Wed 28 Oct— 21:520 min—
Tue 27 Oct— 22:010 min—
Mon 26 Oct— 21:53No data—
Sun 25 OctEmmen Zuid 22:00No data—
Sat 24 OctEmmen Zuid 21:59No data—
Fri 23 Oct— 21:59+7 min+8 min
Thu 22 Oct— 21:55No data—
Wed 21 Oct— 21:54No data—
Mon 19 Oct— 21:530 min—
Sun 18 OctEmmen Zuid 22:02+2 min+3 min
Sat 17 OctEmmen Zuid 21:59No data—
Thu 15 Oct— 21:52No data—
Wed 14 Oct— 21:52No data—
Tue 13 Oct— 21:53No data—
Mon 12 Oct— 21:520 min—
Sun 11 OctEmmen Zuid 22:01+1 min+3 min