R31 286 Hakadal stasjon – Oslo S

View line R31

Hakadal stasjon 15:09 → Oslo S 15:52 Mon, Tue, Wed, Thu, Fri 0 h 43 min · 11 stops Vy

It has not run yet today

Last recorded run: Friday 13 November +4 min

Next service: today 15:09 from Hakadal stasjon · Mon 16 Nov

Next departure 15:09 today · Hakadal stasjon
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
79%
26/33 runs under 3 min
RT coverage: 33 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Oslo S, in minutes. One bar per run.

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

Worst days

  • Tue 22 Sept Max en route +14 min · last fix heading to — +11 min
  • Wed 26 Aug Max en route +11 min · last fix heading to — +9 min
  • Fri 13 Nov Max en route +8 min · last fix heading to Oslo S +4 min
  • Fri 2 Oct Max en route +5 min · last fix heading to — +4 min
  • Mon 28 Sept Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 9% · 3
  • On time 70% · 23
  • 3–10 min 18% · 6
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 83% T n=6
  • 75% W n=8
  • 83% T n=6
  • 67% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 33 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
15:09on time on time
15:10 / 15:11≈ on time ≈ on time
15:14 / 15:15≈ on time ≈ +1 min
15:18 / 15:19≈ on time ≈ +2 min
15:24 / 15:27≈ on time ≈ +3 min
15:28 / 15:29≈ on time ≈ +4 min
15:36 / 15:37≈ on time ≈ +4 min
15:38 / 15:39≈ on time ≈ +4 min
15:42 / 15:43≈ on time ≈ +4 min
15:46 / 15:47≈ on time ≈ +4 min
15:52on time +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
Fri 13 NovOslo S 16:19+4 min+8 min
Wed 11 NovOslo S 16:140 min+1 min
Tue 10 NovOslo S 16:14−1 min+2 min
Mon 9 NovOslo S 16:19+1 min+2 min
Fri 6 NovOslo S 16:15−1 min—
Thu 5 NovOslo S 16:14−1 min+3 min
Wed 4 NovOslo S 16:19+2 min+5 min
Tue 3 NovOslo S 16:140 min+2 min
Mon 2 NovOslo S 16:14−1 min+2 min
Fri 30 OctOslo S 16:17+1 min+5 min
Thu 29 OctOslo S 16:20+3 min+10 min
Wed 28 OctOslo S 16:20+3 min+5 min
Tue 27 OctOslo S 16:140 min+2 min
Mon 26 OctOslo S 16:14−1 min+2 min
Fri 23 OctOslo S 16:15−2 min—
Thu 22 OctOslo S 16:16−1 min+3 min
Wed 21 OctOslo S 16:15−1 min+3 min
Tue 20 OctOslo S 16:160 min+2 min
Mon 19 OctOslo S 16:15+1 min+4 min
Thu 15 OctOslo S 16:150 min+4 min
Wed 14 OctOslo S 16:15−1 min+2 min
Tue 13 OctOslo S 16:160 min+4 min
Mon 12 OctOslo S 15:480 min—
Fri 9 OctOslo S 16:16+1 min+4 min
Thu 8 OctOslo S 16:19+3 min+5 min
Wed 7 OctOslo S 16:20+3 min+4 min
Mon 5 OctOslo S 16:150 min+3 min
Fri 2 Oct— 16:20+4 min+5 min
Wed 30 Sept— 16:07+1 min+5 min
Mon 28 Sept— 16:08+3 min+5 min