R23 1516 Ski stasjon → Oslo S

View line R23

Ski stasjon 09:08 → Oslo S 09:20 Mon, Tue, Wed, Thu, Fri 0 h 12 min · 2 stops Vy

It does not run today

Last recorded run: Friday 30 October −1 min

Next service: Monday 09:08 from Ski stasjon · Mon 23 Nov

Next departure 09:08 Monday · Ski stasjon
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 6 full · 0 partial · 0 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 27 full · 0 partial · 0 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: +1 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

  • Thu 8 Oct Max en route +19 min · last fix heading to Oslo S +17 min
  • Fri 16 Oct Max en route +3 min · last fix heading to Oslo S +3 min

Distribution · 90 days

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

  • Early 4% · 1
  • On time 89% · 24
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=4
  • 100% W n=4
  • 88% T n=8
  • 80% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 27 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
09:08on time on time
09:20on 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
Fri 30 OctOslo S 09:41−1 min—
Thu 29 OctOslo S 09:45−1 min—
Wed 28 OctOslo S 09:45+2 min+4 min
Tue 27 OctOslo S 09:440 min—
Mon 26 OctOslo S 09:450 min—
Fri 23 OctOslo S 09:41−1 min—
Thu 22 OctOslo S 09:45+1 min+1 min
Wed 21 OctOslo S 09:440 min—
Tue 20 OctOslo S 09:41−1 min—
Mon 19 OctOslo S 09:450 min—
Fri 16 OctOslo S 09:45+3 min+3 min
Thu 15 OctOslo S 09:400 min—
Tue 13 OctOslo S 09:45+1 min—
Mon 12 OctOslo S 09:44+1 min—
Fri 9 OctOslo S 09:400 min—
Thu 8 OctOslo S 10:00+17 min+19 min
Wed 7 OctOslo S 09:450 min—
Mon 5 Oct— 09:450 min—
Thu 24 Sept— 21:290 min—
Mon 21 Sept— 09:450 min—
Thu 17 Sept— 09:450 min—
Thu 10 Sept— 09:220 min—
Tue 8 Sept— 09:45+1 min+1 min
Fri 4 Sept— 09:450 min—
Wed 2 Sept— 09:41−1 min—
Mon 31 Aug— 09:450 min—
Thu 27 Aug— 09:46+1 min—