Train Blauwnet A 31258 Oldenzaal – Zutphen

Oldenzaal 18:03 → Zutphen 18:52 Daily 0 h 49 min · 8 stops Blauwnet A

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 18:03 from Oldenzaal · Sun 8 Nov

Next departure 18:03 today · Oldenzaal
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 11 full · 3 partial · 15 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 14 full · 3 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Fri 23 Oct Max en route +4 min · last fix heading to Lochem +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=1
  • 100% W n=2
  • 100% T n=1
  • 67% F n=3
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 17 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
18:03on time on time
18:09≈ on time ≈ on time
18:13 / 18:16≈ on time ≈ on time
18:18≈ on time ≈ +1 min
18:23≈ on time ≈ +1 min
18:30 / 18:32≈ on time ≈ +1 min
18:40≈ on time ≈ +2 min
18:52on time +2 min

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
Sat 7 NovLochem 18:54Partial coverage0 min—
Fri 6 NovLochem 18:54+2 min+2 min
Thu 5 NovHengelo Oost 18:23No data—
Wed 4 NovHengelo Oost 18:23No data—
Tue 3 NovHengelo Oost 18:23No data—
Mon 2 NovHengelo Oost 18:23No data—
Sun 1 NovLochem 18:54+2 min+2 min
Sat 31 OctLochem 18:55Partial coverage0 min—
Fri 30 OctLochem 18:54No data—
Thu 29 Oct— 18:560 min—
Wed 28 OctHengelo Oost 18:230 min—
Tue 27 OctOldenzaal 18:17No data—
Mon 26 OctHengelo Oost 18:230 min—
Sun 25 OctLochem 18:56No data—
Sat 24 OctLochem 18:56No data—
Fri 23 OctLochem 18:53+4 min+4 min
Thu 22 OctLochem 18:54No data—
Wed 21 OctLochem 18:54No data—
Tue 20 OctLochem 18:560 min—
Mon 19 OctLochem 18:570 min—
Sun 18 OctLochem 18:540 min—
Sat 17 OctLochem 18:55No data—
Fri 16 OctLochem 18:55No data—
Thu 15 OctDelden 18:37No data—
Wed 14 OctLochem 18:54No data—
Tue 13 OctLochem 18:50No data—
Mon 12 OctLochem 18:540 min—
Sun 11 OctLochem 18:540 min+1 min
Sat 10 OctLochem 18:55Partial coverage0 min—
Fri 9 OctGoor 18:460 min—