Train Blauwnet A 31230 Oldenzaal – Zutphen

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 11:03 from Oldenzaal · Fri 6 Nov

Next departure 11:03 today · Oldenzaal
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 3 full · 8 partial · 14 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 3 full · 9 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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 100% · 12
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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
11:03on time on time
11:09— —
11:13 / 11:16— —
11:18— —
11:23— —
11:30 / 11:32— —
11:40— —
11: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
Thu 5 NovLochem 11:54No data—
Wed 4 NovLochem 11:54Partial coverage0 min—
Tue 3 NovLochem 11:54No data—
Mon 2 NovLochem 11:54No data—
Sat 31 OctLochem 11:54+1 min—
Fri 30 OctLochem 11:55No data—
Thu 29 OctLochem 11:55Partial coverage0 min—
Wed 28 OctLochem 11:55Partial coverage0 min—
Tue 27 OctLochem 11:55Partial coverage0 min—
Mon 26 OctLochem 11:55No data—
Sat 24 OctLochem 11:55+2 min+2 min
Fri 23 OctLochem 11:56No data—
Thu 22 OctLochem 12:00No data—
Wed 21 OctLochem 11:56No data—
Tue 20 OctLochem 11:55Partial coverage0 min—
Mon 19 OctLochem 11:55Partial coverage0 min—
Sat 17 OctLochem 11:54No data—
Fri 16 OctLochem 11:56No data—
Thu 15 OctLochem 11:54No data—
Wed 14 OctLochem 11:57No data—
Tue 13 OctLochem 11:55No data—
Mon 12 OctLochem 11:55No data—
Sat 10 OctLochem 11:54+1 min+1 min
Fri 9 OctLochem 11:54Partial coverage0 min—
Thu 8 OctLochem 11:54Partial coverage0 min—
Wed 7 OctHengelo Oost 12:01No data—
Tue 6 OctLochem 11:55Partial coverage0 min—
Mon 5 OctLochem 12:05No data—
Sat 3 OctLochem 11:55No data—
Fri 2 OctLochem 11:55No data—