BIZTRAC BETA
Repair and maintenance of machinery

HESSA MEKANISKE AS

Org. no. 980526402 Limited company (AS) Ålesund Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 994,000
Equity NOK 4.8m
Incorporated 1999
Share capital NOK 100,000

HESSA MEKANISKE AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 980526402. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive mekanisk verksted med sveisefabrikasjon og reparasjonsvirksomhet, agenturvirksomhet, kjøp og salg og alt hva dermed står i forbindelse, samt å eie aksjer eller på andre måter delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 994,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 994,000
Equity
NOK 4.8m
Est. value
NOK 6.3m

Financial health · 2025

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

Who owns HESSA MEKANISKE AS?

PER ARVE DIMMEN
HESSA MEKANISKE AS
NOK 3.1m rev. · NOK 994,000 profit

HESSA MEKANISKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HESSA MEKANISKE AS

Who owns HESSA MEKANISKE AS?

PER ARVE DIMMEN is the largest registered owner, with 100.0%.

What is the revenue of HESSA MEKANISKE AS?

HESSA MEKANISKE AS had revenue of NOK 3.1m in 2025.

Who is the general manager of HESSA MEKANISKE AS?

Per Arve Dimmen is registered as general manager of HESSA MEKANISKE AS.

Where is HESSA MEKANISKE AS based?

HESSA MEKANISKE AS has its business address in Ålesund.

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.