R23x 1510 Moss stasjon – Oslo S

View line R23x

Moss stasjon 07:13 → Oslo S 07:50 Mon, Tue, Wed, Thu, Fri 0 h 37 min · 5 stops Vy

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: tomorrow 07:13 from Moss stasjon · Mon 9 Nov

Next departure 07:13 tomorrow · Moss stasjon
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
100%
36/36 runs under 3 min
RT coverage: 36 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

Distribution · 90 days

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

  • Early 11% · 4
  • On time 89% · 32
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=8
  • 100% T n=6
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 36 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
07:13on time on time
07:25 / 07:26≈ on time ≈ on time
07:30 / 07:31≈ on time ≈ on time
07:36 / 07:38≈ on time ≈ +1 min
07:50on 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
Fri 6 NovOslo S 08:190 min+1 min
Thu 5 NovOslo S 08:340 min+1 min
Wed 4 NovOslo S 08:240 min+1 min
Tue 3 NovOslo S 08:24−1 min—
Mon 2 NovOslo S 08:19+1 min—
Fri 30 OctOslo S 08:12+1 min+2 min
Thu 29 OctOslo S 08:400 min—
Wed 28 OctOslo S 08:35+1 min—
Tue 27 OctOslo S 08:29+1 min+3 min
Mon 26 OctOslo S 08:250 min—
Fri 23 OctOslo S 08:300 min—
Thu 22 OctOslo S 08:13−1 min+1 min
Wed 21 OctOslo S 08:340 min—
Tue 20 OctOslo S 08:31+1 min+2 min
Mon 19 OctOslo S 08:16+3 min+3 min
Fri 16 OctOslo S 08:34−1 min—
Thu 15 OctOslo S 08:30−1 min—
Wed 14 OctOslo S 08:150 min—
Tue 13 OctOslo S 08:20−2 min—
Mon 12 OctOslo S 08:400 min+1 min
Fri 9 OctOslo S 08:26−1 min—
Wed 7 OctOslo S 08:250 min+5 min
Tue 6 OctOslo S 08:11+2 min+3 min
Mon 5 Oct— 08:30+2 min+2 min
Mon 28 Sept— 08:31−1 min—
Wed 23 Sept— 07:31+1 min+2 min
Tue 15 Sept— 08:25−1 min+2 min
Fri 11 Sept— 08:240 min+2 min
Fri 4 Sept— 06:230 min—
Thu 3 Sept— 07:420 min—