Train Blauwnet A 8022 Emmen – Zwolle

Emmen 05:41 → Zwolle 06:38 Mon, Tue, Wed, Thu, Fri 0 h 57 min · 11 stops Blauwnet A

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 05:41 from Emmen · Mon 9 Nov

Next departure 05:41 Monday · Emmen
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 8 full · 11 partial · 2 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 8 full · 14 partial · 42 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 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

  • Fri 9 Oct Max en route +4 min · last fix heading to Dalfsen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 75% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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
05:41on time on time
05:44 / 05:46≈ on time ≈ on time
05:49 / 05:51≈ on time ≈ on time
05:56≈ on time ≈ +1 min
06:00≈ on time ≈ +1 min
06:06≈ on time ≈ +1 min
06:10≈ on time ≈ +1 min
06:16≈ on time ≈ +2 min
06:22 / 06:23≈ on time ≈ +2 min
06:30≈ on time ≈ +2 min
06: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
Fri 6 NovDalfsen 06:44No data—
Thu 5 NovDalfsen 06:44Partial coverage0 min—
Wed 4 NovDalfsen 06:44Partial coverage+1 min+1 min
Tue 3 NovDalfsen 06:44Partial coverage0 min—
Mon 2 NovDalfsen 06:44No data—
Fri 30 OctDalfsen 06:45+1 min+1 min
Thu 29 OctDalfsen 06:45Partial coverage0 min—
Wed 28 OctDalfsen 06:45Partial coverage+2 min+2 min
Tue 27 OctDalfsen 06:44Partial coverage0 min—
Mon 26 OctDalfsen 06:45Partial coverage0 min—
Fri 23 OctDalfsen 06:440 min—
Thu 22 OctDalfsen 06:44Partial coverage0 min—
Wed 21 OctDalfsen 06:45Partial coverage+1 min—
Tue 20 OctDalfsen 06:44Partial coverage0 min—
Mon 19 OctDalfsen 06:44Partial coverage0 min—
Fri 16 OctDalfsen 06:440 min—
Thu 15 OctDalfsen 06:450 min—
Wed 14 OctDalfsen 06:46+2 min+2 min
Tue 13 OctDalfsen 06:440 min—
Mon 12 OctDalfsen 06:440 min—
Fri 9 OctDalfsen 06:48+4 min+4 min
Thu 8 OctDalfsen 06:44Partial coverage0 min—
Wed 7 OctDalfsen 06:48Partial coverage+3 min+4 min
Tue 6 OctDalfsen 06:44Partial coverage0 min—
Mon 5 OctDalfsen 06:46No data—
Fri 2 OctDalfsen 06:44No data—
Thu 1 OctDalfsen 06:44No data—
Wed 30 SeptDalfsen 06:44No data—
Tue 29 SeptDalfsen 06:44No data—
Mon 28 SeptDalfsen 06:44No data—