Train Blauwnet A 3868 Emmen – Zwolle

Emmen 17:15 → Zwolle 18:08 Sat, Sun 0 h 53 min · 9 stops Blauwnet A

It does not run today

Last recorded run: Sunday 1 November +1 min

Next service: Saturday 17:15 from Emmen · Sat 7 Nov

Next departure 17:15 Saturday · Emmen
On-time · 30 days
83%
5/6 runs under 3 min
RT coverage: 0 full · 6 partial · 2 no data
On-time · 90 days
83%
5/6 runs under 3 min
RT coverage: 0 full · 6 partial · 20 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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 18 Oct Max en route +4 min · last fix heading to Dalfsen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 5
  • 3–10 min 17% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=3
  • 67% S n=3

Stops and timetable

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

Last 90 days, 6 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:15on time on time
17:20— —
17:23 / 17:24— —
17:31 / 17:32— —
17:40— —
17:46— —
17:52 / 17:53— —
18:00— —
18:08— —

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
Sun 1 NovDalfsen 18:16Partial coverage+1 min+1 min
Sat 31 OctDalfsen 18:15Partial coverage0 min—
Sun 25 OctDalfsen 18:15No data—
Sat 24 OctDalfsen 18:14Partial coverage0 min—
Sun 18 OctDalfsen 18:18Partial coverage+4 min+4 min
Sat 17 OctDalfsen 18:15No data—
Sun 11 OctDalfsen 18:14Partial coverage0 min—
Sat 10 OctDalfsen 18:16Partial coverage+1 min+1 min
Sun 4 OctDalfsen 18:14No data—
Sat 3 OctDalfsen 18:16No data—
Sun 27 SeptDalfsen 18:16No data—
Sat 26 SeptDalfsen 18:15No data—
Sun 20 SeptDalfsen 18:14No data—
Sat 19 SeptDalfsen 18:15No data—
Sun 13 SeptDalfsen 18:14No data—
Sat 12 SeptDalfsen 18:14No data—
Sun 6 SeptOmmen 18:08No data—
Sat 5 SeptOmmen 18:08No data—
Sun 30 AugDalfsen 18:15No data—
Sat 29 AugDalfsen 18:17No data—
Sun 23 AugDalfsen 18:15No data—
Sat 22 AugDalfsen 18:16No data—
Sun 16 AugDalfsen 18:15No data—
Sat 15 AugDalfsen 18:16No data—
Sun 9 AugDalfsen 18:14No data—
Sat 8 AugDalfsen 18:14No data—