Train Blauwnet A 13847 Zwolle – Coevorden

Zwolle 15:39 → Coevorden 16:13 Mon, Tue, Wed, Thu, Fri 0 h 34 min · 5 stops Blauwnet A

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 15:39 from Zwolle · Thu 5 Nov

Next departure 15:39 today · Zwolle
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 8 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 42 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 Coevorden, 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=3
  • 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 (5 stops).

Last 90 days, 10 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
15:39on time on time
15:46— —
15:52 / 15:53— —
16:04— —
16:13— —

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
Wed 4 NovHardenberg 16:19Partial coverage+1 min—
Tue 3 NovHardenberg 16:19No data—
Mon 2 NovHardenberg 16:19No data—
Fri 30 OctHardenberg 16:18No data—
Thu 29 OctHardenberg 16:20No data—
Wed 28 OctHardenberg 16:19Partial coverage0 min—
Tue 27 OctHardenberg 16:20Partial coverage0 min—
Mon 26 OctHardenberg 16:19No data—
Fri 23 OctHardenberg 16:20No data—
Thu 22 OctHardenberg 16:28No data—
Wed 21 OctHardenberg 16:19No data—
Tue 20 OctHardenberg 16:37Partial coverage0 min—
Mon 19 OctHardenberg 16:21Partial coverage0 min—
Fri 9 OctHardenberg 16:19Partial coverage0 min—
Thu 8 OctHardenberg 16:20Partial coverage+1 min+1 min
Wed 7 OctHardenberg 16:21Partial coverage+3 min+3 min
Tue 6 OctHardenberg 16:19Partial coverage+1 min+1 min
Mon 5 OctHardenberg 16:20Partial coverage+1 min+1 min
Fri 2 OctHardenberg 16:19No data—
Thu 1 OctHardenberg 16:19No data—
Wed 30 SeptHardenberg 16:19No data—
Tue 29 SeptHardenberg 16:19No data—
Mon 28 SeptHardenberg 16:21No data—
Fri 25 SeptHardenberg 16:21No data—
Thu 24 SeptHardenberg 16:19No data—
Wed 23 SeptHardenberg 16:19No data—
Tue 22 SeptHardenberg 16:19No data—
Mon 21 SeptHardenberg 16:19No data—
Fri 18 SeptHardenberg 16:21No data—
Thu 17 SeptHardenberg 16:18No data—