BIZTRAC BETA
Manufacture of metal structures and parts of structures

HANSEN MEKANISKE AS

Org. no. 977175623 Limited company (AS) Bergen Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 13.2m
Operating profit NOK 1.4m
Equity NOK 8.3m
Incorporated 1997
Employees 8
Share capital NOK 514,000

HANSEN MEKANISKE AS is registered as a limited company in Bergen, Vestland with organisation number 977175623. The business is classified under manufacture of metal structures and parts of structures (NACE 25.110). The company was incorporated in 1997 and has 8 registered employees. Registered share capital is NOK 514,000, divided into 514 shares. The company's stated purpose is: “Produksjon av metallkonstruksjoner og deler, samt det som naturlig hører inn under slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.2m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 13.2m
Operating profit
NOK 1.4m
Equity
NOK 8.3m
Est. value
NOK 11.1m

Financial health · 2024

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

Who owns HANSEN MEKANISKE AS?

HANSEN EIENDOMSINVEST AS
HANSEN MEKANISKE AS
NOK 13.2m rev. · NOK 1.4m profit

HANSEN MEKANISKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HANSEN MEKANISKE AS

Who owns HANSEN MEKANISKE AS?

HANSEN EIENDOMSINVEST AS is the largest registered owner, with 100.0%.

What is the revenue of HANSEN MEKANISKE AS?

HANSEN MEKANISKE AS had revenue of NOK 13.2m in 2024.

Who is the general manager of HANSEN MEKANISKE AS?

Tore Raymond Hansen is registered as general manager of HANSEN MEKANISKE AS.

Where is HANSEN MEKANISKE AS based?

HANSEN MEKANISKE AS has its business address in Blomsterdalen.

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.