Train Blauwnet A 31209 Goor – Oldenzaal

Goor 06:30 → Oldenzaal 06:57 Mon, Tue, Wed, Thu, Fri, Sat 0 h 27 min · 6 stops Blauwnet A

Running now · updated 06:16

Heading to Oldenzaal No data

Estimated arrival at Oldenzaal 06:57 · 51 km/h

  1. Goor06:30
  2. Delden06:37
  3. Hengelo Gezondheidspark06:40
  4. Hengelo06:44
  5. Hengelo Oost06:50
  6. Oldenzaal06:57
Open live map ↗ Full trip card
Open live card ↗
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 17 full · 3 partial · 5 no data
On-time · 90 days
96%
24/25 runs under 3 min
RT coverage: 21 full · 4 partial · 51 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

Worst days

  • Mon 19 Oct Max en route +5 min · last fix heading to Hengelo Oost +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 24
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 25 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
Goor
06:30on time on time
Delden
06:37≈ on time ≈ on time
Hengelo Gezondheidspark
06:40≈ on time ≈ on time
Hengelo
06:44 / 06:47≈ on time ≈ +1 min
Hengelo Oost
06:50≈ on time ≈ +1 min
Oldenzaal
06:57on 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
Mon 9 NovLochem 06:14No data—
Sat 7 NovHengelo Oost 07:08Partial coverage+1 min+2 min
Fri 6 NovHengelo Oost 07:07No data—
Thu 5 NovHengelo Oost 07:090 min—
Wed 4 NovHengelo Oost 07:040 min+1 min
Tue 3 NovHengelo Oost 07:070 min—
Mon 2 NovHengelo Oost 07:070 min—
Sat 31 OctHengelo Oost 07:06Partial coverage0 min—
Fri 30 OctHengelo Oost 07:040 min—
Thu 29 OctHengelo Oost 07:070 min+1 min
Wed 28 OctHengelo Oost 07:060 min—
Tue 27 OctHengelo Oost 07:04No data—
Mon 26 OctHengelo Oost 07:07+1 min+1 min
Sat 24 OctHengelo Gezondheidspark 06:56+1 min+2 min
Fri 23 OctHengelo Oost 07:07+1 min+1 min
Thu 22 OctHengelo Oost 07:06No data—
Wed 21 OctHengelo Oost 07:07+1 min+1 min
Tue 20 OctHengelo Oost 07:070 min+2 min
Mon 19 OctHengelo Oost 07:10+5 min+5 min
Sat 17 OctHengelo Oost 07:06Partial coverage0 min—
Fri 16 OctHengelo Oost 07:06No data—
Thu 15 OctHengelo Oost 07:060 min—
Wed 14 OctHengelo Oost 07:070 min—
Tue 13 OctHengelo Oost 07:060 min—
Mon 12 OctHengelo Oost 07:060 min—
Sat 10 OctHengelo Oost 07:06Partial coverage0 min—
Fri 9 OctHengelo Oost 07:060 min—
Thu 8 OctHengelo Oost 07:070 min—
Wed 7 OctHengelo Oost 07:08+1 min+2 min
Tue 6 OctHengelo Oost 07:060 min—