R23 1532 Ski stasjon – Oslo S

View line R23

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

It does not run today

Last recorded run: Saturday 14 November 0 min

Next service: tomorrow 13:08 from Ski stasjon · Sat 21 Nov

Next departure 13:08 tomorrow · Ski stasjon
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 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: +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

  • Wed 21 Oct Max en route +3 min · last fix heading to Oslo S +3 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 93% · 27
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=4
  • 75% W n=4
  • 100% T n=4
  • 100% F n=5
  • 100% S n=6
  • — S n=0

Stops and timetable

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

Last 90 days, 29 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
13:08on time on time
13:20on 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
Sat 14 NovOslo S 13:380 min—
Sat 7 NovOslo S 13:39−1 min—
Sat 31 OctOslo S 13:45+1 min+1 min
Fri 30 OctOslo S 13:450 min—
Thu 29 OctOslo S 13:450 min—
Wed 28 OctOslo S 13:41−1 min—
Tue 27 OctOslo S 13:450 min—
Mon 26 OctOslo S 13:44+2 min+2 min
Fri 23 OctOslo S 13:450 min—
Thu 22 OctOslo S 13:45+1 min—
Wed 21 OctOslo S 13:46+3 min+3 min
Tue 20 OctOslo S 13:44+1 min—
Mon 19 OctOslo S 13:450 min—
Sat 17 OctOslo S 13:440 min—
Fri 16 OctOslo S 13:410 min—
Thu 15 OctOslo S 13:450 min—
Tue 13 OctOslo S 13:450 min—
Mon 12 OctOslo S 13:45+1 min—
Fri 9 OctOslo S 13:42−1 min—
Thu 8 OctOslo S 13:45+2 min+2 min
Wed 7 OctOslo S 13:460 min—
Mon 5 Oct— 13:45+1 min+1 min
Sat 3 Oct— 13:40−1 min—
Mon 21 Sept— 13:450 min—
Tue 8 Sept— 13:280 min—
Sat 5 Sept— 13:45+1 min—
Fri 4 Sept— 13:400 min—
Wed 2 Sept— 13:450 min—
Mon 31 Aug— 13:44+1 min—