Train Blauwnet A 8028 Emmen – Zwolle

Emmen 07:11 → Zwolle 08:08 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 07:11 from Emmen · Mon 9 Nov

Full trip card
Next departure 07:11 Monday · Emmen
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 5 full · 13 partial · 3 no data
On-time · 90 days
86%
18/21 runs under 3 min
RT coverage: 5 full · 16 partial · 43 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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
  • Wed 7 Oct Max en route +4 min · last fix heading to Dalfsen +4 min
  • Mon 26 Oct Max en route +4 min · last fix heading to Dalfsen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 18
  • 3–10 min 14% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=5
  • 80% W n=5
  • 100% T n=4
  • 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, 21 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
Emmen
07:11on time on time
Emmen Zuid
07:14 / 07:16≈ on time ≈ on time
Nieuw Amsterdam
07:19 / 07:21≈ on time ≈ on time
Dalen
07:26≈ on time ≈ on time
Coevorden
07:30≈ on time ≈ on time
Gramsbergen
07:36≈ on time ≈ on time
Hardenberg
07:40≈ on time ≈ on time
Mariënberg
07:46≈ on time ≈ on time
Ommen
07:52 / 07:53≈ on time ≈ on time
Dalfsen
08:00≈ on time ≈ on time
Zwolle
08:08on time on time

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 08:19No data—
Thu 5 NovDalfsen 08:18No data—
Wed 4 NovDalfsen 08:17Partial coverage+2 min+2 min
Tue 3 NovDalfsen 08:14Partial coverage0 min—
Mon 2 NovDalfsen 08:17No data—
Fri 30 OctDalfsen 08:15Partial coverage0 min—
Thu 29 OctDalfsen 08:16Partial coverage0 min—
Wed 28 OctDalfsen 08:17Partial coverage0 min—
Tue 27 OctDalfsen 08:15Partial coverage0 min—
Mon 26 OctDalfsen 08:20Partial coverage+4 min+4 min
Fri 23 OctDalfsen 08:16Partial coverage0 min—
Thu 22 OctDalfsen 08:17Partial coverage0 min—
Wed 21 OctDalfsen 08:19Partial coverage0 min—
Tue 20 OctDalfsen 08:18Partial coverage0 min—
Mon 19 OctDalfsen 08:16Partial coverage0 min—
Fri 16 OctDalfsen 08:140 min—
Thu 15 OctDalfsen 08:200 min—
Wed 14 OctDalfsen 08:160 min—
Tue 13 OctDalfsen 08:160 min—
Mon 12 OctDalfsen 08:160 min—
Fri 9 OctDalfsen 08:19Partial coverage+4 min+4 min
Thu 8 OctDalfsen 08:16Partial coverage+1 min+1 min
Wed 7 OctDalfsen 08:19Partial coverage+4 min+4 min
Tue 6 OctDalfsen 08:16Partial coverage+1 min+1 min
Mon 5 OctDalfsen 08:16No data—
Fri 2 OctDalfsen 08:16No data—
Thu 1 OctDalfsen 08:15No data—
Wed 30 SeptDalfsen 08:15No data—
Tue 29 SeptDalfsen 08:18No data—
Mon 28 SeptDalfsen 08:16No data—