Train Eurobahn 20358 Bielefeld Hbf – Hengelo

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

Running now · updated 09:14

Heading to Hengelo 0 min

Estimated arrival at Hengelo 09:26

  1. Bielefeld Hbf07:12
  2. 422082807:41
  3. 422083107:57
  4. 416146908:15
  5. 422082308:33
  6. 422083608:59
  7. Hengelo09:26

Today it is running no worse than usual: typical arrival delay is 0 min; 94% of the last 16 runs arrived on time.

On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 12 full · 4 partial · 10 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 13 full · 4 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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 +19 min · last fix heading to Oldenzaal +19 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
07:12on time on time
07:16 / 07:17≈ on time ≈ on time
07:23 / 07:32≈ on time ≈ on time
07:36 / 07:37≈ on time ≈ on time
07:41 / 07:42≈ on time ≈ on time
07:45 / 07:46≈ on time ≈ on time
07:52≈ on time ≈ on time
07:57≈ on time ≈ +1 min
08:00 / 08:01≈ on time ≈ +1 min
08:04 / 08:05≈ on time ≈ +1 min
08:12 / 08:14≈ on time ≈ +1 min
08:15 / 08:16≈ on time ≈ +1 min
08:26 / 08:27≈ on time ≈ +1 min
08:30≈ on time ≈ +1 min
08:33 / 08:34≈ on time ≈ +1 min
08:38≈ on time ≈ +1 min
08:46 / 08:49≈ on time ≈ +1 min
08:53 / 08:54≈ on time ≈ +1 min
08:59 / 09:00≈ on time ≈ +1 min
09:03 / 09:08≈ on time ≈ +1 min
09:18≈ on time ≈ +2 min
09:26on time +2 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
Thu 5 NovOldenzaal 09:09Partial coverage0 min—
Wed 4 NovOldenzaal 09:34Partial coverage+2 min+3 min
Tue 3 NovOldenzaal 09:34Partial coverage0 min—
Mon 2 NovOldenzaal 09:33Partial coverage0 min—
Sun 1 NovOldenzaal 09:32No data—
Sat 31 OctOldenzaal 09:32No data—
Fri 30 OctOldenzaal 09:32No data—
Thu 29 OctOldenzaal 09:34No data—
Wed 28 OctOldenzaal 09:380 min—
Tue 27 OctOldenzaal 09:320 min—
Mon 26 OctOldenzaal 09:350 min—
Fri 23 OctOldenzaal 09:340 min—
Thu 22 OctOldenzaal 09:32No data—
Wed 21 OctOldenzaal 09:34No data—
Tue 20 OctOldenzaal 09:320 min—
Mon 19 OctOldenzaal 09:330 min—
Fri 16 OctOldenzaal 09:32No data—
Thu 15 OctOldenzaal 09:39No data—
Wed 14 OctOldenzaal 09:34No data—
Tue 13 OctOldenzaal 09:32No data—
Mon 12 OctOldenzaal 09:410 min—
Sun 11 OctOldenzaal 09:320 min—
Sat 10 OctOldenzaal 09:320 min—
Fri 9 OctOldenzaal 09:33+1 min+1 min
Thu 8 OctOldenzaal 09:34+2 min+2 min
Wed 7 OctOldenzaal 09:51+19 min+19 min
Tue 6 OctOldenzaal 09:320 min—
Mon 5 OctOldenzaal 09:37No data—
Sun 4 OctOldenzaal 09:32No data—
Sat 3 OctOldenzaal 09:33No data—