Train Blauwnet A 31261 Zutphen – Oldenzaal

Zutphen 19:06 → Oldenzaal 19:57 Daily 0 h 51 min · 8 stops Blauwnet A

It has not run yet today

Last recorded run: Sunday 1 November 0 min

Next service: tomorrow 19:06 from Zutphen · Sat 7 Nov

Next departure 19:06 tomorrow · Zutphen
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 2 full · 6 partial · 6 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 2 full · 6 partial · 35 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 8 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
19:06on time on time
19:21— —
19:29 / 19:30— —
19:37— —
19:40— —
19:44 / 19:47— —
19:50— —
19:57— —

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 1 NovHengelo Oost 20:07Partial coverage0 min+2 min
Sat 31 OctHengelo Oost 20:06Partial coverage0 min—
Thu 29 Oct— 20:000 min—
Sun 25 OctHengelo Gezondheidspark 19:55No data—
Sat 24 OctHengelo Gezondheidspark 19:59No data—
Fri 23 OctLochem 19:35Partial coverage+1 min+1 min
Tue 20 Oct— 20:010 min—
Mon 19 Oct— 19:55No data—
Sun 18 OctHengelo Oost 20:06Partial coverage0 min—
Sat 17 OctHengelo Oost 20:06No data—
Fri 16 OctHengelo Oost 20:04No data—
Wed 14 OctHengelo 20:01No data—
Sun 11 OctHengelo Oost 20:06Partial coverage0 min—
Sat 10 OctHengelo Oost 20:06Partial coverage0 min—
Sun 4 OctHengelo Oost 20:07No data—
Sat 3 OctHengelo Oost 20:07No data—
Sun 27 SeptHengelo Oost 20:08No data—
Sat 26 SeptHengelo Oost 20:06No data—
Sun 20 SeptHengelo Oost 20:06No data—
Sat 19 SeptHengelo Oost 20:06No data—
Sun 13 SeptHengelo Oost 20:06No data—
Sat 12 SeptHengelo Oost 20:06No data—
Sun 6 SeptHengelo Oost 20:08No data—
Sat 5 SeptHengelo Oost 20:06No data—
Sun 30 AugHengelo Oost 20:09No data—
Sat 29 AugHengelo Oost 20:06No data—
Fri 28 AugGoor 19:44No data—
Wed 26 AugZutphen 19:20No data—
Sun 23 AugHengelo Oost 20:06No data—
Sat 22 AugHengelo Oost 20:06No data—