Train Blauwnet A 31223 Zutphen – Oldenzaal

Zutphen 09:36 → Oldenzaal 10:27 Daily 0 h 51 min · 8 stops Blauwnet A

Running now · updated 09:44

Heading to Oldenzaal No data

Estimated arrival at Oldenzaal 10:27 · 26 km/h

  1. Zutphen09:36
  2. Lochem09:51
  3. Goor09:59
  4. Hengelo Gezondheidspark10:10
  5. Hengelo10:14
  6. Hengelo Oost10:20
  7. Oldenzaal10:27
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 4 full · 10 partial · 16 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 5 full · 12 partial · 72 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 Oldenzaal, 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • 100% W n=3
  • 100% T n=2
  • 100% F n=1
  • 100% S n=5
  • 100% S n=3

Stops and timetable

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

Last 90 days, 17 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 10Today
09:36on time on time
09:51≈ on time ≈ on time
09:59 / 10:00≈ on time ≈ +1 min
10:07≈ on time ≈ +1 min
10:10≈ on time ≈ +1 min
10:14 / 10:17≈ on time ≈ +1 min
10:20≈ on time ≈ +1 min
10:27on 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
Sun 8 NovLochem 09:44No data—
Sat 7 NovHengelo Oost 10:34Partial coverage0 min—
Fri 6 NovHengelo Oost 10:34No data—
Thu 5 NovHengelo Oost 10:37No data—
Wed 4 NovHengelo Oost 10:38Partial coverage+2 min+2 min
Tue 3 NovHengelo Oost 10:38Partial coverage0 min—
Mon 2 NovHengelo Oost 10:34Partial coverage0 min—
Sun 1 NovHengelo Oost 10:370 min—
Sat 31 OctHengelo Oost 10:36Partial coverage0 min—
Fri 30 OctHengelo Oost 10:38No data—
Thu 29 OctHengelo Oost 10:36Partial coverage0 min—
Wed 28 OctHengelo Oost 10:36Partial coverage0 min—
Tue 27 OctHengelo Oost 10:37No data—
Mon 26 OctHengelo Oost 10:37No data—
Sun 25 OctHengelo Gezondheidspark 10:30No data—
Sat 24 OctHengelo Gezondheidspark 10:26+1 min+2 min
Fri 23 OctHengelo Oost 10:37No data—
Thu 22 OctHengelo Oost 10:39No data—
Wed 21 OctHengelo Oost 10:34No data—
Tue 20 OctHengelo Oost 10:37No data—
Mon 19 OctHengelo Oost 10:37Partial coverage0 min—
Sun 18 OctHengelo Oost 10:370 min—
Sat 17 OctHengelo Oost 10:37Partial coverage0 min—
Fri 16 OctHengelo Oost 10:37No data—
Thu 15 OctHengelo Oost 10:36No data—
Wed 14 OctHengelo Oost 10:36No data—
Tue 13 OctHengelo Oost 10:37No data—
Mon 12 OctHengelo Oost 10:37No data—
Sun 11 OctHengelo Oost 10:38+1 min+1 min
Sat 10 OctHengelo Oost 10:37Partial coverage0 min—