Train Arriva 30756 Doetinchem – Arnhem Centraal

Doetinchem 18:38 → Arnhem Centraal 19:10 Daily 0 h 32 min · 9 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 18:38 from Doetinchem · Thu 5 Nov

Next departure 18:38 today · Doetinchem
On-time · 30 days
82%
9/11 runs under 3 min
RT coverage: 9 full · 2 partial · 9 no data
On-time · 90 days
85%
11/13 runs under 3 min
RT coverage: 11 full · 2 partial · 29 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Arnhem Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 23 Oct Max en route +6 min · last fix heading to Arnhem Velperpoort +6 min
  • Thu 8 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 11
  • 3–10 min 15% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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
18:38on time +1 min
18:41≈ on time ≈ +1 min
18:44 / 18:45≈ on time ≈ +1 min
18:50≈ +1 min ≈ +2 min
18:54 / 18:55≈ +1 min ≈ +3 min
18:59≈ +1 min ≈ +4 min
19:03≈ +1 min ≈ +4 min
19:07≈ +1 min ≈ +4 min
19:10+1 min +5 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
Wed 4 Nov— 19:14No data—
Mon 2 Nov— 19:14+1 min+1 min
Sun 1 NovArnhem Velperpoort 19:09+2 min+2 min
Sat 31 OctArnhem Velperpoort 19:08+1 min+1 min
Fri 30 OctDidam 19:12No data—
Thu 29 Oct— 19:16+2 min+2 min
Tue 27 Oct— 19:180 min—
Mon 26 Oct— 19:15No data—
Fri 23 OctArnhem Velperpoort 19:22+6 min+6 min
Thu 22 OctWehl 19:13No data—
Wed 21 OctDoetinchem 19:14No data—
Tue 20 OctWehl 19:170 min—
Mon 19 OctDoetinchem De Huet 19:13Partial coverage0 min—
Fri 16 OctArnhem Velperpoort 19:21No data—
Thu 15 Oct— 19:12No data—
Wed 14 OctArnhem Velperpoort 19:21No data—
Tue 13 OctDoetinchem 19:20No data—
Mon 12 OctWehl 19:08Partial coverage0 min—
Fri 9 Oct— 19:15+3 min+3 min
Thu 8 Oct— 19:16+5 min+5 min
Tue 6 Oct— 19:130 min—
Mon 5 Oct— 19:130 min—
Fri 2 OctWehl 18:59No data—
Fri 18 SeptWehl 18:59No data—
Fri 11 SeptDidam 19:04No data—
Fri 4 SeptDidam 19:04No data—
Fri 28 AugArnhem Velperpoort 19:21No data—
Thu 27 AugWehl 18:59No data—
Wed 26 AugArnhem Velperpoort 19:21No data—
Tue 25 AugDidam 19:04No data—