Train NS 3091 Heerhugowaard – Arnhem Centraal

Heerhugowaard 23:32 → Arnhem Centraal 01:30 Daily 1 h 58 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 23:32 from Heerhugowaard · Thu 19 Nov

Next departure 23:32 today · Heerhugowaard
On-time · 30 days
89%
24/27 runs under 3 min
RT coverage: 27 full · 0 partial · 1 no data
On-time · 90 days
93%
39/42 runs under 3 min
RT coverage: 42 full · 0 partial · 17 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Thu 29 Oct Max en route +7 min · last fix heading to — +7 min
  • Mon 2 Nov Max en route +5 min · last fix heading to — +5 min
  • Sat 14 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 39
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=7
  • 100% W n=7
  • 80% T n=5
  • 100% F n=6
  • 83% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 42 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:32on time on time
23:37≈ on time ≈ on time
23:40 / 23:43≈ on time ≈ on time
23:49≈ on time ≈ on time
23:55≈ on time ≈ on time
00:08≈ on time ≈ on time
00:15≈ on time ≈ on time
00:21 / 00:23≈ on time ≈ on time
00:31≈ on time ≈ on time
00:36≈ on time ≈ on time
00:52 / 00:53≈ on time ≈ on time
01:01≈ on time ≈ on time
01:14≈ on time ≈ on time
01:19≈ on time ≈ +1 min
01:30on time +1 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 18 Nov— 01:490 min—
Tue 17 Nov— 01:590 min—
Mon 16 Nov— 01:53+3 min+3 min
Sun 15 NovElst 02:080 min—
Sat 14 Nov— 01:54+4 min+4 min
Fri 13 Nov— 02:140 min—
Wed 11 Nov— 01:490 min—
Tue 10 Nov— 02:090 min—
Mon 9 Nov— 01:490 min—
Sun 8 NovElst 01:59+1 min—
Sat 7 NovSchagen 01:540 min—
Fri 6 Nov— 01:590 min—
Thu 5 Nov— 01:580 min—
Wed 4 Nov— 02:190 min—
Tue 3 Nov— 01:490 min—
Mon 2 Nov— 01:59+5 min+5 min
Sun 1 NovElst 02:020 min—
Sat 31 OctSchagen 23:360 min—
Fri 30 Oct— 01:560 min—
Thu 29 Oct— 01:14+7 min+7 min
Wed 28 Oct— 01:020 min—
Tue 27 Oct— 01:240 min—
Mon 26 OctAmsterdam Bijlmer ArenA 01:220 min—
Sun 25 OctUtrecht Centraal 01:16No data—
Sat 24 Oct— 01:220 min—
Fri 23 Oct— 00:530 min—
Thu 22 Oct— 01:450 min—
Wed 21 Oct— 01:050 min—
Tue 20 Oct— 01:020 min—
Sun 18 OctElst 02:090 min—