Train Blauwnet A 31212 Oldenzaal – Zutphen

Oldenzaal 06:33 → Zutphen 07:23 Mon, Tue, Wed, Thu, Fri, Sun 0 h 50 min · 8 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Lochem at 07:27 +2 min

  1. Oldenzaal06:33
  2. Hengelo Oost06:39
  3. Hengelo06:43
  4. Delden06:53
  5. Goor07:00
  6. Lochem07:10
  7. Zutphen07:23

Next service: tomorrow 06:33 from Oldenzaal · Thu 19 Nov

Next departure 06:33 tomorrow · Oldenzaal
On-time · 30 days
77%
17/22 runs under 3 min
RT coverage: 3 full · 19 partial · 4 no data
On-time · 90 days
85%
28/33 runs under 3 min
RT coverage: 5 full · 28 partial · 43 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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 30 Oct Max en route +19 min · last fix heading to Lochem +19 min
  • Mon 9 Nov Max en route +6 min · last fix heading to Lochem +6 min
  • Thu 29 Oct Max en route +5 min · last fix heading to Lochem +4 min
  • Mon 16 Nov Max en route +4 min · last fix heading to Lochem +4 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Lochem +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 28
  • 3–10 min 12% · 4
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 60% M n=5
  • 86% T n=7
  • 100% W n=6
  • 80% T n=5
  • 80% F n=5
  • — S n=0
  • 100% S n=5

Stops and timetable

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

Last 90 days, 33 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
06:33on time on time
06:39≈ on time ≈ on time
06:43 / 06:46≈ on time ≈ on time
06:48≈ on time ≈ on time
06:53≈ on time ≈ on time
07:00 / 07:02≈ on time ≈ on time
07:10≈ on time ≈ on time
07:23on 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
Wed 18 NovLochem 07:27Partial coverage+2 min+2 min
Tue 17 NovLochem 07:24Partial coverage+3 min+3 min
Mon 16 NovLochem 07:29Partial coverage+4 min+4 min
Sun 15 NovLochem 07:24+1 min—
Fri 13 NovLochem 07:24Partial coverage+2 min+2 min
Thu 12 NovLochem 07:24Partial coverage+1 min—
Wed 11 NovLochem 07:24Partial coverage+1 min—
Tue 10 NovLochem 07:28Partial coverage+4 min+4 min
Mon 9 NovLochem 07:29Partial coverage+6 min+6 min
Sun 8 NovLochem 07:24+1 min—
Fri 6 NovLochem 07:25No data—
Thu 5 NovLochem 07:29No data—
Wed 4 NovLochem 07:24Partial coverage+1 min—
Tue 3 NovLochem 07:27Partial coverage+1 min—
Mon 2 NovLochem 07:24No data—
Sun 1 NovLochem 07:250 min—
Fri 30 OctLochem 07:43Partial coverage+19 min+19 min
Thu 29 OctLochem 07:28Partial coverage+4 min+5 min
Wed 28 OctLochem 07:26Partial coverage0 min—
Tue 27 OctLochem 07:25Partial coverage0 min—
Mon 26 OctLochem 07:25Partial coverage0 min—
Sun 25 OctLochem 07:47No data—
Fri 23 OctLochem 07:26Partial coverage+2 min+2 min
Thu 22 OctLochem 07:26Partial coverage0 min—
Wed 21 OctLochem 07:25Partial coverage0 min—
Tue 20 OctLochem 07:25Partial coverage0 min—
Mon 19 OctLochem 07:25Partial coverage0 min—
Sun 18 OctLochem 07:250 min—
Fri 16 OctLochem 07:25Partial coverage0 min—
Thu 15 OctLochem 07:25Partial coverage+1 min—