R31 290 Hakadal stasjon – Oslo S

View line R31

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

It does not run today

Last recorded run: Thursday 5 November +2 min

Next service: Monday 17:09 from Hakadal stasjon · Mon 9 Nov

Next departure 17:09 Monday · Hakadal stasjon
On-time · 30 days
53%
10/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
45%
14/31 runs under 3 min
RT coverage: 31 full · 0 partial · 0 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +3 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +8 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 27 Oct Max en route +11 min · last fix heading to Oslo S +10 min
  • Fri 9 Oct Max en route +10 min · last fix heading to Oslo S +8 min
  • Tue 3 Nov Max en route +8 min · last fix heading to Oslo S +8 min
  • Tue 25 Aug Max en route +9 min · last fix heading to — +8 min
  • Wed 4 Nov Max en route +7 min · last fix heading to Oslo S +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 45% · 14
  • 3–10 min 52% · 16
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 14% T n=7
  • 33% W n=6
  • 40% T n=5
  • 57% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

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