biztrac. BETA
COMPANY REGISTER PROFILE
928966615 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

OSLO AIRPORT PROPERTY AS

Org. no. 928966615 Limited company (AS) Ullensaker Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 11.3m
Operating profit NOK 5.9m
Equity NOK 6.2m
Incorporated 2022
Share capital NOK 1.0m

OSLO AIRPORT PROPERTY AS is registered as a limited company in Ullensaker, Akershus with organisation number 928966615. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2022. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg, utvikling, drift og utleie av fast eiendom, og alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.3m in revenue and NOK 5.9m in operating profit.

Key figures · 2025

Revenue
NOK 11.3m
▲ +9 %
Operating profit
NOK 5.9m
▼ −12 %
Equity
NOK 6.2m
▲ +49 %
Est. value
NOK 13.5m

Financial health · 2025

Liquidity
3.46
Very good
Current assets ÷ current liabilities
Profitability
10.6%
Good
Return on total assets
Solidity
11.2%
Satisfactory
Equity as a share of total capital

Who owns OSLO AIRPORT PROPERTY AS?

OSLO AIRPORT PROPERTY AS
NOK 11.3m rev. · NOK 5.9m profit

OSLO AIRPORT PROPERTY AS has 1 registered shareholder:

All shareholders and roles →

Group structure

OSLO AIRPORT PROPERTY AS er morselskap for 9 datterselskaper:

Frequently asked questions about OSLO AIRPORT PROPERTY AS

Who owns OSLO AIRPORT PROPERTY AS?

COAST INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of OSLO AIRPORT PROPERTY AS?

OSLO AIRPORT PROPERTY AS had revenue of NOK 11.3m in 2025.

Where is OSLO AIRPORT PROPERTY AS based?

OSLO AIRPORT PROPERTY AS has its business address in Gardermoen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.