BIZTRAC BETA
COMPANY REGISTER PROFILE
929196384 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

MORTEN DAHL HOLDING AS

Org. no. 929196384 Limited company (AS) Larvik Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 4,000
Operating profit NOK 0
Equity NOK 1.9m
Incorporated 2022
Share capital NOK 36,000

Signals

1 flags
  • Nylig endring 2026-06-14 Adresseendring registrert 2026-06-14.

MORTEN DAHL HOLDING AS is registered as a limited company in Larvik, Vestfold with organisation number 929196384. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 36,000, divided into 36000 shares. The company's stated purpose is: “Eie og investere i aksjer og virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4,000 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 4,000
Operating profit
NOK 0
Equity
NOK 1.9m
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns MORTEN DAHL HOLDING AS?

MORTEN DAHL
MORTEN DAHL HOLDING AS
NOK 4,000 rev. · NOK 0 profit

MORTEN DAHL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MORTEN DAHL HOLDING AS

Who owns MORTEN DAHL HOLDING AS?

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

What is the revenue of MORTEN DAHL HOLDING AS?

MORTEN DAHL HOLDING AS had revenue of NOK 4,000 in 2025.

Who is the general manager of MORTEN DAHL HOLDING AS?

Morten Dahl is registered as general manager of MORTEN DAHL HOLDING AS.

Where is MORTEN DAHL HOLDING AS based?

MORTEN DAHL HOLDING AS has its business address in Stavern.

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.