Train Blauwnet A 31250 Oldenzaal – Zutphen

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

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

Next departure 16:03 today · Oldenzaal
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 6 full · 9 partial · 13 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 6 full · 12 partial · 68 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: +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

Worst days

  • Mon 5 Oct Max en route +8 min · last fix heading to Lochem +8 min

Distribution · 90 days

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

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

On-time by weekday

  • 67% M n=3
  • 100% T n=3
  • 100% W n=3
  • 100% T n=2
  • 100% F n=1
  • 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, 18 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:03on time on time
16:09≈ on time ≈ on time
16:13 / 16:16≈ on time ≈ on time
16:18≈ on time ≈ +1 min
16:23≈ on time ≈ +1 min
16:30 / 16:32≈ on time ≈ +1 min
16:40≈ on time ≈ +1 min
16:53on 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
Wed 4 NovLochem 16:54Partial coverage0 min—
Tue 3 NovLochem 16:54No data—
Mon 2 NovLochem 16:54No data—
Sun 1 NovLochem 16:54+2 min+2 min
Sat 31 OctLochem 16:55+2 min+2 min
Fri 30 OctLochem 16:55No data—
Thu 29 OctLochem 16:55Partial coverage0 min—
Wed 28 OctLochem 16:54Partial coverage0 min—
Tue 27 OctLochem 16:56Partial coverage0 min—
Mon 26 OctLochem 16:54No data—
Sun 25 OctLochem 16:55No data—
Sat 24 OctLochem 16:540 min—
Fri 23 OctLochem 16:55No data—
Thu 22 OctLochem 16:55No data—
Wed 21 OctLochem 16:55No data—
Tue 20 OctLochem 16:56Partial coverage0 min—
Mon 19 OctLochem 16:59Partial coverage0 min—
Sun 18 OctLochem 16:530 min—
Sat 17 OctLochem 16:54No data—
Fri 16 OctLochem 17:04No data—
Thu 15 OctLochem 16:55No data—
Wed 14 OctLochem 16:55No data—
Tue 13 OctLochem 16:55No data—
Mon 12 OctLochem 16:55Partial coverage0 min—
Sun 11 OctLochem 16:54+1 min—
Sat 10 OctLochem 16:540 min—
Fri 9 OctLochem 16:55Partial coverage0 min—
Thu 8 OctLochem 16:54Partial coverage+1 min—
Wed 7 OctLochem 16:54Partial coverage0 min—
Tue 6 OctLochem 16:54Partial coverage0 min—