Line F5: Oslo SStavanger
Checking traffic notices…
Departure board
From Oslo S
Stavanger
Finding your next train
Checking departure times and platforms…
| Time | Destination | Platform | Train details |
|---|
Norwegian local time · Entur · updated every 30 seconds. A dash means no platform is reported.
Along the line
Where is the train?
Map coverage & sources
SJ NORD does not publish vehicle positions through Entur. Where a position is missing, hollow markers show an estimate along the route between station times. Updated stop times are used where available. An estimate does not confirm the train is running; check departures for travel information.
Filled markers use reported positions from Vy, Flytoget and Go-Ahead. Coverage varies and this map does not include every freight or passenger train.
Select a train for its stops. Select a station for departures.
Know your route
Stops & connections
F5 connects Oslo S and Stavanger. Select a station for its departure board and connecting lines. Individual trains may serve fewer stops.
Journeys on F5
- Lysaker → Oslo S13 min
- Oslo S → Asker23 min
- Oslo S → Sandvika17 min
- Oslo S → Drammen35 min
- Stavanger → Sandnes sentrum16 min
- Bryne → Stavanger32 min
- Stavanger → Egersund1 h 11 min
- Oslo S → Kongsberg1 h 17 min
- Drammen → Bø1 h 26 min
- Drammen → Drangedal1 h 57 min
- Drammen → Neslandsvatn2 h 9 min
- Oslo S → Bø2 h 2 min
2026-11-04 – 2026-11-10.
- Measured stop departures
- 2,235
- 4+ minutes late
- 1,112
- Cancelled departures
- 1195.1 % of planned
- On time, all planned
- 47.7 %cancelled counts as not on time
- No reason given105 · 88.2 %
- No traffic notice linked14 · 11.8 %
- «Toget er innstilt mellom Oslo S og Stavanger på grunn av problemer med toget.» (GOA, 57 departures)
- «Toget er innstilt mellom Stavanger og Oslo S på grunn av problemer med toget.» (GOA, 25 departures)
- «Toget er innstilt mellom Kristiansand og Stavanger på grunn av problemer med toget.» (GOA, 13 departures)
Counted for 119 of 119 cancelled departures. The cause is read only from the operator's own traffic notice; when the notice names no cause we say so.
Delays and data coverage
Measured delays: 485 at 4–9 min · 437 at 10–29 min · 190 at 30+ min.
19 planned stop departures were neither measured nor reported cancelled. A missing measurement is not evidence of a cancellation.
Cancelled departures are station departures Entur reported cancelled and that we did not see run. A reported cancellation counts as accounted for in the data coverage: we know what happened to that departure. A train whose whole journey was cancelled before we could see its stops is reported separately. Whole trains reported cancelled: 0.