Train Blauwnet A 13851 Zwolle – Emmen

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

✓ Today’s run finished

Today, last fix heading to Emmen Zuid at 17:37 No data

  1. Zwolle16:39
  2. Dalfsen16:46
  3. Ommen16:52
  4. Hardenberg17:04
  5. Coevorden17:13
  6. Emmen Zuid17:23
  7. Emmen17:28

Next service: tomorrow 16:39 from Zwolle · Fri 6 Nov

Next departure 16:39 tomorrow · Zwolle
On-time · 30 days
86%
6/7 runs under 3 min
RT coverage: 0 full · 7 partial · 10 no data
On-time · 90 days
89%
8/9 runs under 3 min
RT coverage: 0 full · 9 partial · 44 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Thu 8 Oct Max en route +4 min · last fix heading to Emmen Zuid +4 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

  • 100% M n=2
  • 100% T n=3
  • 100% W n=2
  • 50% T n=2
  • — F n=0
  • — 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
16:39on time on time
16:46— —
16:52 / 16:53— —
17:04— —
17:13 / 17:14— —
17:23— —
17: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 NovEmmen Zuid 17:37No data—
Wed 4 NovEmmen Zuid 17:37No data—
Tue 3 NovEmmen Zuid 17:34No data—
Mon 2 NovEmmen Zuid 17:37No data—
Fri 30 OctEmmen Zuid 17:38No data—
Thu 29 OctEmmen Zuid 17:33Partial coverage0 min—
Wed 28 OctEmmen Zuid 17:37Partial coverage0 min—
Tue 27 OctEmmen Zuid 17:37Partial coverage0 min—
Mon 26 OctEmmen Zuid 17:37No data—
Fri 23 OctEmmen Zuid 17:39No data—
Thu 22 OctEmmen Zuid 17:44No data—
Wed 21 OctEmmen Zuid 17:38No data—
Tue 20 OctEmmen Zuid 17:37Partial coverage0 min—
Mon 19 OctEmmen Zuid 17:37Partial coverage0 min—
Fri 9 OctEmmen Zuid 17:37No data—
Thu 8 OctEmmen Zuid 17:34Partial coverage+4 min+4 min
Wed 7 OctEmmen Zuid 17:37Partial coverage+1 min+1 min
Tue 6 OctEmmen Zuid 17:37Partial coverage+2 min+2 min
Mon 5 OctEmmen Zuid 17:37Partial coverage0 min—
Fri 2 OctEmmen Zuid 17:37No data—
Thu 1 OctEmmen Zuid 17:37No data—
Wed 30 SeptEmmen Zuid 17:37No data—
Tue 29 SeptEmmen Zuid 17:37No data—
Mon 28 SeptEmmen Zuid 17:37No data—
Fri 25 SeptEmmen Zuid 17:37No data—
Thu 24 SeptEmmen Zuid 17:37No data—
Wed 23 SeptEmmen Zuid 17:37No data—
Tue 22 SeptEmmen Zuid 17:37No data—
Mon 21 SeptEmmen Zuid 17:37No data—
Fri 18 SeptEmmen Zuid 17:40No data—