Train Arriva 7992 Enschede – Hengelo

Enschede 00:04 → Hengelo 00:12 Daily 0 h 08 min · 3 stops Arriva

✓ Today’s run finished

Today, last fix heading to — at 00:14 +1 min

  1. Enschede00:04
  2. Enschede Kennispark00:08
  3. Hengelo00:12

Next service: tomorrow 00:04 from Enschede · Wed 18 Nov

Next departure 00:04 tomorrow · Enschede
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 11 full · 3 partial · 7 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 16 full · 5 partial · 16 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sat 14 Nov Max en route +8 min · last fix heading to — +7 min
  • Fri 30 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 19
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=5
  • 100% W n=3
  • 100% T n=1
  • 50% F n=2
  • 80% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 21 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
00:04on time on time
00:08≈ on time ≈ +2 min
00:12+1 min +3 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
Tue 17 Nov— 00:14+1 min+1 min
Sun 15 NovEnschede Kennispark 00:23Partial coverage+1 min+1 min
Sat 14 Nov— 01:09+7 min+8 min
Wed 11 Nov— 00:140 min—
Tue 10 Nov— 00:14+2 min+2 min
Sun 8 NovEnschede Kennispark 00:22Partial coverage0 min—
Sat 7 Nov— 01:04+2 min+3 min
Wed 4 Nov— 00:140 min—
Sun 1 NovEnschede Kennispark 00:22Partial coverage0 min—
Sat 31 Oct— 01:06No data—
Fri 30 Oct— 00:19+4 min+4 min
Thu 29 Oct— 00:14No data—
Wed 28 Oct— 00:160 min—
Tue 27 Oct— 00:160 min—
Mon 26 OctHeino 01:17No data—
Sun 25 Oct— 01:11No data—
Sat 24 Oct— 01:06+2 min+4 min
Fri 23 Oct— 00:22No data—
Thu 22 Oct— 00:16No data—
Wed 21 Oct— 00:15No data—
Tue 20 Oct— 00:17+1 min+1 min
Sun 18 OctEnschede Kennispark 00:22Partial coverage0 min—
Sat 17 OctHeino 01:06+3 min+4 min
Thu 15 Oct— 00:140 min—
Wed 14 Oct— 00:11No data—
Sun 11 OctEnschede Kennispark 00:22Partial coverage+1 min+1 min
Sat 10 Oct— 01:000 min—
Fri 9 Oct— 00:130 min—
Tue 6 OctEnschede Kennispark 00:150 min—
Sun 4 OctEnschede Kennispark 00:22No data—