Oslo Airport Gardermoen (OSL) flight compensation: delays and cancellations
Short answer: A commercial flight that begins at Oslo Airport Gardermoen (OSL) normally falls within European passenger-rights territory, including when a non-EU airline operates it. A third-country departure ending at OSL has a narrower rule, because the aircraft generally must be operated by an eligible European carrier. For travel through OSL, the monetary result still turns on what happened, when the traveller reached the contractual destination and whether the airline proves an extraordinary cause plus reasonable measures.
Free eligibility check
Check your case in the form
Enter your route, date and type of disruption. We will check whether your case qualifies for a claim under EU 261/2004 or UK261.
What happened to your flight?
Claim up to €600 for a delayed or cancelled flight.
Choose the situation that applies to your flight:
This OSL assessment uses sources checked on 12 September 2026 and intentionally leaves unstable flight numbers out of the analysis.
The local screening line should contain OSL, the aircraft operator and every ticketed endpoint. In the OSL record, names such as Norwegian, European network carriers, Norwegian regions and selected long-haul destinations illustrate the range of possible records at this airport, but only the passenger's own documents establish the relevant combination.
Airport-specific facts at Oslo Airport Gardermoen
Passenger-rights evidence at Oslo Airport Gardermoen reflects a network built around Norway's principal EEA hub with domestic feeders and broad international service. On the documented OSL facts, flights can be performed by Norwegian, SAS, Widerøe and European network carriers, connecting Oslo with Norwegian regions, Europe, the UK and selected long-haul destinations.
Norway participates through the EEA, so an OSL departure receives the same territorial starting protection as an EU departure.
These examples describe the OSL market reviewed on the date above; they are not a guarantee that any airline operates every season. The e-ticket and day-of-travel record control the individual case.
The local coordinates of a OSL claim
The presence of Norwegian or European network carriers on a OSL confirmation does not settle operational control. When recording the OSL event, preserve the line beneath the flight number, because codeshare, wet lease and a same-day substitution can place another airline on the aircraft.
Routes associated with Norwegian regions and selected long-haul destinations show why distance alone is an incomplete OSL test. For OSL, the departure side, aircraft operator and final destination on one protected booking must be established before money is calculated.
When writing about the disruption, distinguish the airport from its city: Oslo Airport Gardermoen is OSL. For the journey involving OSL, retain that identifier through every rerouting and expense entry, even if the airline moved the passenger elsewhere.
For OSL, those three coordinates -- operator, complete route and precise airport -- should agree across the ticket, boarding documents and claim form. At OSL, if one changes after rebooking, show both the original and replacement value rather than overwriting the first.
For this airport, the working record links OSL, Norwegian, European network carriers, Norwegian regions and selected long-haul destinations only where the passenger's own ticket and day-of-travel documents support that connection.
Place the OSL flight on the right legal side
| OSL itinerary fact | Carrier in operational control | Coverage consequence |
|---|---|---|
| Passenger starts at OSL | EU or non-Carrier within EU261 inbound scope | Start with European passenger rights |
| Non-European departure ending at OSL | Eligible European performing airline | The non-European origin can still qualify |
| Inbound journey from abroad to OSL | Third-country performing airline | Operator status generally leaves this outside EU261 |
| Through journey on a single OSL reservation | Check who performed the disrupted flight | The ticketed endpoint may control time but not erase the carrier test |
The coverage screen for Oslo Airport Gardermoen begins with two facts: where the disrupted aircraft was due to depart and which carrier was responsible for flying it. Residence and payment currency do not replace either fact.
The OSL table is a screening tool, not a promise of payment. On the documented OSL facts, the traveller must still show a qualifying disruption and the airline may defeat fixed compensation only by proving an extraordinary cause plus reasonable measures.
Final destination versus separate tickets at OSL
For travel through OSL, a domestic Widerøe or SAS feeder on one ticket can make final arrival abroad decisive; an independently bought feeder is usually separate. Before combining delays across OSL, verify who sold through transport and whether the carrier rebooked the onward sector as part of the same journey.
The final-arrival clock for an OSL through journey stops when passengers can leave the aircraft at their destination, not when wheels touch the runway. Keep a timestamped note if airline records later differ.
Turn the OSL event into evidence
The strongest Oslo Airport Gardermoen file connects documents to decisions. For the journey involving OSL, record what the carrier communicated, what choice the passenger made and which expense followed from the disruption.
- the original reservation for Oslo Airport Gardermoen, with the PNR and 'operated by' wording visible before any rebooking overwrites it;
- the first boarding pass plus replacement coupons that show how the airline changed the route after OSL;
- the time promised on the ticket and the moment the completed reroute actually delivered the traveller beyond Oslo Airport Gardermoen;
- the first operational explanation, later updates and visible OSL status board before those records disappear;
- dated invoices that identify each meal, hotel night or ground transfer purchased because of the OSL wait;
- Applied to OSL, the carrier's refused or unanswered assistance request and the decision that led to reasonable self-help.
For OSL, keep care receipts separate from consequential losses such as prepaid hotels at the destination. The legal basis and evidence burden are not the same.
Four different remedies can follow at OSL
A qualifying OSL disruption is priced by distance rather than fare: EUR 250 up to 1,500 km, EUR 400 for the applicable middle category and EUR 600 for other journeys above 3,500 km. For OSL, defined rerouting outcomes can halve the sum, and extraordinary circumstances can defeat it.
At Oslo Airport Gardermoen, fixed compensation is only one column. For the journey involving OSL, cancellation also gives a choice between reimbursement and rerouting, while a qualifying wait can require meals, hotel accommodation and transport even when fixed compensation fails.
For overnight disruption at Oslo Airport Gardermoen, request hotel and transport first. At OSL, if no assistance appears, document the unavailable desk or unanswered channel before arranging a reasonable alternative.
A two-flight OSL thought experiment
Overbooking at OSL leaves one passenger behind involuntarily while another accepts travel credit and volunteers. When recording the OSL event, their outcomes differ because consent to surrender the seat changes the denied-boarding analysis.
A family using Oslo Airport Gardermoen should run this analysis per passenger. In this OSL claim, infants without a separate fare, reward tickets and voluntary seat surrender may require additional examination.
The operating airline comes first at OSL
Send the first OSL demand to the operating airline, not automatically to the airport, booking platform or marketing carrier. In the OSL record, identify the flight, booking, passengers, final delay, remedy and evidence in separate paragraphs.
After allowing the airline to answer the documented OSL demand, match the escalation to the governing regime. When recording the OSL event, civil Aviation Authority of Norway can identify the national framework, while prescription and court competence remain separate.
If another airport replaced OSL, start with the airport comparison page. For the journey involving OSL, the guides to delay and cancellation own those legal tests, while the calculator supplies a figure only for covered travel.
Status of the rules on 12 September 2026
The applicable-law section is deliberately dated 12 September 2026. In this OSL claim, it keeps the EU rules then in use separate from the July 2026 reform, whose new procedures apply only after publication and the stated 12 months and 20 days.
Treat the OSL file as live: archive evidence, complain through a traceable channel and calculate deadlines under the jurisdiction that can hear the present dispute.
FAQ
Does EU261 cover every flight departing from OSL?
Regulation 261 generally covers the departure. For the journey involving OSL, the remaining questions concern the passenger's reservation, timing, cause and whether the claim is for compensation, refund, rerouting or care.
Who is responsible for a codeshare disruption at OSL?
Address the statutory claim to the performing carrier shown for the disrupted OSL flight. Use the seller only for ticket servicing that genuinely belongs to it.
Does a missed connection change the OSL delay calculation?
The final ticketed airport may supply the relevant delay on one reservation. Do not assume that flights displayed together by a search engine are contractually linked.
What remains due when weather affected Oslo Airport Gardermoen?
Extraordinary conditions may remove the distance-based payment without erasing every duty. The airline should still explain the causal chain and its response.
What should I collect before leaving Oslo Airport Gardermoen?
For the journey involving OSL, create a dated bundle containing the PNR, ticket numbers, both routings, messages, airport-board images and proof of every reasonable purchase caused by the event.