Train Blauwnet A 3876 Hardenberg – Zwolle

Hardenberg 19:40 → Zwolle 20:08 Daily 0 h 28 min · 5 stops Blauwnet A

It has not run yet today

Last recorded run: Sunday 15 November +3 min

Next service: today 19:40 from Hardenberg · Mon 16 Nov

Next departure 19:40 today · Hardenberg
On-time · 30 days
73%
11/15 runs under 3 min
RT coverage: 14 full · 1 partial · 9 no data
On-time · 90 days
80%
16/20 runs under 3 min
RT coverage: 19 full · 1 partial · 30 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: +5 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

  • Mon 9 Nov Max en route +7 min · last fix heading to — +7 min
  • Thu 12 Nov Max en route +5 min · last fix heading to — +5 min
  • Fri 23 Oct Max en route +4 min · last fix heading to Nieuw Amsterdam +4 min
  • Sun 15 Nov Max en route +3 min · last fix heading to Dalfsen +3 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 80% · 16
  • 3–10 min 20% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=4
  • 100% W n=1
  • 50% T n=2
  • 50% F n=2
  • 100% S n=4
  • 75% S n=4

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
19:40on time on time
19:46≈ on time ≈ +1 min
19:52 / 19:53≈ on time ≈ +2 min
20:00≈ +1 min ≈ +3 min
20:08+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
Sun 15 NovDalfsen 20:18Partial coverage+3 min+3 min
Sat 14 NovDalfsen 20:14+1 min—
Thu 12 Nov— 20:14+5 min+5 min
Wed 11 Nov— 20:12+2 min+2 min
Tue 10 Nov— 20:090 min—
Mon 9 Nov— 20:19+7 min+7 min
Sun 8 NovOmmen 20:07No data—
Sat 7 NovDalfsen 20:14+1 min+1 min
Thu 5 Nov— 20:12No data—
Sun 1 NovDalfsen 20:18+3 min+3 min
Sat 31 OctDalfsen 20:150 min—
Fri 30 Oct— 20:11No data—
Thu 29 Oct— 20:110 min—
Wed 28 Oct— 20:12No data—
Tue 27 Oct— 20:140 min—
Mon 26 OctMariënberg 20:15No data—
Sun 25 OctDalfsen 20:15No data—
Sat 24 OctDalfsen 20:15No data—
Fri 23 OctNieuw Amsterdam 20:15+4 min+4 min
Thu 22 Oct— 20:14No data—
Wed 21 Oct— 20:15No data—
Tue 20 Oct— 20:110 min—
Mon 19 Oct— 20:120 min—
Sun 18 OctDalfsen 20:17+3 min+3 min
Sat 17 OctDalfsen 20:15No data—
Fri 16 OctOmmen 20:07No data—
Wed 14 OctMariënberg 20:15No data—
Tue 13 Oct— 20:12No data—
Mon 12 Oct— 20:110 min—
Sun 11 OctDalfsen 20:17+2 min+2 min