Train Blauwnet A 31242 Oldenzaal – Zutphen

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

✓ Today’s run finished

Today, last fix heading to Lochem at 14:54 No data

  1. Oldenzaal14:03
  2. Hengelo Oost14:09
  3. Hengelo14:13
  4. Delden14:23
  5. Goor14:30
  6. Lochem14:40
  7. Zutphen14:53

Next service: tomorrow 14:03 from Oldenzaal · Sat 7 Nov

Next departure 14:03 tomorrow · Oldenzaal
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 3 full · 9 partial · 14 no data
On-time · 90 days
87%
13/15 runs under 3 min
RT coverage: 3 full · 12 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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 +16 min · last fix heading to Lochem +16 min
  • Sat 10 Oct Max en route +3 min · last fix heading to Lochem +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 13
  • 3–10 min 7% · 1
  • 10–30 min 7% · 1
  • 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
  • 67% S n=3
  • — S n=0

Stops and timetable

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

Last 90 days, 15 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
14:03on time on time
14:09— —
14:13 / 14:16— —
14:18— —
14:23— —
14:30 / 14:32— —
14:40— —
14: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 14:54No data—
Thu 5 NovLochem 14:54No data—
Wed 4 NovLochem 14:54Partial coverage0 min—
Tue 3 NovLochem 14:54Partial coverage0 min—
Mon 2 NovLochem 14:54Partial coverage0 min—
Sat 31 OctLochem 14:53+2 min+2 min
Fri 30 OctLochem 14:55No data—
Thu 29 OctLochem 14:55Partial coverage0 min—
Wed 28 OctLochem 14:55Partial coverage0 min—
Tue 27 OctLochem 14:59No data—
Mon 26 OctLochem 14:55No data—
Sat 24 OctLochem 14:550 min—
Fri 23 OctLochem 14:56No data—
Thu 22 OctLochem 14:55No data—
Wed 21 OctLochem 14:54No data—
Tue 20 OctLochem 14:55Partial coverage0 min—
Mon 19 OctLochem 14:55Partial coverage0 min—
Sat 17 OctLochem 14:54No data—
Fri 16 OctLochem 14:55No data—
Thu 15 OctLochem 14:55No data—
Wed 14 OctLochem 14:56No data—
Tue 13 OctLochem 14:55No data—
Mon 12 OctLochem 14:55No data—
Sat 10 OctLochem 14:55+3 min+3 min
Fri 9 OctLochem 14:55Partial coverage0 min—
Thu 8 OctLochem 14:55Partial coverage0 min—
Wed 7 OctLochem 14:55Partial coverage0 min—
Tue 6 OctLochem 14:56Partial coverage+2 min+2 min
Mon 5 OctLochem 15:11Partial coverage+16 min+16 min
Sat 3 OctLochem 14:53No data—