Train Blauwnet A 31228 Oldenzaal – Zutphen

Oldenzaal 10:33 → Zutphen 11:23 Daily 0 h 50 min · 8 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Lochem at 11:24 +1 min

  1. Oldenzaal10:33
  2. Hengelo Oost10:39
  3. Hengelo10:43
  4. Delden10:53
  5. Goor11:00
  6. Lochem11:10
  7. Zutphen11:23

Next service: tomorrow 10:33 from Oldenzaal · Mon 9 Nov

Next departure 10:33 tomorrow · Oldenzaal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 1 full · 11 partial · 18 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 1 full · 15 partial · 73 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

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

  • Early 0% · 0
  • On time 100% · 16
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 16 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
10:33on time on time
10:39— —
10:43 / 10:46— —
10:48— —
10:53— —
11:00 / 11:02— —
11:10— —
11:23— —

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
Sun 8 NovLochem 11:24Partial coverage+1 min—
Sat 7 NovLochem 11:24Partial coverage0 min—
Fri 6 NovLochem 11:24No data—
Thu 5 NovLochem 11:24No data—
Wed 4 NovLochem 11:24Partial coverage+2 min+2 min
Tue 3 NovLochem 11:24No data—
Mon 2 NovLochem 11:24No data—
Sun 1 NovLochem 11:26Partial coverage+1 min—
Sat 31 OctLochem 11:25Partial coverage0 min—
Fri 30 OctLochem 11:25No data—
Thu 29 OctLochem 11:25No data—
Wed 28 OctLochem 11:25Partial coverage0 min—
Tue 27 OctLochem 11:25Partial coverage0 min—
Mon 26 OctLochem 11:25No data—
Sun 25 OctLochem 11:26No data—
Sat 24 OctLochem 11:25+2 min+2 min
Fri 23 OctLochem 11:25No data—
Thu 22 OctLochem 11:29No data—
Wed 21 OctLochem 11:25No data—
Tue 20 OctLochem 11:25Partial coverage0 min—
Mon 19 OctLochem 11:25No data—
Sun 18 OctLochem 11:25Partial coverage0 min—
Sat 17 OctLochem 11:26No data—
Fri 16 OctLochem 11:25No data—
Thu 15 OctLochem 11:25No data—
Wed 14 OctLochem 11:24No data—
Tue 13 OctLochem 11:25No data—
Mon 12 OctLochem 11:26No data—
Sun 11 OctLochem 11:25Partial coverage0 min—
Sat 10 OctLochem 11:25Partial coverage+1 min—