Train Blauwnet A 3848 Hardenberg – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Dalfsen at 13:15 0 min

  1. Hardenberg12:40
  2. Mariënberg12:46
  3. Ommen12:52
  4. Dalfsen13:00
  5. Zwolle13:08

Next service: tomorrow 12:40 from Hardenberg · Tue 17 Nov

Next departure 12:40 tomorrow · Hardenberg
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 17 full · 1 partial · 12 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 24 full · 1 partial · 64 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=3
  • 100% T n=3
  • 100% F n=2
  • 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, 25 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
12:40on time on time
12:46≈ on time ≈ on time
12:52 / 12:53≈ on time ≈ +1 min
13:00≈ on time ≈ +1 min
13:08on 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
Mon 16 NovDalfsen 13:15Partial coverage0 min—
Sun 15 NovDalfsen 13:15+1 min+1 min
Sat 14 NovDalfsen 13:140 min—
Fri 13 NovDalfsen 13:140 min—
Thu 12 NovDalfsen 13:140 min—
Wed 11 NovDalfsen 13:140 min—
Tue 10 NovDalfsen 13:140 min—
Mon 9 NovDalfsen 13:140 min—
Sun 8 NovDalfsen 13:140 min—
Sat 7 NovDalfsen 13:14+2 min+2 min
Fri 6 NovDalfsen 13:14No data—
Thu 5 NovDalfsen 13:14No data—
Wed 4 NovDalfsen 13:14No data—
Tue 3 NovDalfsen 13:14No data—
Mon 2 NovDalfsen 13:14No data—
Sun 1 NovDalfsen 13:18+2 min+2 min
Sat 31 OctDalfsen 13:140 min—
Fri 30 OctDalfsen 13:14No data—
Thu 29 OctDalfsen 13:140 min—
Wed 28 OctDalfsen 13:150 min—
Tue 27 OctDalfsen 13:14No data—
Mon 26 OctDalfsen 13:15No data—
Sun 25 OctDalfsen 13:16No data—
Sat 24 OctDalfsen 13:150 min—
Fri 23 OctDalfsen 13:15No data—
Thu 22 OctDalfsen 13:16No data—
Wed 21 OctDalfsen 13:14No data—
Tue 20 OctDalfsen 13:140 min—
Mon 19 OctDalfsen 13:150 min—
Sun 18 OctDalfsen 13:150 min—