Train Blauwnet A 31214 Oldenzaal – Zutphen

Oldenzaal 07:03 → Zutphen 07:52 Mon, Tue, Wed, Thu, Fri, Sat 0 h 49 min · 8 stops Blauwnet A

It does not run today

Last recorded run: Saturday 7 November 0 min

Next service: tomorrow 07:03 from Oldenzaal · Mon 9 Nov

Next departure 07:03 tomorrow · Oldenzaal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 10 full · 4 partial · 10 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 14 full · 4 partial · 56 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

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

  • Early 0% · 0
  • On time 100% · 18
  • 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=5
  • 100% T n=2
  • 100% F n=2
  • 100% S n=5
  • — S n=0

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
07:03on time on time
07:09≈ on time ≈ on time
07:13 / 07:16≈ on time ≈ on time
07:18≈ on time ≈ on time
07:23≈ on time ≈ on time
07:30 / 07:31≈ on time ≈ on time
07:40≈ on time ≈ +1 min
07:52on time +1 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 07:54Partial coverage0 min—
Fri 6 NovLochem 07:54No data—
Thu 5 NovLochem 07:58No data—
Wed 4 NovLochem 07:54+1 min—
Tue 3 NovLochem 07:540 min—
Mon 2 NovLochem 07:54No data—
Sat 31 OctLochem 07:54Partial coverage+2 min+2 min
Fri 30 OctLochem 07:54No data—
Thu 29 OctLochem 07:540 min—
Wed 28 OctLochem 07:550 min—
Mon 26 OctLochem 07:56+1 min—
Sat 24 OctLochem 07:550 min—
Fri 23 OctLochem 07:550 min—
Thu 22 OctLochem 07:55No data—
Wed 21 OctLochem 07:550 min—
Tue 20 OctLochem 07:560 min—
Mon 19 OctLochem 07:54No data—
Sat 17 OctLochem 07:55Partial coverage+1 min—
Fri 16 OctLochem 07:55No data—
Thu 15 OctLochem 07:55No data—
Wed 14 OctLochem 07:550 min—
Tue 13 OctLochem 07:56No data—
Mon 12 OctLochem 07:55No data—
Sat 10 OctLochem 07:54Partial coverage+1 min—
Fri 9 OctLochem 07:550 min—
Thu 8 OctLochem 07:55+1 min—
Wed 7 OctLochem 07:56+1 min—
Tue 6 OctLochem 07:56+1 min—
Sat 3 OctLochem 07:54No data—
Fri 2 OctLochem 07:55No data—