Flight data

You can use some of the content on Avinor's website in your own services without having to pay for it.

Spacious modern control room with multiple large display screens and staff members standing, showcasing operational monitoring and management.

Flight Data in XML Format

Changes in URL and Parameters for XML Feeds:

URLs and parameters for the new XML feed are now case-sensitive. If the URL is incorrect regarding uppercase and lowercase letters, the request will fail.
- If the parameters are incorrect regarding uppercase and lowercase letters, the parameter will not be evaluated, and the default value will be used.
Estimated times will be updated earlier and more frequently

Technical Description:

The data foundation in the services is the same as that used in our own internet solutions, on information screens at airports, and with partners such as Flytoget and NRK. The services do not include data from private airports like Sandefjord Airport, Torp.

The points below provide technical descriptions of the data services we offer.

Note that the descriptions are intended for individuals familiar with the XML format.

xmlfeed	Description
asrv.avinor.no/XmlFeed/v1.0	Flights to and from Norwegian airports
asrv.avinor.no/flightStatuses/v1.0	Status of flights
asrv.avinor.no/airportNames/v1.0	Names and IATA codes for airports
asrv.avinor.no/airlineNames/v1.0	Names and IATA codes for airlines

Note: Please be aware of the correct use of uppercase and lowercase letters in the links and parameters. Incorrect use will cause the link to not work and the parameters to be disregarded.

Flight information (incl. updated traffic status) - asrv.avinor.no/XmlFeed/v1.0

The service provides access to the timetable for Avinor's 43 airports, as well as continuously updated traffic status.

To ensure you offer your end-users correct/updated flight data, you should retrieve flight times every 3 minutes. More frequent queries than this are not necessary.We urge everyone using data from Avinor to cache the data in their own service, and not allow the client (end user) to go directly to our service.

Parameters

Parameter

Description

Example

airport

Mandatory. IATA code that determines which airport the XML extraction applies to.

airport=OSL

TimeFrom

Optional, default value is one hour. Determines how far back in time flights are retrieved for, rounded down to whole hours.

TimeFrom=2

TimeTo

Optional, default value is seven hours. Determines how far forward in time flights are retrieved for, rounded down to whole hours.

TimeTo=5

Direction

Optional, specifies the "direction" of a flight: A = "Arrivals", D = "Departures".If no value is selected, both A and D will be displayed.

direction=D

lastUpdate

Optional, retrieves only flight data that has been updated after a given time.

lastUpdate=2024-08-08T09:30:00Z

codeshare

Optional, when this parameter is included, any codeshare info will be added to the flight. Codeshare info consists of codeshareAirlineDesignators, codeshareAirlineNames, codeshareFlightNumbers, and codeshareOperationalSuffixs.

codeshare=Y

servicetype

Optional, Allows including helicopter flights by adding the parameter serviceType «E». Helicopter flights will be included in the result, in addition to regular scheduled flights with service type ‘J’ (Schedule passenger) and ‘C’ (Charter passenger).

serviceType=E

direction

Example request: asrv.avinor.no/XmlFeed/v1.0?

TimeFrom=1&TimeTo=7&airport=OSL&direction=D&lastUpdate=2024-08-08T09:30:00Z

The query retrieves changes in departures at Oslo Airport, one hour back and seven hours forward, and only for flights updated after the specified date/time in lastUpdate. Description of attributes: The top element (parent element) in the XML document is named airport.This element has a sub-element (child element) named flights and it contains elements of the type flight.

Attribute	Description	Example
lastUpdate	Always included. Attribute for the flights element that indicates the last modification time for flight data for the respective airport.	"2024-08-09T07:05:00Z"
uniqueId	Always included. Attribute for the flight element that indicates a unique ID for the flight, max 12 digits	"1617049968"
flightId	Always included. Sub-element of "flight" that indicates the ID for the flight.	"SK4167"
dom_int	Always included. Indicates whether it is a domestic (D), international (I), or Schengen (S) flight.	"D"
schedule_time	Always included. arrival/departure time.	"2024-08-09T07:05:00Z"
arr_dep	Always included. Indicates arrival or departure. A = "Arrival", D = "Departure".	"D"
airport	Always included.Displays the IATA code for the arrival or departure airport depending on arr_dep. See the separate service for the airport name below.	"BGO"
airline	Always included.Displays the IATA code for the airline. Refer to the separate service for airline names below.	VF
via_airport	Displays any layovers, max. 10 IATA codes separated by commas «,».	SVG, BOO
check_in	Displays check-in area if provided.	1 2 3
gate	Displays gate number. Can contain both numbers and letters.	B32
status code	The attribute «code» on the status element indicates the status text for a flight. Note that status texts can change without notice. Refer also to the separate service for status texts described below.	A = Arrived C = Cancelled D = Departed E = New time N = New info
status time	The attribute “time” on the status element indicates the status time for a flight.	2024-08-09T07:05:00Z
belt_number	Indicates which baggage belt is used for a flight.	9

Time Indications

All times are given in UTC (Wikipedia:UTC, CET) and are in ISO 8601 (Wikipedia: ISO 8601 format) [YYYY]-[MM]-[DD]T[hh]:[mm]:[ss]Z.Remember to adjust for our time zone, as well as any daylight saving time.

Example: 2009-12-31T16:00:00 corresponds to December 31, 2009, at 17:00 local time in Norway (CET), while 2009-06-23T16:00:00 corresponds to June 23, 2009, at 18:00 local time in Norway (Daylight Saving Time).

Flight Statuses - asrv.avinor.no/flightStatuses/v1.0

The service provides you with status text for the status codes associated with a flight.

Queries to the service more frequently than every 24.time should not be necessary to ensure updated data.

Parameters

Parameter	Description	Example
code	Display only one of the status codes	code=N

Example request:

asrv.avinor.no/flightStatuses/v1.0?code=D

Airport Names - asrv.avinor.no/airportNames/v1.0

The service gives you access to the names and IATA code of Norwegian and international airports.

Queries against the service more frequently than every 24.time should not be necessary to ensure updated data.

Parameters

Parameter	Description	Example
airport	Optional - Display only one of the airports	airport=OSL
shortname	Optional - Include a short name for the airport in the result	shortname=Y

Example of request:

asrv.avinor.no/airportNames/v1.0?airport=BGO&shortname=Y

Airline - asrv.avinor.no/airlineNames/v1.0

The service gives you access to the names and IATA code of Norwegian and international airlines.

Queries against the service more frequently than every 24.

Terms of Use

We do not impose any limitations on how data is used, as long as the content is not used in contexts that violate Norwegian law. We reserve the right to terminate access for users who utilize the services in contexts deemed harmful to Avinor's reputation. Information, but not justification, about such decisions will be provided if contact information is available.

All content from our services must be labeled "Flight data from Avinor." The text must be a link to www.avinor.no, placed in close proximity to the data, and be clearly visible to the end user.

If you plan to use the data services in contexts that involve a heavy load on our servers, we ask you to contact us in advance. Unfortunately, Avinor is not able to provide technical support.

Avinor cannot guarantee that the content is complete, up to date, or available at any given time and place. (However, we promise to do our best with the available resources and conditions.)

If you have questions or wish to contact us, send an email to