BIZTRAC BETA
Site preparation

SVEIN HOVDAHL AS

Org. no. 890025242 Limited company (AS) Trondheim Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK −135,000
Equity NOK 712,000
Incorporated 2006
Share capital NOK 100,000

Signals

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

SVEIN HOVDAHL AS is registered as a limited company in Trondheim, Trøndelag with organisation number 890025242. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Riving av bygninger og flytting av masse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK −135,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK −135,000
Equity
NOK 712,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns SVEIN HOVDAHL AS?

SVEIN GUNNAR HOVDAHL
SVEIN HOVDAHL AS
NOK 2.3m rev. · NOK −135,000 profit

SVEIN HOVDAHL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SVEIN HOVDAHL AS own?

SVEIN HOVDAHL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SVEIN HOVDAHL AS

Who owns SVEIN HOVDAHL AS?

SVEIN GUNNAR HOVDAHL is the largest registered owner, with 100.0%.

What is the revenue of SVEIN HOVDAHL AS?

SVEIN HOVDAHL AS had revenue of NOK 2.3m in 2024.

Who is the general manager of SVEIN HOVDAHL AS?

Svein Gunnar Hovdahl is registered as general manager of SVEIN HOVDAHL AS.

Where is SVEIN HOVDAHL AS based?

SVEIN HOVDAHL AS has its business address in Trondheim.

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.