BIZTRAC BETA
Site preparation

HOVDANE MASKIN AS

Org. no. 918423222 Limited company (AS) Kvam Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 5.1m
Operating profit NOK −560,000
Equity NOK 1.4m
Incorporated 2016
Share capital NOK 140,000

Signals

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

HOVDANE MASKIN AS is registered as a limited company in Kvam, Vestland with organisation number 918423222. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2016. Registered share capital is NOK 140,000, divided into 100 shares. The company's stated purpose is: “Anleggsvirksomhet med graving, boring, transport og snørydding, herunder å delta i andre selskaper med lignende virksomhet, samt kjøp og salg av aksjer og eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.1m in revenue and NOK −560,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.1m
Operating profit
NOK −560,000
Equity
NOK 1.4m
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns HOVDANE MASKIN AS?

GEIRMUND VIK HOVDANE
HOVDANE MASKIN AS
NOK 5.1m rev. · NOK −560,000 profit

HOVDANE MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOVDANE MASKIN AS

Who owns HOVDANE MASKIN AS?

GEIRMUND VIK HOVDANE is the largest registered owner, with 100.0%.

What is the revenue of HOVDANE MASKIN AS?

HOVDANE MASKIN AS had revenue of NOK 5.1m in 2024.

Who is the general manager of HOVDANE MASKIN AS?

Geirmund Vik Hovdane is registered as general manager of HOVDANE MASKIN AS.

Where is HOVDANE MASKIN AS based?

HOVDANE MASKIN AS has its business address in Ålvik.

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.