BIZTRAC BETA
Site preparation

OVE DAHL HOLDING AS

Org. no. 994915118 Limited company (AS) Larvik Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 188,000
Operating profit NOK 92,000
Equity NOK −58,000
Incorporated 2009
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−58k kr).

OVE DAHL HOLDING AS is registered as a limited company in Larvik, Vestfold with organisation number 994915118. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Konsulentvirksomhet knyttet til maskinentreprenørvirksomhet, samt investering og deltagelse i andre selskaper”. The most recent filed accounts, for the 2024 financial year, show NOK 188,000 in revenue and NOK 92,000 in operating profit.

Key figures · 2024

Revenue
NOK 188,000
Operating profit
NOK 92,000
Equity
NOK −58,000
Est. value
NOK 461,000

Financial health · 2024

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

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

Who owns OVE DAHL HOLDING AS?

OVE DAHL
OVE DAHL HOLDING AS
NOK 188,000 rev. · NOK 92,000 profit

OVE DAHL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OVE DAHL HOLDING AS

Who owns OVE DAHL HOLDING AS?

OVE DAHL is the largest registered owner, with 100.0%.

What is the revenue of OVE DAHL HOLDING AS?

OVE DAHL HOLDING AS had revenue of NOK 188,000 in 2024.

Who is the general manager of OVE DAHL HOLDING AS?

Ove Dahl is registered as general manager of OVE DAHL HOLDING AS.

Where is OVE DAHL HOLDING AS based?

OVE DAHL HOLDING AS has its business address in Larvik.

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.