BIZTRAC BETA
Rental and operating of own or leased real estate

OLKV HOLDING AS

Org. no. 921664397 Limited company (AS) Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK −1.1m
Equity NOK 61.4m
Incorporated 2018
Share capital NOK 32,000

Signals

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

OLKV HOLDING AS is registered as a limited company in Hå, Rogaland with organisation number 921664397. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 32,000, divided into 2265440 shares. The company's stated purpose is: “Å investere i aksjer og andre selskaper og virksomheter, herunder deltakelse av enhver art i andre virksomheter, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK −1.1m in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK −1.1m
Equity
NOK 61.4m
Est. value
NOK 46.7m

Financial health · 2025

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

Who owns OLKV HOLDING AS?

OLAV KVIA
OLKV HOLDING AS
NOK 3.1m rev. · NOK −1.1m profit

OLKV HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OLKV HOLDING AS own?

OLKV HOLDING AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about OLKV HOLDING AS

Who owns OLKV HOLDING AS?

OLAV KVIA is the largest registered owner, with 100.0%.

What is the revenue of OLKV HOLDING AS?

OLKV HOLDING AS had revenue of NOK 3.1m in 2025.

Where is OLKV HOLDING AS based?

OLKV HOLDING AS has its business address in Nærbø.

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.