BIZTRAC BETA
Other captive investment companies

CAROMA AS

Org. no. 915008062 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 1.2m
Equity NOK 21.1m
Incorporated 2015
Share capital NOK 80,000

CAROMA AS is registered as a limited company in Oslo, Oslo with organisation number 915008062. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 80,000, divided into 100 shares. The company's stated purpose is: “Drive investeringsvirksomhet gjennom eierskap i aksjer, andeler, eiendom og annet. Videre å drive eiendomsutvikling og eiendomsforvaltning og yte konsulenttjenester innen forretningsutvikling, økonomistyring, finansiering, bygg og anleggsbransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 1.2m
Equity
NOK 21.1m
Est. value
NOK 15.2m

Financial health · 2025

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

Who owns CAROMA AS?

LARS FRANG RIISE
CAROMA AS
NOK 1.2m rev. · NOK 1.2m profit

CAROMA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CAROMA AS own?

CAROMA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CAROMA AS

Who owns CAROMA AS?

LARS FRANG RIISE is the largest registered owner, with 100.0%.

What is the revenue of CAROMA AS?

CAROMA AS had revenue of NOK 1.2m in 2025.

Who is the general manager of CAROMA AS?

Lars Frang Riise is registered as general manager of CAROMA AS.

Where is CAROMA AS based?

CAROMA 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.