R23 1538 Ski stasjon → Oslo S

View line R23

Ski stasjon 14:38 → Oslo S 14:50 Mon, Tue, Wed, Thu, Fri 0 h 12 min · 2 stops Vy

It does not run today

Last recorded run: Thursday 19 November +1 min

Next service: Monday 14:38 from Ski stasjon · Mon 23 Nov

Next departure 14:38 Monday · Ski stasjon
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 16 full · 0 partial · 0 no data
On-time · 90 days
94%
30/32 runs under 3 min
RT coverage: 32 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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 6 Oct Max en route +8 min · last fix heading to Oslo S +8 min
  • Tue 27 Oct Max en route +3 min · last fix heading to Oslo S +3 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 91% · 29
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 78% T n=9
  • 100% W n=4
  • 100% T n=7
  • 100% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 32 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
14:38on time on time
14:50+1 min +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
Thu 19 NovOslo S 15:14+1 min+1 min
Wed 18 NovOslo S 15:14+2 min+2 min
Tue 17 NovOslo S 15:14+2 min+2 min
Mon 16 NovOslo S 15:14+1 min+1 min
Thu 12 NovOslo S 15:14+2 min+2 min
Tue 10 NovOslo S 15:14+1 min+1 min
Fri 6 NovOslo S 15:14+1 min+1 min
Thu 5 NovOslo S 15:14+1 min+1 min
Tue 3 NovOslo S 15:14+1 min+1 min
Mon 2 NovOslo S 15:140 min—
Fri 30 OctOslo S 15:150 min—
Thu 29 OctOslo S 15:150 min—
Wed 28 OctOslo S 15:15+1 min+1 min
Tue 27 OctOslo S 15:15+3 min+3 min
Mon 26 OctOslo S 15:14+1 min+1 min
Fri 23 OctOslo S 15:15+2 min+2 min
Thu 22 OctOslo S 15:15+1 min+1 min
Wed 21 OctOslo S 15:150 min—
Tue 20 OctOslo S 15:16+1 min+1 min
Mon 19 OctOslo S 15:150 min—
Fri 16 OctOslo S 15:15+1 min+1 min
Thu 15 OctOslo S 15:15+2 min+2 min
Wed 14 OctOslo S 15:140 min—
Tue 13 OctOslo S 15:15+1 min+1 min
Fri 9 OctOslo S 15:15+2 min+2 min
Thu 8 OctOslo S 15:14+1 min+1 min
Tue 6 OctOslo S 15:20+8 min+8 min
Mon 5 OctOslo S 15:15+2 min+2 min
Tue 22 Sept— 15:130 min—
Fri 18 Sept— 15:14+1 min+1 min