Train Eurobahn 20373 Hengelo – Bielefeld Hbf

Hengelo 14:34 → Bielefeld Hbf 16:47 Daily 2 h 13 min · 21 stops Eurobahn

✓ Today’s run finished

Today, last fix heading to Oldenzaal at 14:57 No data

  1. Hengelo14:34
  2. Oldenzaal14:42
  3. Bad Bentheim14:52
  4. 422083714:59
  5. 422082215:24
  6. 414953615:43
  7. Bielefeld Hbf16:47

Next service: tomorrow 14:34 from Hengelo · Sat 7 Nov

Next departure 14:34 tomorrow · Hengelo
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 10 full · 3 partial · 13 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 13 full · 3 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Bielefeld Hbf, 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 4 Nov Max en route +15 min · last fix heading to Oldenzaal +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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:34on time on time
14:42≈ on time ≈ on time
14:52 / 14:56≈ on time ≈ on time
14:59≈ on time ≈ on time
15:04 / 15:05≈ on time ≈ on time
15:11 / 15:14≈ on time ≈ on time
15:20 / 15:21≈ on time ≈ on time
15:24≈ on time ≈ on time
15:27 / 15:28≈ on time ≈ on time
15:31 / 15:32≈ on time ≈ on time
15:43≈ on time ≈ on time
15:45 / 15:47≈ on time ≈ on time
15:53 / 15:54≈ on time ≈ on time
15:57 / 15:58≈ on time ≈ on time
16:01 / 16:02≈ on time ≈ on time
16:06≈ on time ≈ on time
16:11 / 16:12≈ on time ≈ on time
16:16≈ on time ≈ on time
16:20 / 16:21≈ on time ≈ on time
16:29 / 16:30≈ on time ≈ on time
16:47on time on time

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 NovOldenzaal 14:57No data—
Thu 5 NovOldenzaal 14:54No data—
Wed 4 NovOldenzaal 15:49Partial coverage+15 min+15 min
Tue 3 NovOldenzaal 14:54Partial coverage0 min—
Mon 2 NovOldenzaal 14:54Partial coverage0 min—
Sun 1 NovOldenzaal 14:59No data—
Sat 31 OctOldenzaal 15:03No data—
Fri 30 OctOldenzaal 14:56No data—
Thu 29 OctOldenzaal 15:02No data—
Wed 28 OctOldenzaal 14:580 min—
Tue 27 OctOldenzaal 15:160 min—
Mon 26 OctOldenzaal 14:570 min—
Fri 23 OctOldenzaal 14:57No data—
Thu 22 OctOldenzaal 14:56No data—
Wed 21 OctOldenzaal 15:05No data—
Tue 20 OctOldenzaal 15:000 min—
Mon 19 OctOldenzaal 14:570 min—
Fri 16 OctOldenzaal 15:11No data—
Thu 15 OctOldenzaal 14:57No data—
Wed 14 OctOldenzaal 14:57No data—
Tue 13 OctOldenzaal 14:57No data—
Mon 12 OctOldenzaal 14:560 min—
Sun 11 OctOldenzaal 14:580 min—
Sat 10 OctOldenzaal 14:560 min—
Fri 9 OctOldenzaal 14:560 min—
Thu 8 OctOldenzaal 15:120 min—
Wed 7 OctOldenzaal 15:010 min—
Tue 6 OctOldenzaal 14:560 min—
Mon 5 OctOldenzaal 14:570 min—
Sun 4 OctOldenzaal 14:57No data—