BIZTRAC BETA
Development of building projects

CAVU EIENDOM AS

Org. no. 925850462 Limited company (AS) Eidsvoll Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 640,000
Operating profit NOK 398,000
Equity NOK −358,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

CAVU EIENDOM AS is registered as a limited company in Eidsvoll, Akershus with organisation number 925850462. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eiendomsutvikling, utleie, formidling, investering, renovering, kjøp og salg av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 640,000 in revenue and NOK 398,000 in operating profit.

Key figures · 2024

Revenue
NOK 640,000
Operating profit
NOK 398,000
Equity
NOK −358,000
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
5.73
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-6.5%
Weak
Equity as a share of total capital

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

Who owns CAVU EIENDOM AS?

CATHRINE LOSO-NGUYEN
CAVU EIENDOM AS
NOK 640,000 rev. · NOK 398,000 profit

CAVU EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CAVU EIENDOM AS

Who owns CAVU EIENDOM AS?

CATHRINE LOSO-NGUYEN is the largest registered owner, with 50.0%.

What is the revenue of CAVU EIENDOM AS?

CAVU EIENDOM AS had revenue of NOK 640,000 in 2024.

Who is the general manager of CAVU EIENDOM AS?

Olav Loso-Nguyen is registered as general manager of CAVU EIENDOM AS.

Where is CAVU EIENDOM AS based?

CAVU EIENDOM AS has its business address in Eidsvoll Verk.

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.