Train Blauwnet A 8046 Emmen – Zwolle

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 11:41 from Emmen · Fri 6 Nov

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

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

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

On-time by weekday

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

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