Train Arriva 30479 Apeldoorn – Winterswijk

Apeldoorn 23:22 → Winterswijk 00:11 Daily 0 h 49 min · 7 stops Arriva

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 23:22 from Apeldoorn · Fri 6 Nov

Next departure 23:22 today · Apeldoorn
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 11 full · 3 partial · 12 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 12 full · 3 partial · 24 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 Winterswijk, in minutes. One bar per run.

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

Worst days

  • Mon 12 Oct Max en route +6 min · last fix heading to — +5 min

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 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 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
23:22on time on time
23:35 / 23:37≈ on time ≈ +1 min
23:44 / 23:45≈ on time ≈ +2 min
23:51≈ on time ≈ +2 min
23:59 / 00:00≈ on time ≈ +2 min
00:07≈ on time ≈ +2 min
00:11on 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 Nov— 00:14No data—
Wed 4 Nov— 00:14+1 min+1 min
Mon 2 Nov— 00:14+2 min+2 min
Sun 1 NovWinterswijk West 00:19Partial coverage0 min—
Sat 31 OctApeldoorn 00:11No data—
Fri 30 Oct— 00:13No data—
Thu 29 Oct— 00:140 min+1 min
Wed 28 Oct— 00:130 min—
Mon 26 Oct— 00:110 min—
Sun 25 OctWinterswijk West 00:25No data—
Sat 24 Oct— 00:20No data—
Fri 23 Oct— 00:130 min—
Thu 22 Oct— 00:28No data—
Wed 21 Oct— 00:14No data—
Tue 20 Oct— 00:16No data—
Sun 18 OctWinterswijk West 00:21Partial coverage0 min—
Sat 17 OctWinterswijk West 00:22No data—
Fri 16 Oct— 00:15+2 min+3 min
Thu 15 Oct— 00:11No data—
Wed 14 Oct— 00:12No data—
Tue 13 Oct— 00:17No data—
Mon 12 Oct— 00:18+5 min+6 min
Sun 11 OctWinterswijk West 00:21Partial coverage0 min—
Sat 10 Oct— 00:140 min+2 min
Fri 9 Oct— 00:110 min—
Thu 8 Oct— 00:120 min—
Wed 7 Oct— 00:120 min—
Sun 4 OctWinterswijk West 00:21No data—
Sat 3 OctWinterswijk West 00:18No data—
Sun 27 SeptWinterswijk West 00:21No data—