BIZTRAC BETA
Rental and operating of own or leased real estate

CALAS EIENDOM AS

Org. no. 976966236 Limited company (AS) Oslo Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 271,000
Operating profit NOK −69,000
Equity NOK 414,000
Incorporated 1996
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−69k kr).

CALAS EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 976966236. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift, utleie av fast eiendom, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 271,000 in revenue and NOK −69,000 in operating profit.

Key figures · 2025

Revenue
NOK 271,000
Operating profit
NOK −69,000
Equity
NOK 414,000
Est. value
NOK 703,000

Financial health · 2025

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

Who owns CALAS EIENDOM AS?

PÅL ERIK BERGER
CALAS EIENDOM AS
NOK 271,000 rev. · NOK −69,000 profit

CALAS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CALAS EIENDOM AS own?

CALAS EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CALAS EIENDOM AS

Who owns CALAS EIENDOM AS?

PÅL ERIK BERGER is the largest registered owner, with 100.0%.

What is the revenue of CALAS EIENDOM AS?

CALAS EIENDOM AS had revenue of NOK 271,000 in 2025.

Where is CALAS EIENDOM AS based?

CALAS EIENDOM 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.