BIZTRAC BETA
Civil engineering activities

DAHLHAUG AS

Org. no. 931313495 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −25,000
Equity NOK 33,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−25k kr).

DAHLHAUG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 931313495. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen konsulenttjenester - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −25,000
Equity
NOK 33,000
Est. value
NOK 54,000

Financial health · 2024

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

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

Who owns DAHLHAUG AS?

JOHN ESPEN DAHLHAUG
DAHLHAUG AS
NOK 0 rev. · NOK −25,000 profit

DAHLHAUG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DAHLHAUG AS

Who owns DAHLHAUG AS?

JOHN ESPEN DAHLHAUG is the largest registered owner, with 100.0%.

What is the revenue of DAHLHAUG AS?

DAHLHAUG AS had revenue of NOK 0 in 2025.

Who is the general manager of DAHLHAUG AS?

John Espen Dahlhaug is registered as general manager of DAHLHAUG AS.

Where is DAHLHAUG AS based?

DAHLHAUG AS has its business address in Tiller.

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.