Train Blauwnet A 8070 Emmen – Zwolle

Emmen 17:41 → Zwolle 18:38 Daily 0 h 57 min · 11 stops Blauwnet A

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 17:41 from Emmen · Thu 5 Nov

Next departure 17:41 today · Emmen
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 6 full · 9 partial · 14 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 6 full · 11 partial · 71 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

  • Sun 1 Nov Max en route +4 min · last fix heading to Dalfsen +4 min
  • Fri 23 Oct Max en route +3 min · last fix heading to Dalfsen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 15
  • 3–10 min 12% · 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=2
  • 100% T n=1
  • 50% F n=2
  • 100% S n=2
  • 67% S n=3

Stops and timetable

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

Last 90 days, 17 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
17:41on time on time
17:44 / 17:46≈ on time ≈ on time
17:49 / 17:51≈ on time ≈ on time
17:56≈ on time ≈ +1 min
18:00≈ on time ≈ +1 min
18:06≈ on time ≈ +1 min
18:10≈ on time ≈ +1 min
18:16≈ on time ≈ +2 min
18:22 / 18:23≈ on time ≈ +2 min
18:30≈ on time ≈ +2 min
18:38+1 min +2 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
Wed 4 NovHardenberg 18:44Partial coverage0 min—
Tue 3 NovHardenberg 18:24No data—
Mon 2 NovHardenberg 18:39Partial coverage0 min—
Sun 1 NovDalfsen 18:49+4 min+4 min
Sat 31 OctDalfsen 18:450 min—
Fri 30 OctDalfsen 18:44No data—
Thu 29 OctCoevorden 18:43No data—
Wed 28 OctHardenberg 18:38Partial coverage0 min—
Tue 27 OctCoevorden 18:45No data—
Mon 26 OctGramsbergen 18:46Partial coverage0 min—
Sun 25 OctDalfsen 18:44No data—
Sat 24 OctDalfsen 18:45No data—
Fri 23 OctDalfsen 18:44Partial coverage+3 min+3 min
Thu 22 OctDalfsen 19:02No data—
Wed 21 OctDalfsen 18:44No data—
Tue 20 OctDalfsen 18:44Partial coverage0 min—
Mon 19 OctDalfsen 18:44Partial coverage0 min—
Sun 18 OctDalfsen 18:45+1 min—
Sat 17 OctDalfsen 18:45No data—
Fri 16 OctDalfsen 18:47No data—
Thu 15 OctDalfsen 18:44No data—
Wed 14 OctDalfsen 18:49No data—
Tue 13 OctDalfsen 18:44No data—
Mon 12 OctDalfsen 18:44Partial coverage0 min—
Sun 11 OctDalfsen 18:450 min—
Sat 10 OctDalfsen 18:45+1 min—
Fri 9 OctDalfsen 18:44+1 min—
Thu 8 OctCoevorden 18:40Partial coverage0 min—
Wed 7 OctGramsbergen 18:40No data—
Tue 6 OctCoevorden 18:42Partial coverage0 min—