Train Blauwnet A 31266 Oldenzaal – Zutphen

Oldenzaal 20:03 → Zutphen 20:53 Daily 0 h 50 min · 8 stops Blauwnet A

It has not run yet today

Last recorded run: Sunday 8 November +2 min

Next service: tomorrow 20:03 from Oldenzaal · Tue 10 Nov

Next departure 20:03 tomorrow · Oldenzaal
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 2 full · 6 partial · 3 no data
On-time · 90 days
89%
8/9 runs under 3 min
RT coverage: 2 full · 7 partial · 23 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Zutphen, in minutes. One bar per run.

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

Worst days

  • Sun 11 Oct Max en route +5 min · last fix heading to Lochem +5 min

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 89% · 8
  • 3–10 min 11% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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
20:03on time on time
20:09— —
20:13 / 20:16— —
20:18— —
20:23— —
20:29 / 20:30— —
20:39— —
20: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
Sun 8 NovLochem 20:53Partial coverage+2 min+2 min
Sat 7 NovLochem 20:53Partial coverage+2 min+2 min
Sun 1 NovLochem 20:58Partial coverage0 min—
Sat 31 OctLochem 20:53Partial coverage0 min—
Thu 29 Oct— 20:580 min—
Sun 25 OctLochem 21:04No data—
Sat 24 OctLochem 21:02No data—
Tue 20 Oct— 21:030 min—
Sun 18 OctLochem 20:57Partial coverage+2 min+2 min
Sat 17 OctLochem 20:53No data—
Sun 11 OctLochem 20:55Partial coverage+5 min+5 min
Sat 10 OctLochem 20:53Partial coverage+2 min+2 min
Sun 4 OctLochem 20:54No data—
Sat 3 OctLochem 20:54No data—
Sun 27 SeptLochem 20:54No data—
Sat 26 SeptLochem 20:53No data—
Sun 20 SeptLochem 20:55No data—
Sat 19 SeptLochem 20:53No data—
Sun 13 SeptGoor 20:46No data—
Sat 12 SeptGoor 20:47No data—
Sun 6 SeptLochem 20:53No data—
Sat 5 SeptLochem 20:55No data—
Sun 30 AugLochem 20:53No data—
Sat 29 AugLochem 20:53No data—
Sun 23 AugLochem 20:54No data—
Sat 22 AugLochem 20:54No data—
Fri 21 AugGoor 20:44No data—
Sun 16 AugLochem 20:53No data—
Sat 15 AugLochem 20:53No data—
Fri 14 AugLochem 20:53No data—