BIZTRAC BETA
Development of building projects

LUXHUS AS

Org. no. 920628982 Limited company (AS) Ålesund Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 58,000
Equity NOK −944,000
Incorporated 2018
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−944k kr).

LUXHUS AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 920628982. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Eie, utvikle og drive eiendom og forvalte aksjer og dertil hørende virksomhet. Selskapet kan også delta i andre selskaper og virksomheter når dette samsvarer med selskapets formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 58,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 58,000
Equity
NOK −944,000
Est. value
NOK 345,000

Financial health · 2024

Liquidity
0.34
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-669.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LUXHUS AS?

CHRISTOPHER ROBIN AAHJEM
LUXHUS AS
NOK 0 rev. · NOK 58,000 profit

LUXHUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUXHUS AS

Who owns LUXHUS AS?

CHRISTOPHER ROBIN AAHJEM is the largest registered owner, with 100.0%.

What is the revenue of LUXHUS AS?

LUXHUS AS had revenue of NOK 0 in 2024.

Who is the general manager of LUXHUS AS?

Christopher Robin Aahjem is registered as general manager of LUXHUS AS.

Where is LUXHUS AS based?

LUXHUS AS has its business address in Ørskog.

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.