Train Eurobahn 20365 Hengelo – Bielefeld Hbf

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

✓ Today’s run finished

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

  1. Hengelo10:34
  2. Oldenzaal10:42
  3. Bad Bentheim10:52
  4. 422083710:59
  5. 422082211:24
  6. 414953611:43
  7. Bielefeld Hbf12:47

Next service: tomorrow 10:34 from Hengelo · Mon 9 Nov

Next departure 10:34 tomorrow · Hengelo
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 8 full · 4 partial · 14 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 12 full · 4 partial · 67 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

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

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

On-time by weekday

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

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
10:34on time on time
10:42≈ on time ≈ on time
10:52 / 10:56≈ on time ≈ on time
10:59≈ on time ≈ on time
11:04 / 11:05≈ on time ≈ on time
11:11 / 11:14≈ on time ≈ on time
11:20 / 11:21≈ on time ≈ on time
11:24≈ on time ≈ on time
11:27 / 11:28≈ on time ≈ on time
11:31 / 11:32≈ on time ≈ on time
11:43≈ on time ≈ on time
11:45 / 11:47≈ on time ≈ on time
11:53 / 11:54≈ on time ≈ on time
11:57 / 11:58≈ on time ≈ on time
12:01 / 12:02≈ on time ≈ on time
12:06≈ on time ≈ on time
12:11 / 12:12≈ on time ≈ on time
12:16≈ on time ≈ on time
12:20 / 12:21≈ on time ≈ on time
12:27 / 12:30≈ on time ≈ on time
12: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
Sun 8 NovOldenzaal 10:54Partial coverage0 min—
Sat 7 NovOldenzaal 10:57Partial coverage0 min—
Fri 6 NovOldenzaal 10:57No data—
Thu 5 NovOldenzaal 10:57No data—
Wed 4 NovOldenzaal 10:57Partial coverage0 min—
Tue 3 NovOldenzaal 10:59Partial coverage0 min—
Mon 2 NovOldenzaal 10:57No data—
Sun 1 NovOldenzaal 10:57No data—
Sat 31 OctOldenzaal 10:57No data—
Fri 30 OctOldenzaal 11:01No data—
Thu 29 OctOldenzaal 10:57No data—
Wed 28 OctOldenzaal 10:570 min—
Tue 27 OctOldenzaal 11:000 min—
Mon 26 OctOldenzaal 10:570 min—
Fri 23 OctOldenzaal 11:03No data—
Thu 22 OctOldenzaal 11:08No data—
Wed 21 OctOldenzaal 11:04No data—
Tue 20 OctOldenzaal 10:570 min—
Mon 19 OctOldenzaal 11:160 min—
Fri 16 OctOldenzaal 10:57No data—
Thu 15 OctOldenzaal 10:56No data—
Wed 14 OctOldenzaal 10:56No data—
Tue 13 OctOldenzaal 10:58No data—
Mon 12 OctOldenzaal 11:090 min—
Sun 11 OctOldenzaal 10:580 min—
Sat 10 OctOldenzaal 10:580 min—
Fri 9 OctOldenzaal 11:080 min—
Thu 8 OctOldenzaal 11:010 min—
Wed 7 OctOldenzaal 12:000 min—
Tue 6 OctOldenzaal 10:570 min—