FLY2 3940 Oslo lufthavn stasjon – Oslo S

View line FLY2

Oslo lufthavn stasjon 15:40 → Oslo S 15:59 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
88%
21/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 no data
On-time · 90 days
86%
24/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
+4min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Wed 21 Oct Max en route +6 min · last fix heading to Oslo S +6 min
  • Fri 30 Oct Max en route +4 min · last fix heading to Oslo S +4 min
  • Thu 29 Oct Max en route +4 min · last fix heading to Oslo S +4 min
  • Mon 5 Oct Max en route +4 min · last fix heading to Oslo S +4 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 86% · 24
  • 3–10 min 14% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 80% W n=5
  • 80% T n=5
  • 75% F n=4
  • — S n=0
  • 100% 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
15:40on time on time
15:59on time +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
Fri 6 NovOslo S 16:040 min—
Thu 5 NovOslo S 16:040 min—
Wed 4 NovOslo S 16:040 min—
Tue 3 NovOslo S 16:08+1 min+1 min
Mon 2 NovOslo S 16:030 min—
Sun 1 NovOslo S 16:050 min—
Fri 30 OctOslo S 16:55+4 min+4 min
Thu 29 OctOslo S 16:12+4 min+4 min
Wed 28 OctOslo S 16:060 min—
Tue 27 OctOslo S 16:070 min—
Mon 26 OctOslo S 16:120 min—
Sun 25 OctOslo S 16:020 min—
Thu 22 OctOslo S 16:08+1 min+1 min
Wed 21 OctOslo S 16:10+6 min+6 min
Tue 20 OctOslo S 16:050 min—
Mon 19 OctOslo S 16:05+1 min+1 min
Sun 18 OctOslo S 16:040 min—
Fri 16 OctOslo S 16:090 min—
Thu 15 OctOslo S 16:050 min—
Wed 14 OctOslo S 16:070 min—
Tue 13 OctOslo S 16:040 min—
Mon 12 OctOslo S 16:060 min—
Sun 11 OctOslo S 16:07+2 min+2 min
Fri 9 OctOslo S 16:050 min—
Thu 8 OctOslo S 16:08+1 min+2 min
Wed 7 OctOslo S 16:14+1 min+1 min
Tue 6 OctOslo S 16:07+2 min+2 min
Mon 5 OctOslo S 16:14+4 min+4 min