BIZTRAC BETA
Other captive investment companies

LAGOPUS MUTUS AS

Org. no. 965188193 Limited company (AS) Oslo Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 28.7m
Operating profit NOK 28.5m
Equity NOK 317.1m
Incorporated 1992
Share capital NOK 59.2m

LAGOPUS MUTUS AS is registered as a limited company in Oslo, Oslo with organisation number 965188193. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 1992. Registered share capital is NOK 59.2m, divided into 197500 shares. The company's stated purpose is: “Å gjøre investeringer i andre selskaper, fast eiendom, skip, bore- og entreprenørvirksomhet i havet, handel, konsulenttjenester og hva dermed står i forbindelse med angitt virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.7m in revenue and NOK 28.5m in operating profit.

Key figures · 2024

Revenue
NOK 28.7m
Operating profit
NOK 28.5m
Equity
NOK 317.1m
Est. value
NOK 255.1m

Financial health · 2024

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

Who owns LAGOPUS MUTUS AS?

CUMULUS INVEST AS
LAGOPUS MUTUS AS
NOK 28.7m rev. · NOK 28.5m profit

LAGOPUS MUTUS AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LAGOPUS MUTUS AS er morselskap for 3 datterselskaper:

Frequently asked questions about LAGOPUS MUTUS AS

Who owns LAGOPUS MUTUS AS?

CUMULUS INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LAGOPUS MUTUS AS?

LAGOPUS MUTUS AS had revenue of NOK 28.7m in 2024.

Who is the general manager of LAGOPUS MUTUS AS?

Esben Adolf Riddervold is registered as general manager of LAGOPUS MUTUS AS.

Where is LAGOPUS MUTUS AS based?

LAGOPUS MUTUS 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.