R23 1506 Ski stasjon – Oslo S

View line R23

Ski stasjon 06:38 → Oslo S 06:50 0 h 12 min · 2 stops Vy

Not running right now

Last recorded run: Friday 30 October 0 min

On-time · 30 days
75%
12/16 runs under 3 min
RT coverage: 16 full · 0 partial · 0 no data
On-time · 90 days
85%
35/41 runs under 3 min
RT coverage: 41 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +6 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 +9 min · last fix heading to Oslo S +9 min
  • Thu 15 Oct Max en route +8 min · last fix heading to Oslo S +8 min
  • Mon 26 Oct Max en route +5 min · last fix heading to Oslo S +5 min
  • Tue 6 Oct Max en route +7 min · last fix heading to Oslo S +5 min
  • Tue 27 Oct Max en route +7 min · last fix heading to Oslo S +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 35
  • 3–10 min 15% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 71% T n=7
  • 90% W n=10
  • 75% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 41 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
06:38on time on time
06:50on time +5 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 07:150 min+1 min
Thu 29 OctOslo S 07:15+2 min+3 min
Wed 28 OctOslo S 07:14+2 min+3 min
Tue 27 OctOslo S 07:19+5 min+7 min
Mon 26 OctOslo S 07:15+5 min+5 min
Fri 23 OctOslo S 07:150 min—
Wed 21 OctOslo S 07:15+1 min+1 min
Tue 20 OctOslo S 07:150 min—
Mon 19 OctOslo S 07:150 min—
Fri 16 OctOslo S 07:15−1 min—
Thu 15 OctOslo S 07:20+8 min+8 min
Wed 14 OctOslo S 07:150 min—
Tue 13 OctOslo S 07:15+1 min+1 min
Mon 12 OctOslo S 07:14+2 min+3 min
Fri 9 OctOslo S 07:14+1 min+2 min
Thu 8 OctOslo S 07:20+9 min+9 min
Wed 7 OctOslo S 07:150 min—
Tue 6 OctOslo S 07:20+5 min+7 min
Mon 5 Oct— 07:16+1 min+2 min
Thu 1 Oct— 07:15+1 min+1 min
Wed 30 Sept— 06:330 min—
Mon 28 Sept— 05:460 min—
Thu 24 Sept— 07:120 min—
Wed 23 Sept— 06:150 min—
Tue 22 Sept— 07:14−1 min—
Mon 21 Sept— 06:160 min—
Fri 18 Sept— 07:150 min—
Mon 14 Sept— 07:15+1 min+3 min
Wed 9 Sept— 07:15+4 min+4 min
Fri 4 Sept— 06:160 min—