Train Blauwnet A 13832 Coevorden – Zwolle

Coevorden 08:47 → Zwolle 09:23 Mon, Tue, Wed, Thu, Fri 0 h 36 min · 5 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Dalfsen at 09:29 0 min

  1. Coevorden08:47
  2. Hardenberg08:56
  3. Ommen09:06
  4. Dalfsen09:15
  5. Zwolle09:23

Next service: tomorrow 08:47 from Coevorden · Tue 10 Nov

Next departure 08:47 tomorrow · Coevorden
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 0 full · 6 partial · 10 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 45 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

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
08:47on time on time
08:56— —
09:06 / 09:08— —
09:15— —
09:23— —

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
Mon 9 NovDalfsen 09:29Partial coverage0 min—
Fri 6 NovDalfsen 09:37No data—
Thu 5 NovDalfsen 09:29No data—
Wed 4 NovDalfsen 09:29Partial coverage0 min—
Tue 3 NovDalfsen 09:29No data—
Mon 2 NovDalfsen 09:29No data—
Fri 30 OctDalfsen 09:29No data—
Thu 29 OctDalfsen 12:06No data—
Wed 28 OctDalfsen 09:29Partial coverage0 min—
Tue 27 OctDalfsen 09:29Partial coverage0 min—
Mon 26 OctDalfsen 09:29No data—
Fri 23 OctDalfsen 09:30No data—
Thu 22 OctDalfsen 09:29No data—
Wed 21 OctDalfsen 09:33No data—
Tue 20 OctDalfsen 09:29Partial coverage0 min—
Mon 19 OctDalfsen 09:29Partial coverage0 min—
Fri 9 OctDalfsen 09:31Partial coverage0 min—
Thu 8 OctDalfsen 09:29Partial coverage0 min—
Wed 7 OctDalfsen 09:31Partial coverage+2 min+2 min
Tue 6 OctDalfsen 09:29Partial coverage0 min—
Mon 5 OctDalfsen 09:29No data—
Fri 2 OctDalfsen 09:29No data—
Thu 1 OctDalfsen 09:29No data—
Wed 30 SeptDalfsen 09:29No data—
Tue 29 SeptDalfsen 09:29No data—
Mon 28 SeptDalfsen 09:29No data—
Fri 25 SeptDalfsen 09:29No data—
Thu 24 SeptDalfsen 09:29No data—
Wed 23 SeptDalfsen 09:30No data—
Tue 22 SeptDalfsen 09:29No data—