BIZTRAC BETA
Rental and operating of own or leased real estate

CAMUS EIENDOM AS

Org. no. 990375313 Limited company (AS) Lindesnes Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 55,000
Operating profit NOK 968
Equity NOK 985,000
Incorporated 2006
Share capital NOK 1.0m

Signals

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

CAMUS EIENDOM AS is registered as a limited company in Lindesnes, Agder with organisation number 990375313. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investering i eiendom, andre selskaper og utleie, samt annen økonomisk virksomhet som naturlig ligger under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 55,000 in revenue and NOK 968 in operating profit.

Key figures · 2024

Revenue
NOK 55,000
Operating profit
NOK 968
Equity
NOK 985,000
Est. value
NOK 676,000

Financial health · 2024

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

Who owns CAMUS EIENDOM AS?

DEHOLT GRUPPEN AS
CAMUS EIENDOM AS
NOK 55,000 rev. · NOK 968 profit

CAMUS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

CAMUS EIENDOM AS er morselskap for 4 datterselskaper:

Frequently asked questions about CAMUS EIENDOM AS

Who owns CAMUS EIENDOM AS?

DEHOLT GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of CAMUS EIENDOM AS?

CAMUS EIENDOM AS had revenue of NOK 55,000 in 2024.

Where is CAMUS EIENDOM AS based?

CAMUS EIENDOM AS has its business address in Bjelland.

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.