BIZTRAC BETA
Uoppgitt

XO SKYLEASE AS

Org. no. 824832242 Limited company (AS) Søndre Land Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 3.9m
Equity NOK 1.8m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

XO SKYLEASE AS is registered as a limited company in Søndre Land, Innlandet with organisation number 824832242. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i selskaper, kjøp av virksomhet, investering i eiendom og utleie av helikopter og det som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 3.9m in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 3.9m
Equity
NOK 1.8m
Est. value
NOK 11.8m

Financial health · 2025

Liquidity
1.54
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.5%
Good
Equity as a share of total capital

Who owns XO SKYLEASE AS?

XO GROUP AS
XO SKYLEASE AS
NOK 4.4m rev. · NOK 3.9m profit

XO SKYLEASE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

XO SKYLEASE AS er morselskap for 9 datterselskaper:

Frequently asked questions about XO SKYLEASE AS

Who owns XO SKYLEASE AS?

XO GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of XO SKYLEASE AS?

XO SKYLEASE AS had revenue of NOK 4.4m in 2025.

Who is the general manager of XO SKYLEASE AS?

Mads Engen Sopp is registered as general manager of XO SKYLEASE AS.

Where is XO SKYLEASE AS based?

XO SKYLEASE AS has its business address in Hov.

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.