BIZTRAC BETA
Manufacture of other fabricated metal products n.e.c.

HASUND MEK. VERKSTED AS

Org. no. 912443663 Limited company (AS) Ulstein Incorporated 1947 Active
Ownership graph ↗
Revenue 2025 NOK 8.7m
Operating profit NOK 1.2m
Equity NOK 7.6m
Incorporated 1947
Share capital NOK 2.1m

HASUND MEK. VERKSTED AS is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 912443663. The business is classified under manufacture of other fabricated metal products n.e.c. (NACE 25.990). The company was incorporated in 1947. Registered share capital is NOK 2.1m, divided into 4540 shares. The company's stated purpose is: “Drive skipsverft og mekanisk verksted, eiendomsutvikling og akjsinvesteringer, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.7m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 8.7m
Operating profit
NOK 1.2m
Equity
NOK 7.6m
Est. value
NOK 9.0m

Financial health · 2025

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

Who owns HASUND MEK. VERKSTED AS?

SOLVOLL INVEST AS
HASUND MEK. VERKSTED AS
NOK 8.7m rev. · NOK 1.2m profit

HASUND MEK. VERKSTED AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HASUND MEK. VERKSTED AS

Who owns HASUND MEK. VERKSTED AS?

SOLVOLL INVEST AS is the largest registered owner, with 80.0%.

What is the revenue of HASUND MEK. VERKSTED AS?

HASUND MEK. VERKSTED AS had revenue of NOK 8.7m in 2025.

Who is the general manager of HASUND MEK. VERKSTED AS?

Vegard Hasund is registered as general manager of HASUND MEK. VERKSTED AS.

Where is HASUND MEK. VERKSTED AS based?

HASUND MEK. VERKSTED AS has its business address in Ulsteinvik.

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.