FLY2 3980 Oslo lufthavn stasjon – Oslo S

View line FLY2

Oslo lufthavn stasjon 22:20 → Oslo S 22:39 Fri 0 h 19 min · 2 stops Flytoget

It does not run today

Last recorded run: Friday 6 November 0 min

On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

  • Sun 18 Oct Max en route +15 min · last fix heading to Oslo S +15 min
  • Sun 25 Oct Max en route +11 min · last fix heading to Oslo S +11 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 0% · 0
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • — S n=0
  • 50% S n=4

Stops and timetable

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

Last 90 days, 28 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
22:20on time on time
22:39on time on time

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 23:280 min+6 min
Thu 5 NovOslo S 23:030 min—
Wed 4 NovOslo S 23:240 min+2 min
Tue 3 NovOslo S 23:040 min—
Mon 2 NovOslo S 23:090 min—
Sun 1 NovOslo S 22:44+1 min+1 min
Fri 30 OctOslo S 23:040 min—
Thu 29 OctOslo S 23:120 min+2 min
Wed 28 OctOslo S 23:010 min—
Tue 27 OctOslo S 23:030 min—
Mon 26 OctOslo S 23:120 min+9 min
Sun 25 OctOslo S 22:55+11 min+11 min
Thu 22 OctOslo S 23:080 min—
Wed 21 OctOslo S 23:030 min—
Tue 20 OctOslo S 23:100 min—
Mon 19 OctOslo S 23:260 min—
Sun 18 OctOslo S 22:56+15 min+15 min
Fri 16 OctOslo S 23:040 min—
Thu 15 OctOslo S 23:050 min—
Wed 14 OctOslo S 23:140 min—
Tue 13 OctOslo S 23:080 min—
Mon 12 OctOslo S 23:040 min—
Sun 11 OctOslo S 22:450 min—
Fri 9 OctOslo S 23:050 min—
Thu 8 OctOslo S 23:130 min—
Wed 7 OctOslo S 23:120 min+5 min
Tue 6 OctOslo S 23:200 min—
Mon 5 OctOslo S 23:130 min—