BIZTRAC BETA
Buying and selling of own real estate

CALADAN AS

Org. no. 911865157 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 40,000
Operating profit NOK −34,000
Equity NOK 207,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

CALADAN AS is registered as a limited company in Oslo, Oslo with organisation number 911865157. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp og salg av aksjer og andeler i andre virksomheter, kjøp, salg og utleie av fast eiendom, samt konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 40,000 in revenue and NOK −34,000 in operating profit.

Key figures · 2025

Revenue
NOK 40,000
Operating profit
NOK −34,000
Equity
NOK 207,000
Est. value
NOK 313,000

Financial health · 2025

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

Who owns CALADAN AS?

CHRISTOFFER NÆSS
CALADAN AS
NOK 40,000 rev. · NOK −34,000 profit

CALADAN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CALADAN AS own?

CALADAN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CALADAN AS

Who owns CALADAN AS?

CHRISTOFFER NÆSS is the largest registered owner, with 100.0%.

What is the revenue of CALADAN AS?

CALADAN AS had revenue of NOK 40,000 in 2025.

Who is the general manager of CALADAN AS?

Christoffer Næss is registered as general manager of CALADAN AS.

Where is CALADAN AS based?

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