Train Blauwnet A 31215 Zutphen – Oldenzaal

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

Running now · updated 08:01

Heading to Oldenzaal No data

Estimated arrival at Oldenzaal 08:27 · 98 km/h

  1. Zutphen07:36
  2. Lochem07:51
  3. Goor07:59
  4. Hengelo Gezondheidspark08:10
  5. Hengelo08:14
  6. Hengelo Oost08:20
  7. Oldenzaal08:27
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 3 full · 13 partial · 14 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 3 full · 14 partial · 72 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Worst days

  • Fri 9 Oct Max en route +7 min · last fix heading to Hengelo Oost +5 min
  • Tue 6 Oct Max en route +3 min · last fix heading to Hengelo Oost +3 min

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 88% · 15
  • 3–10 min 12% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
07:36on time on time
07:51— —
07:59 / 08:00— —
08:07— —
08:10— —
08:14 / 08:17— —
08:20— —
08:27— —

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
Thu 5 NovGoor 07:59No data—
Wed 4 NovHengelo Oost 08:37Partial coverage0 min—
Tue 3 NovHengelo Oost 08:37No data—
Mon 2 NovHengelo Oost 08:37No data—
Sun 1 NovHengelo Oost 08:370 min—
Sat 31 OctHengelo Oost 08:37Partial coverage0 min—
Fri 30 OctHengelo Oost 08:34Partial coverageNo data—
Thu 29 OctHengelo Oost 08:38Partial coverage0 min—
Wed 28 OctHengelo Oost 08:37Partial coverage0 min—
Tue 27 OctHengelo Oost 08:36Partial coverage0 min—
Mon 26 OctHengelo Oost 08:39Partial coverage0 min—
Sun 25 OctHengelo Gezondheidspark 08:32No data—
Sat 24 OctHengelo Gezondheidspark 08:25+1 min—
Fri 23 OctHengelo Oost 08:40No data—
Thu 22 OctHengelo Oost 08:37No data—
Wed 21 OctHengelo Oost 08:38No data—
Tue 20 OctHengelo Oost 08:45Partial coverage0 min—
Mon 19 OctHengelo Oost 08:40Partial coverage0 min—
Sun 18 OctHengelo Oost 08:37No data—
Sat 17 OctHengelo Oost 08:36Partial coverage+1 min+1 min
Fri 16 OctHengelo Oost 08:37No data—
Thu 15 OctHengelo Oost 08:37No data—
Wed 14 OctHengelo Oost 08:37No data—
Tue 13 OctHengelo Oost 08:36No data—
Mon 12 OctHengelo Oost 08:36No data—
Sun 11 OctHengelo Oost 08:380 min—
Sat 10 OctHengelo Oost 08:37Partial coverage0 min—
Fri 9 OctHengelo Oost 08:42Partial coverage+5 min+7 min
Thu 8 OctHengelo Oost 08:36Partial coverage0 min—
Wed 7 OctHengelo Oost 08:39Partial coverage+1 min+1 min