R22 1928 Rakkestad stasjon – Oslo S

View line R22

Rakkestad stasjon 16:47 → Oslo S 17:59 Mon, Tue, Wed, Thu, Fri 1 h 12 min · 13 stops Vy

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 16:47 from Rakkestad stasjon · Wed 11 Nov

Next departure 16:47 today · Rakkestad stasjon
On-time · 30 days
83%
24/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
85%
45/53 runs under 3 min
RT coverage: 53 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Fri 6 Nov Max en route +20 min · last fix heading to Oslo S +20 min
  • Sat 29 Aug Max en route +17 min · last fix heading to — +17 min
  • Mon 9 Nov Max en route +9 min · last fix heading to Oslo S +9 min
  • Mon 17 Aug Max en route +9 min · last fix heading to — +7 min
  • Tue 13 Oct Max en route +5 min · last fix heading to Oslo S +5 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 81% · 43
  • 3–10 min 11% · 6
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 71% M n=7
  • 75% T n=8
  • 100% W n=7
  • 83% T n=6
  • 67% F n=6
  • 89% S n=9
  • 100% S n=10

Stops and timetable

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

Last 90 days, 53 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
16:47on time on time
16:50≈ on time ≈ on time
16:54≈ on time ≈ on time
17:01 / 17:02≈ on time ≈ +1 min
17:05 / 17:06≈ on time ≈ +1 min
17:12 / 17:14≈ on time ≈ +1 min
17:23 / 17:24≈ +1 min ≈ +2 min
17:26 / 17:27≈ +1 min ≈ +2 min
17:31 / 17:32≈ +1 min ≈ +2 min
17:35 / 17:36≈ +1 min ≈ +3 min
17:39 / 17:40≈ +1 min ≈ +3 min
17:46 / 17:47≈ +1 min ≈ +3 min
17:59+1 min +4 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
Tue 10 NovOslo S 18:190 min—
Mon 9 NovOslo S 18:29+9 min+9 min
Sun 8 NovOslo S 18:190 min+1 min
Sat 7 NovOslo S 18:24+2 min+4 min
Fri 6 NovOslo S 18:39+20 min+20 min
Thu 5 NovOslo S 18:24+4 min+4 min
Wed 4 NovOslo S 18:190 min+4 min
Tue 3 NovOslo S 18:24+3 min+5 min
Mon 2 NovOslo S 18:190 min—
Sun 1 NovOslo S 18:19+1 min+1 min
Sat 31 OctOslo S 18:19+1 min+2 min
Fri 30 OctOslo S 18:25+2 min+2 min
Thu 29 OctOslo S 18:25+2 min+5 min
Wed 28 OctOslo S 18:20+1 min+1 min
Tue 27 OctOslo S 18:24+2 min+2 min
Mon 26 OctOslo S 18:20+1 min+1 min
Sun 25 OctOslo S 18:250 min+1 min
Sat 24 OctOslo S 18:25+1 min+2 min
Fri 23 OctOslo S 18:20+1 min+2 min
Thu 22 OctOslo S 18:20−1 min+2 min
Wed 21 OctOslo S 18:25+1 min+3 min
Tue 20 OctOslo S 18:25+2 min+3 min
Mon 19 OctOslo S 18:200 min+1 min
Sun 18 OctOslo S 18:19+1 min+2 min
Sat 17 OctOslo S 18:24+1 min+2 min
Fri 16 OctOslo S 18:200 min+3 min
Thu 15 OctOslo S 18:26+1 min+4 min
Wed 14 OctOslo S 18:190 min+1 min
Tue 13 OctOslo S 18:25+5 min+5 min
Sun 11 OctOslo S 18:20+1 min—