Train Blauwnet A 13849 Zwolle – Coevorden

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

It has not run yet today

Last recorded run: Tuesday 10 November +3 min

Next service: today 16:09 from Zwolle · Wed 11 Nov

Next departure 16:09 today · 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
92%
11/12 runs under 3 min
RT coverage: 0 full · 12 partial · 44 no data
Typical delay
0min
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

  • Tue 10 Nov Max en route +3 min · last fix heading to Hardenberg +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 11
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 75% T n=4
  • 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, 12 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:09on time on time
16:16— —
16:22 / 16:23— —
16:34— —
16:43— —

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
Tue 10 NovHardenberg 16:49Partial coverage+3 min+3 min
Mon 9 NovHardenberg 16:49Partial coverage+2 min+2 min
Fri 6 NovHardenberg 16:54No data—
Thu 5 NovHardenberg 16:53No data—
Wed 4 NovHardenberg 16:49Partial coverage0 min—
Tue 3 NovHardenberg 16:49No data—
Mon 2 NovHardenberg 16:49No data—
Fri 30 OctHardenberg 16:50No data—
Thu 29 OctEmmen Zuid 17:07No data—
Wed 28 OctHardenberg 16:48Partial coverage0 min—
Tue 27 OctHardenberg 16:49Partial coverage0 min—
Mon 26 OctHardenberg 16:50No data—
Fri 23 OctHardenberg 16:52No data—
Thu 22 OctHardenberg 16:48No data—
Wed 21 OctHardenberg 16:50No data—
Tue 20 OctHardenberg 16:49Partial coverage0 min—
Mon 19 OctHardenberg 16:49Partial coverage0 min—
Fri 9 OctHardenberg 16:49Partial coverage0 min—
Thu 8 OctHardenberg 16:51Partial coverage+3 min+3 min
Wed 7 OctHardenberg 16:51Partial coverage+3 min+3 min
Tue 6 OctHardenberg 16:49Partial coverage+1 min+1 min
Mon 5 OctHardenberg 16:48Partial coverage0 min—
Fri 2 OctHardenberg 16:49No data—
Thu 1 OctHardenberg 16:49No data—
Wed 30 SeptHardenberg 16:50No data—
Tue 29 SeptHardenberg 16:50No data—
Mon 28 SeptHardenberg 16:50No data—
Fri 25 SeptHardenberg 16:49No data—
Thu 24 SeptHardenberg 16:48No data—
Wed 23 SeptHardenberg 16:50No data—