BIZTRAC BETA
Rental and operating of own or leased real estate

AIRSPACE HOLDING AS

Org. no. 989113704 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 860,000
Equity NOK 72.2m
Incorporated 2005
Share capital NOK 89,000

AIRSPACE HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 989113704. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 89,000, divided into 1 shares. The company's stated purpose is: “Investering i aksjer, verdipapirer og deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 860,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 860,000
Equity
NOK 72.2m
Est. value
NOK 52.0m

Financial health · 2024

Liquidity
37.52
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
98.4%
Very good
Equity as a share of total capital

Who owns AIRSPACE HOLDING AS?

JAN IVAR LJOSLAND
AIRSPACE HOLDING AS
NOK 1.7m rev. · NOK 860,000 profit

AIRSPACE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AIRSPACE HOLDING AS own?

AIRSPACE HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about AIRSPACE HOLDING AS

Who owns AIRSPACE HOLDING AS?

JAN IVAR LJOSLAND is the largest registered owner, with 100.0%.

What is the revenue of AIRSPACE HOLDING AS?

AIRSPACE HOLDING AS had revenue of NOK 1.7m in 2024.

Who is the general manager of AIRSPACE HOLDING AS?

Madelen Ljosland is registered as general manager of AIRSPACE HOLDING AS.

Where is AIRSPACE HOLDING AS based?

AIRSPACE HOLDING AS has its business address in Oslo.

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

Report a problem

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