BIZTRAC BETA
Civil engineering activities

CASORO AS

Org. no. 987553421 Limited company (AS) Bærum Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 2.1m
Equity NOK 27.9m
Incorporated 2004
Share capital NOK 150,000

CASORO AS is registered as a limited company in Bærum, Akershus with organisation number 987553421. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2004. Registered share capital is NOK 150,000, divided into 150374 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå investering i aksjer og annen virksomhet beslektet med denne, samt handel med aksjer og verdipapirer, herunder lånefinansierte investeringer med verdipapirer og valuta, hvor selskapet kan pantsette sine aktiver i den forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 2.1m
Equity
NOK 27.9m
Est. value
NOK 20.4m

Financial health · 2025

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

Who owns CASORO AS?

MTS EIENDOM AS
CASORO AS
NOK 3.0m rev. · NOK 2.1m profit

CASORO AS has 6 registered shareholders:

All shareholders and roles →

Which companies does CASORO AS own?

CASORO AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about CASORO AS

Who owns CASORO AS?

MTS EIENDOM AS is the largest registered owner, with 39.9%.

What is the revenue of CASORO AS?

CASORO AS had revenue of NOK 3.0m in 2025.

Where is CASORO AS based?

CASORO AS has its business address in Slependen.

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.