Train Blauwnet A 8058 Emmen – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Dalfsen at 15:44 0 min

  1. Emmen14:41
  2. Nieuw Amsterdam14:49
  3. Dalen14:55
  4. Gramsbergen15:06
  5. Mariënberg15:16
  6. Dalfsen15:30
  7. Zwolle15:38

Next service: tomorrow 14:41 from Emmen · Sun 8 Nov

Next departure 14:41 tomorrow · Emmen
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 10 full · 7 partial · 13 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 14 full · 7 partial · 68 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

Worst days

  • Wed 7 Oct Max en route +5 min · last fix heading to Dalfsen +5 min
  • Thu 8 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 90% · 19
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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