Train Blauwnet A 13815 Zwolle – Coevorden

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

✓ Today’s run finished

Today, last fix heading to Hardenberg at 08:18 0 min

  1. Zwolle07:39
  2. Dalfsen07:46
  3. Ommen07:52
  4. Hardenberg08:04
  5. Coevorden08:13

Next service: tomorrow 07:39 from Zwolle · Thu 12 Nov

Next departure 07:39 tomorrow · Zwolle
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 0 full · 10 partial · 8 no data
On-time · 90 days
79%
11/14 runs under 3 min
RT coverage: 0 full · 14 partial · 42 no data
Typical delay
+1min
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 Coevorden, in minutes. One bar per run.

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

Worst days

  • Fri 9 Oct Max en route +4 min · last fix heading to Hardenberg +4 min
  • Wed 7 Oct Max en route +3 min · last fix heading to Hardenberg +3 min
  • Tue 10 Nov Max en route +3 min · last fix heading to Hardenberg +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 11
  • 3–10 min 21% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 75% T n=4
  • 75% W n=4
  • 100% T n=1
  • 50% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 14 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
07:39on time on time
07:46— —
07:52 / 07:53— —
08:04— —
08: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 11 NovHardenberg 08:18Partial coverage0 min—
Tue 10 NovHardenberg 08:19Partial coverage+3 min+3 min
Mon 9 NovHardenberg 08:19Partial coverage+1 min+1 min
Fri 6 NovHardenberg 08:22No data—
Thu 5 NovHardenberg 08:22No data—
Wed 4 NovHardenberg 08:19Partial coverage+1 min+1 min
Tue 3 NovHardenberg 08:19No data—
Mon 2 NovHardenberg 08:19No data—
Fri 30 OctHardenberg 08:18Partial coverageNo data—
Thu 29 OctHardenberg 08:20No data—
Wed 28 OctHardenberg 08:18Partial coverage0 min—
Tue 27 OctHardenberg 08:19Partial coverage0 min—
Mon 26 OctHardenberg 08:22Partial coverage+2 min+2 min
Fri 23 OctHardenberg 08:19Partial coverage0 min—
Thu 22 OctHardenberg 08:20No data—
Wed 21 OctHardenberg 08:23No data—
Tue 20 OctHardenberg 08:21Partial coverage0 min—
Mon 19 OctHardenberg 08:20Partial coverage0 min—
Fri 9 OctHardenberg 08:23Partial coverage+4 min+4 min
Thu 8 OctHardenberg 08:20Partial coverage+2 min+2 min
Wed 7 OctHardenberg 08:22Partial coverage+3 min+3 min
Tue 6 OctHardenberg 08:20Partial coverage+2 min+2 min
Mon 5 OctHardenberg 08:21No data—
Fri 2 OctHardenberg 08:19No data—
Thu 1 OctHardenberg 08:20No data—
Wed 30 SeptHardenberg 08:19No data—
Tue 29 SeptHardenberg 08:22No data—
Mon 28 SeptHardenberg 08:20No data—
Fri 25 SeptHardenberg 08:19No data—
Thu 24 SeptHardenberg 08:20No data—