Train Blauwnet A 13862 Coevorden – Zwolle

Coevorden 16:17 → Zwolle 16:53 Mon, Tue, Wed, Thu, Fri 0 h 36 min · 5 stops Blauwnet A

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 16:17 from Coevorden · Thu 5 Nov

Next departure 16:17 today · Coevorden
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%
9/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
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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 100% · 9
  • 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=2
  • 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, 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:17on time +1 min
16:26— —
16:36 / 16:38— —
16:45— —
16:53— —

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 NovDalfsen 16:59Partial coverage0 min—
Tue 3 NovDalfsen 16:59No data—
Mon 2 NovDalfsen 16:59No data—
Fri 30 OctDalfsen 16:59No data—
Thu 29 OctDalfsen 16:59No data—
Wed 28 OctDalfsen 16:59Partial coverage0 min—
Tue 27 OctDalfsen 16:59Partial coverage0 min—
Mon 26 OctDalfsen 17:06No data—
Fri 23 OctDalfsen 17:00No data—
Thu 22 OctDalfsen 17:06No data—
Wed 21 OctDalfsen 16:59No data—
Tue 20 OctDalfsen 16:59Partial coverage0 min—
Mon 19 OctDalfsen 16:59Partial coverage0 min—
Fri 9 OctDalfsen 16:59Partial coverage0 min—
Thu 8 OctDalfsen 17:01Partial coverage+1 min+1 min
Wed 7 OctDalfsen 17:01Partial coverage0 min+1 min
Tue 6 OctDalfsen 16:59No data—
Mon 5 OctDalfsen 16:59Partial coverage0 min—
Fri 2 OctDalfsen 16:59No data—
Thu 1 OctDalfsen 17:00No data—
Wed 30 SeptDalfsen 16:59No data—
Tue 29 SeptDalfsen 16:59No data—
Mon 28 SeptDalfsen 17:00No data—
Fri 25 SeptDalfsen 16:59No data—
Thu 24 SeptDalfsen 16:59No data—
Wed 23 SeptDalfsen 16:59No data—
Tue 22 SeptDalfsen 16:59No data—
Mon 21 SeptDalfsen 16:59No data—
Fri 18 SeptDalfsen 17:06No data—
Thu 17 SeptHardenberg 16:40No data—