R23 1540 Ski stasjon – Oslo S

View line R23

Ski stasjon 15:08 → Oslo S 15: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 15:08 from Ski stasjon · Sat 21 Nov

Next departure 15:08 tomorrow · Ski stasjon
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 11 full · 0 partial · 0 no data
On-time · 90 days
93%
27/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

  • Sat 24 Oct Max en route +4 min · last fix heading to Oslo S +3 min
  • Wed 7 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 90% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 75% W n=4
  • 100% T n=4
  • 100% F n=6
  • 83% 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
15:08on time on time
15: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 15:440 min—
Sat 7 NovOslo S 15:440 min—
Sat 31 OctOslo S 15:440 min—
Fri 30 OctOslo S 15:410 min—
Thu 29 OctOslo S 15:41−1 min—
Wed 28 OctOslo S 15:450 min—
Tue 27 OctOslo S 15:450 min—
Mon 26 OctOslo S 15:440 min—
Sat 24 OctOslo S 15:45+3 min+4 min
Fri 23 OctOslo S 15:450 min—
Thu 22 OctOslo S 15:45+1 min+2 min
Wed 21 OctOslo S 15:45−1 min—
Tue 20 OctOslo S 15:45+1 min—
Mon 19 OctOslo S 15:450 min—
Sat 17 OctOslo S 15:450 min—
Fri 16 OctOslo S 15:440 min—
Thu 15 OctOslo S 15:440 min—
Tue 13 OctOslo S 15:440 min—
Mon 12 OctOslo S 15:450 min—
Fri 9 OctOslo S 15:44+1 min—
Thu 8 OctOslo S 15:450 min—
Wed 7 OctOslo S 15:45+3 min+3 min
Mon 5 OctOslo S 15:450 min—
Fri 2 Oct— 15:41−1 min—
Sat 19 Sept— 15:450 min+1 min
Tue 15 Sept— 15:45+1 min—
Fri 11 Sept— 15:450 min—
Wed 2 Sept— 15:45+2 min+2 min
Tue 25 Aug— 15:44+1 min+2 min