Train Eurobahn 20372 Bielefeld Hbf – Hengelo

Bielefeld Hbf 14:12 → Hengelo 16:26 Daily 2 h 14 min · 22 stops Eurobahn

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 14:12 from Bielefeld Hbf · Sun 8 Nov

Next departure 14:12 today · Bielefeld Hbf
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 8 full · 2 partial · 15 no data
On-time · 90 days
73%
11/15 runs under 3 min
RT coverage: 13 full · 2 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+16min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Hengelo, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 7 Oct Max en route +27 min · last fix heading to Oldenzaal +27 min
  • Thu 8 Oct Max en route +21 min · last fix heading to Oldenzaal +21 min
  • Wed 4 Nov Max en route +9 min · last fix heading to Oldenzaal +9 min
  • Mon 5 Oct Max en route +4 min · last fix heading to Oldenzaal +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 73% · 11
  • 3–10 min 13% · 2
  • 10–30 min 13% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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
14:12on time +1 min
14:16 / 14:17≈ on time ≈ +1 min
14:23 / 14:32≈ on time ≈ +2 min
14:37 / 14:38≈ on time ≈ +4 min
14:42 / 14:43≈ on time ≈ +4 min
14:46 / 14:47≈ on time ≈ +5 min
14:53≈ on time ≈ +6 min
14:58≈ on time ≈ +6 min
15:01 / 15:02≈ on time ≈ +7 min
15:05 / 15:06≈ on time ≈ +7 min
15:12 / 15:14≈ on time ≈ +8 min
15:15 / 15:16≈ on time ≈ +9 min
15:26≈ on time ≈ +10 min
15:29 / 15:30≈ on time ≈ +10 min
15:33 / 15:34≈ on time ≈ +11 min
15:37≈ on time ≈ +11 min
15:46 / 15:48≈ on time ≈ +13 min
15:53 / 15:54≈ on time ≈ +13 min
15:59 / 16:00≈ on time ≈ +14 min
16:03 / 16:08≈ on time ≈ +15 min
16:18≈ on time ≈ +17 min
16:26on time +18 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
Sat 7 NovOldenzaal 16:32Partial coverage0 min—
Fri 6 NovOldenzaal 16:32No data—
Thu 5 NovOldenzaal 16:34No data—
Wed 4 NovOldenzaal 16:42Partial coverage+9 min+9 min
Tue 3 NovOldenzaal 16:32No data—
Mon 2 NovOldenzaal 16:37No data—
Sun 1 NovOldenzaal 16:33No data—
Sat 31 OctOldenzaal 16:32No data—
Fri 30 OctOldenzaal 16:35No data—
Thu 29 OctOldenzaal 16:33No data—
Wed 28 OctOldenzaal 16:350 min—
Tue 27 OctOldenzaal 16:330 min—
Mon 26 OctOldenzaal 16:320 min—
Fri 23 OctOldenzaal 16:32No data—
Thu 22 OctOldenzaal 16:33No data—
Wed 21 OctOldenzaal 16:47No data—
Tue 20 OctOldenzaal 16:480 min—
Mon 19 OctOldenzaal 16:330 min—
Fri 16 OctOldenzaal 16:33No data—
Thu 15 OctOldenzaal 16:32No data—
Wed 14 OctOldenzaal 16:34No data—
Tue 13 OctOldenzaal 16:33No data—
Mon 12 OctOldenzaal 16:320 min—
Sun 11 OctOldenzaal 16:400 min+5 min
Sat 10 OctOldenzaal 16:320 min—
Fri 9 OctOldenzaal 16:320 min—
Thu 8 OctOldenzaal 16:47+21 min+21 min
Wed 7 OctOldenzaal 16:57+27 min+27 min
Tue 6 OctOldenzaal 16:320 min—
Mon 5 OctOldenzaal 16:35+4 min+4 min