Train Blauwnet A 31210 Oldenzaal – Zutphen

Oldenzaal 06:03 → Zutphen 06:53 Mon, Tue, Wed, Thu, Fri 0 h 50 min · 8 stops Blauwnet A

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 06:03 from Oldenzaal · Mon 9 Nov

Next departure 06:03 Monday · Oldenzaal
On-time · 30 days
79%
15/19 runs under 3 min
RT coverage: 0 full · 19 partial · 2 no data
On-time · 90 days
77%
17/22 runs under 3 min
RT coverage: 0 full · 22 partial · 42 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Thu 29 Oct Max en route +7 min · last fix heading to Lochem +7 min
  • Fri 30 Oct Max en route +5 min · last fix heading to Lochem +5 min
  • Tue 3 Nov Max en route +5 min · last fix heading to Lochem +5 min
  • Wed 7 Oct Max en route +5 min · last fix heading to Lochem +5 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Lochem +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 77% · 17
  • 3–10 min 23% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 80% T n=5
  • 60% W n=5
  • 80% T n=5
  • 75% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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
06:03on time on time
06:09— —
06:13 / 06:16— —
06:18— —
06:23— —
06:30 / 06:32— —
06:40— —
06: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
Fri 6 NovLochem 06:54No data—
Thu 5 NovLochem 06:57Partial coverage0 min—
Wed 4 NovLochem 06:54Partial coverage+4 min+4 min
Tue 3 NovLochem 06:54Partial coverage+5 min+5 min
Mon 2 NovLochem 06:54No data—
Fri 30 OctLochem 07:00Partial coverage+5 min+5 min
Thu 29 OctLochem 07:00Partial coverage+7 min+7 min
Wed 28 OctLochem 06:55Partial coverage0 min—
Tue 27 OctLochem 06:54Partial coverage+1 min—
Mon 26 OctLochem 06:56Partial coverage+1 min—
Fri 23 OctLochem 06:55Partial coverage0 min—
Thu 22 OctLochem 06:55Partial coverage+1 min—
Wed 21 OctLochem 06:55Partial coverage0 min—
Tue 20 OctLochem 06:57Partial coverage+1 min+1 min
Mon 19 OctLochem 06:54Partial coverage0 min—
Fri 16 OctLochem 06:54Partial coverage0 min—
Thu 15 OctLochem 06:55Partial coverage0 min—
Wed 14 OctLochem 06:54Partial coverage0 min—
Tue 13 OctLochem 06:55Partial coverage0 min—
Mon 12 OctLochem 06:55Partial coverage0 min—
Fri 9 OctLochem 06:55Partial coverage+2 min+2 min
Thu 8 OctLochem 06:55Partial coverage+2 min+2 min
Wed 7 OctLochem 06:58Partial coverage+5 min+5 min
Tue 6 OctLochem 06:55Partial coverage+2 min+2 min
Mon 5 OctLochem 06:56No data—
Fri 2 OctLochem 06:54No data—
Thu 1 OctLochem 06:55No data—
Wed 30 SeptLochem 06:55No data—
Tue 29 SeptLochem 06:55No data—
Mon 28 SeptLochem 06:54No data—