BIZTRAC BETA
Uoppgitt

CHRISTOFFER OLSTAD HOLDING AS

Org. no. 933717933 Limited company (AS) Gjerdrum Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −2
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2 kr).

CHRISTOFFER OLSTAD HOLDING AS is registered as a limited company in Gjerdrum, Akershus with organisation number 933717933. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Holdingsselskap der hovedvirksomheten innebærer kjøp, salg, utvikling, investering, drift og forvaltning av direkte og indirekte eierinteresser.”.

Key figures · 2024

Operating profit
NOK −2
Equity
NOK 24,000
Est. value
NOK 28,000

Financial health · 2024

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns CHRISTOFFER OLSTAD HOLDING AS?

CHRISTOFFER OLSTAD
CHRISTOFFER OLSTAD HOLDING AS
· NOK −2 profit

CHRISTOFFER OLSTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CHRISTOFFER OLSTAD HOLDING AS own?

CHRISTOFFER OLSTAD HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about CHRISTOFFER OLSTAD HOLDING AS

Who owns CHRISTOFFER OLSTAD HOLDING AS?

CHRISTOFFER OLSTAD is the largest registered owner, with 100.0%.

Who is the general manager of CHRISTOFFER OLSTAD HOLDING AS?

Christoffer Olstad is registered as general manager of CHRISTOFFER OLSTAD HOLDING AS.

Where is CHRISTOFFER OLSTAD HOLDING AS based?

CHRISTOFFER OLSTAD HOLDING AS has its business address in Gjerdrum.

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.