Train Eurobahn 20379 Hengelo – Bielefeld Hbf

Hengelo 17:34 → Bielefeld Hbf 19:47 Daily 2 h 13 min · 22 stops Eurobahn

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 17:34 from Hengelo · Tue 10 Nov

Next departure 17:34 today · Hengelo
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 6 full · 5 partial · 14 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 13 full · 5 partial · 64 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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
17:34on time on time
17:42≈ on time ≈ on time
17:52 / 17:56≈ on time ≈ on time
17:59≈ on time ≈ on time
18:04 / 18:05≈ on time ≈ on time
18:11 / 18:14≈ on time ≈ on time
18:20 / 18:21≈ on time ≈ on time
18:24≈ on time ≈ on time
18:27 / 18:28≈ on time ≈ on time
18:31 / 18:32≈ on time ≈ on time
18:43≈ on time ≈ on time
18:45 / 18:47≈ on time ≈ on time
18:53≈ on time ≈ on time
18:57≈ on time ≈ on time
19:01≈ on time ≈ on time
19:06≈ on time ≈ on time
19:11 / 19:12≈ on time ≈ on time
19:15 / 19:16≈ on time ≈ on time
19:20 / 19:21≈ on time ≈ on time
19:29 / 19:36≈ on time ≈ on time
19:40 / 19:41≈ on time ≈ on time
19: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
Mon 9 NovOldenzaal 17:54Partial coverage0 min—
Sun 8 NovOldenzaal 17:57Partial coverage0 min—
Sat 7 NovOldenzaal 17:57Partial coverage0 min—
Fri 6 NovOldenzaal 17:54Partial coverage0 min—
Thu 5 NovOldenzaal 17:54No data—
Wed 4 NovOldenzaal 17:54Partial coverage0 min—
Tue 3 NovOldenzaal 17:54No data—
Mon 2 NovOldenzaal 17:54No data—
Sun 1 NovOldenzaal 17:58No data—
Sat 31 OctOldenzaal 18:00No data—
Fri 30 OctOldenzaal 18:02No data—
Thu 29 OctOldenzaal 17:56No data—
Wed 28 OctOldenzaal 17:540 min—
Tue 27 OctOldenzaal 17:560 min—
Mon 26 OctOldenzaal 17:560 min—
Fri 23 OctOldenzaal 17:57No data—
Thu 22 OctOldenzaal 17:55No data—
Wed 21 OctOldenzaal 17:56No data—
Tue 20 OctOldenzaal 17:560 min—
Mon 19 OctOldenzaal 17:560 min—
Fri 16 OctOldenzaal 17:57No data—
Thu 15 OctOldenzaal 17:56No data—
Wed 14 OctOldenzaal 17:57No data—
Tue 13 OctOldenzaal 17:56No data—
Mon 12 OctOldenzaal 17:530 min—
Sun 11 OctOldenzaal 17:570 min—
Sat 10 OctOldenzaal 17:560 min—
Fri 9 OctOldenzaal 17:560 min—
Thu 8 OctOldenzaal 17:560 min—
Wed 7 OctOldenzaal 17:560 min—