BIZTRAC BETA
Buying and selling of own real estate

CAMBRIDGE HOLDING AS

Org. no. 984124104 Limited company (AS) Oslo Incorporated 2001 Active
Ownership graph ↗
Operating profit NOK −1.2m
Equity NOK 1.2m
Incorporated 2001
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,2 mill kr).

CAMBRIDGE HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 984124104. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Konsulentvirksomhet, kjøpe, eie, forvalte og selge fast eiendom, løsøre- herunder aksjer og verdipapirer, skip, skipsparter, skipsmegling, finansiering og alt som naturlig knytter sag til dette, herunder deltagelse i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −1.2m
Equity
NOK 1.2m
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
1.46
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.0%
Good
Equity as a share of total capital

Who owns CAMBRIDGE HOLDING AS?

ANNICA KRISTINA TRONSTAD
CAMBRIDGE HOLDING AS
· NOK −1.2m profit

CAMBRIDGE HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does CAMBRIDGE HOLDING AS own?

CAMBRIDGE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CAMBRIDGE HOLDING AS

Who owns CAMBRIDGE HOLDING AS?

ANNICA KRISTINA TRONSTAD is the largest registered owner, with 80.0%.

Who is the general manager of CAMBRIDGE HOLDING AS?

Felix Alexander Tronstad is registered as general manager of CAMBRIDGE HOLDING AS.

Where is CAMBRIDGE HOLDING AS based?

CAMBRIDGE HOLDING 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.