Train Blauwnet A 8050 Emmen – Zwolle

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

It has not run yet today

Last recorded run: Wednesday 4 November No data

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

Next departure 12:41 today · Emmen
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 6 full · 6 partial · 17 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 8 full · 6 partial · 74 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=1
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

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