BIZTRAC BETA
Rental and operating of own or leased real estate

OIV HOLDING AS

Org. no. 926092154 Limited company (AS) Modum Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −42,000
Equity NOK 17.2m
Incorporated 2020
Share capital NOK 932,000

Signals

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

OIV HOLDING AS is registered as a limited company in Modum, Buskerud with organisation number 926092154. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 932,000, divided into 84 shares. The company's stated purpose is: “Å investere i aksjer, andeler i selskap etter selskapsloven, utenlandske selskaper, obligasjoner, fast eiendom og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −42,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −42,000
Equity
NOK 17.2m
Est. value
NOK 19.4m

Financial health · 2024

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

Who owns OIV HOLDING AS?

MORTEN STRAND
OIV HOLDING AS
NOK 0 rev. · NOK −42,000 profit

OIV HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OIV HOLDING AS own?

OIV HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about OIV HOLDING AS

Who owns OIV HOLDING AS?

MORTEN STRAND is the largest registered owner, with 100.0%.

What is the revenue of OIV HOLDING AS?

OIV HOLDING AS had revenue of NOK 0 in 2024.

Where is OIV HOLDING AS based?

OIV HOLDING AS has its business address in Vikersund.

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.