Train Blauwnet A 13855 Zwolle – Emmen

Zwolle 17:39 → Emmen 18:28 Mon, Tue, Wed, Thu, Fri 0 h 49 min · 7 stops Blauwnet A

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 17:39 from Zwolle · Fri 6 Nov

Next departure 17:39 today · Zwolle
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 0 full · 7 partial · 9 no data
On-time · 90 days
89%
8/9 runs under 3 min
RT coverage: 0 full · 9 partial · 43 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Emmen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 5 Oct Max en route +3 min · last fix heading to Hardenberg +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 8
  • 3–10 min 11% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 9 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:39on time on time
17:46— —
17:52 / 17:53— —
18:04— —
18:13 / 18:14— —
18:23— —
18:28— —

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 NovHardenberg 18:33No data—
Wed 4 NovCoevorden 18:28Partial coverage0 min—
Tue 3 NovHardenberg 18:18No data—
Mon 2 NovHardenberg 18:18No data—
Fri 30 OctEmmen Zuid 18:37No data—
Thu 29 OctOmmen 18:31No data—
Wed 28 OctHardenberg 18:30Partial coverage0 min—
Tue 27 OctHardenberg 18:35No data—
Mon 26 OctHardenberg 18:35Partial coverage0 min—
Fri 23 OctEmmen Zuid 18:37No data—
Thu 22 OctEmmen Zuid 18:47No data—
Wed 21 OctEmmen Zuid 18:34No data—
Tue 20 OctEmmen Zuid 18:37Partial coverage0 min—
Mon 19 OctEmmen Zuid 18:37Partial coverage0 min—
Fri 9 OctEmmen Zuid 18:37Partial coverage+1 min+1 min
Thu 8 OctOmmen 18:34Partial coverage+2 min+2 min
Wed 7 OctHardenberg 18:29No data—
Tue 6 OctHardenberg 18:32Partial coverage+2 min+2 min
Mon 5 OctHardenberg 18:18Partial coverage+3 min+3 min
Fri 2 OctEmmen Zuid 18:37No data—
Thu 1 OctHardenberg 18:18No data—
Wed 30 SeptHardenberg 18:18No data—
Tue 29 SeptHardenberg 18:18No data—
Mon 28 SeptHardenberg 18:18No data—
Fri 25 SeptEmmen Zuid 18:37No data—
Thu 24 SeptOmmen 18:08No data—
Wed 23 SeptHardenberg 18:18No data—
Tue 22 SeptHardenberg 18:18No data—
Mon 21 SeptHardenberg 18:18No data—
Fri 18 SeptEmmen Zuid 18:37No data—