BIZTRAC BETA
Machining of metals

NAMSEN MEKANISKE AS

Org. no. 820705262 Limited company (AS) Overhalla Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 519,000
Equity NOK 792,000
Incorporated 2018
Share capital NOK 60,000

NAMSEN MEKANISKE AS is registered as a limited company in Overhalla, Trøndelag with organisation number 820705262. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2018. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Verksteddrift med konstruksjon, produksjon og reparasjon innen mekanisk industri, salg av materiell, samt annen virksomhet som naturlig faller inn under dette. Selskapet kan også delta i annen virksomhet, også gjennom aksjer og andeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 519,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 519,000
Equity
NOK 792,000
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns NAMSEN MEKANISKE AS?

RUNE HANSEN
NAMSEN MEKANISKE AS
NOK 1.9m rev. · NOK 519,000 profit

NAMSEN MEKANISKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NAMSEN MEKANISKE AS

Who owns NAMSEN MEKANISKE AS?

RUNE HANSEN is the largest registered owner, with 100.0%.

What is the revenue of NAMSEN MEKANISKE AS?

NAMSEN MEKANISKE AS had revenue of NOK 1.9m in 2025.

Who is the general manager of NAMSEN MEKANISKE AS?

Rune Hansen is registered as general manager of NAMSEN MEKANISKE AS.

Where is NAMSEN MEKANISKE AS based?

NAMSEN MEKANISKE AS has its business address in Overhalla.

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.