Train Blauwnet A 31211 Zutphen – Oldenzaal

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

✓ Today’s run finished

Today, last fix heading to Hengelo Oost at 07:37 No data

  1. Zutphen06:36
  2. Lochem06:51
  3. Goor06:59
  4. Hengelo Gezondheidspark07:10
  5. Hengelo07:14
  6. Hengelo Oost07:20
  7. Oldenzaal07:27

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

Next departure 06:36 tomorrow · Zutphen
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 6 full · 20 partial · 4 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 6 full · 22 partial · 61 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

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

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

On-time by weekday

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

Stops and timetable

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

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