Train Eurobahn 20359 Hengelo – Bielefeld Hbf

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

✓ Today’s run finished

Today, last fix heading to Oldenzaal at 07:54 0 min

  1. Hengelo07:34
  2. Oldenzaal07:42
  3. Bad Bentheim07:52
  4. 422083408:04
  5. 422082208:23
  6. Osnabrück Hbf08:45
  7. Bielefeld Hbf09:47

Next service: tomorrow 07:34 from Hengelo · Fri 6 Nov

Next departure 07:34 tomorrow · Hengelo
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 12 full · 2 partial · 12 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 13 full · 2 partial · 70 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=4
  • 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, 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
07:34on time on time
07:42≈ on time ≈ on time
07:52 / 07:56≈ on time ≈ on time
07:59≈ on time ≈ on time
08:04 / 08:05≈ on time ≈ on time
08:11 / 08:14≈ on time ≈ on time
08:20 / 08:21≈ on time ≈ on time
08:23 / 08:24≈ on time ≈ on time
08:27 / 08:28≈ on time ≈ on time
08:31 / 08:32≈ on time ≈ on time
08:43≈ on time ≈ on time
08:45 / 08:47≈ on time ≈ on time
08:52 / 08:53≈ on time ≈ on time
08:56 / 08:57≈ on time ≈ on time
09:00 / 09:01≈ on time ≈ on time
09:05≈ on time ≈ on time
09:11 / 09:12≈ on time ≈ on time
09:16≈ on time ≈ on time
09:20 / 09:21≈ on time ≈ on time
09:29 / 09:36≈ on time ≈ on time
09:40 / 09:41≈ on time ≈ on time
09: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
Thu 5 NovOldenzaal 07:54Partial coverage0 min—
Wed 4 NovOldenzaal 07:59Partial coverage0 min—
Tue 3 NovOldenzaal 07:59No data—
Mon 2 NovOldenzaal 07:57No data—
Sun 1 NovOldenzaal 07:56No data—
Sat 31 OctOldenzaal 07:56No data—
Fri 30 OctOldenzaal 08:22No data—
Thu 29 OctOldenzaal 07:57No data—
Wed 28 OctOldenzaal 07:570 min—
Tue 27 OctOldenzaal 07:580 min—
Mon 26 OctOldenzaal 07:570 min—
Fri 23 OctOldenzaal 07:590 min—
Thu 22 OctOldenzaal 07:56No data—
Wed 21 OctOldenzaal 08:020 min—
Tue 20 OctOldenzaal 08:090 min—
Mon 19 OctOldenzaal 07:56No data—
Fri 16 OctOldenzaal 07:57No data—
Thu 15 OctOldenzaal 07:57No data—
Wed 14 OctOldenzaal 07:56No data—
Tue 13 OctOldenzaal 07:59No data—
Mon 12 OctOldenzaal 07:590 min—
Sun 11 OctOldenzaal 07:560 min—
Sat 10 OctOldenzaal 07:570 min—
Fri 9 OctOldenzaal 07:570 min—
Thu 8 OctOldenzaal 07:570 min—
Wed 7 OctOldenzaal 07:570 min—
Tue 6 OctOldenzaal 07:570 min—
Mon 5 OctOldenzaal 07:59No data—
Sun 4 OctOldenzaal 07:57No data—
Sat 3 OctOldenzaal 07:56No data—