BIZTRAC BETA
Uoppgitt

OCV HOLDING AS

Org. no. 927984741 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK 5.0m
Incorporated 2021
Share capital NOK 30,000

Signals

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

OCV HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 927984741. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investere i verdipapirer, eiendom og andre produkter - og tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, samt kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 5.0m
Est. value
NOK 12.0m

Financial health · 2024

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

Who owns OCV HOLDING AS?

OLE CHRISTIAN PETTERSEN
OCV HOLDING AS
NOK 0 rev. · NOK −7,000 profit

OCV HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does OCV HOLDING AS own?

OCV HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OCV HOLDING AS

Who owns OCV HOLDING AS?

OLE CHRISTIAN PETTERSEN is the largest registered owner, with 80.0%.

What is the revenue of OCV HOLDING AS?

OCV HOLDING AS had revenue of NOK 0 in 2024.

Where is OCV HOLDING AS based?

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