Train Blauwnet A 8082 Hardenberg – Zwolle

Hardenberg 21:10 → Zwolle 21:38 Daily 0 h 28 min · 5 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Dalfsen at 21:47 +2 min

  1. Hardenberg21:10
  2. Mariënberg21:16
  3. Ommen21:22
  4. Dalfsen21:30
  5. Zwolle21:38

Next service: tomorrow 21:10 from Hardenberg · Mon 16 Nov

Next departure 21:10 tomorrow · Hardenberg
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 15 full · 2 partial · 7 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 21 full · 2 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Zwolle, 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 +8 min · last fix heading to — +8 min
  • Fri 13 Nov Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=1
  • 67% T n=3
  • 80% F n=5
  • 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, 23 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
21:10on time on time
21:16≈ on time ≈ +1 min
21:22 / 21:23≈ on time ≈ +1 min
21:30≈ on time ≈ +2 min
21:38on time +3 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
Sun 15 NovDalfsen 21:47Partial coverage+2 min+2 min
Sat 14 NovDalfsen 21:44Partial coverage0 min—
Fri 13 Nov— 21:44+3 min+3 min
Thu 12 Nov— 21:49+8 min+8 min
Wed 11 Nov— 21:390 min—
Mon 9 Nov— 21:43+2 min+2 min
Sat 7 NovDalfsen 21:440 min—
Fri 6 Nov— 21:430 min—
Thu 5 Nov— 21:390 min—
Mon 2 Nov— 21:390 min—
Sun 1 NovDalfsen 21:44+1 min+1 min
Sat 31 OctDalfsen 21:45No data—
Fri 30 Oct— 21:44No data—
Thu 29 Oct— 21:400 min—
Tue 27 Oct— 21:410 min—
Mon 26 Oct— 21:40No data—
Sun 25 OctDalfsen 21:45No data—
Sat 24 OctDalfsen 21:49No data—
Fri 23 Oct— 21:43+3 min+3 min
Thu 22 Oct— 21:45No data—
Tue 20 Oct— 21:400 min—
Mon 19 Oct— 21:400 min—
Sun 18 OctDalfsen 21:46+1 min+1 min
Sat 17 OctDalfsen 21:44No data—
Fri 16 Oct— 21:42+1 min+1 min
Thu 15 Oct— 21:42No data—
Tue 13 Oct— 21:41No data—
Mon 12 Oct— 21:420 min—
Sun 11 OctDalfsen 21:46+3 min+3 min
Sat 10 OctDalfsen 21:44+1 min+1 min