BIZTRAC BETA
Machining of metals

K.THORBERGSEN MEKANISKE AS

Org. no. 990018472 Limited company (AS) Hamarøy Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 12.9m
Operating profit NOK 9.6m
Equity NOK 13.2m
Incorporated 2006
Share capital NOK 100,000

K.THORBERGSEN MEKANISKE AS is registered as a limited company in Hamarøy, Nordland with organisation number 990018472. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Sveiseverksted. Selskapet skal også kunne drive og/eller delta i annen næringsvirksomhet, herunder aksjekjøp, egen virksomhet eller lignende.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.9m in revenue and NOK 9.6m in operating profit.

Key figures · 2025

Revenue
NOK 12.9m
Operating profit
NOK 9.6m
Equity
NOK 13.2m
Est. value
NOK 38.4m

Financial health · 2025

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

Who owns K.THORBERGSEN MEKANISKE AS?

KNUT ARNE THORBERGSEN
K.THORBERGSEN MEKANISKE AS
NOK 12.9m rev. · NOK 9.6m profit

K.THORBERGSEN MEKANISKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about K.THORBERGSEN MEKANISKE AS

Who owns K.THORBERGSEN MEKANISKE AS?

KNUT ARNE THORBERGSEN is the largest registered owner, with 100.0%.

What is the revenue of K.THORBERGSEN MEKANISKE AS?

K.THORBERGSEN MEKANISKE AS had revenue of NOK 12.9m in 2025.

Who is the general manager of K.THORBERGSEN MEKANISKE AS?

Knut Arne Thorbergsen is registered as general manager of K.THORBERGSEN MEKANISKE AS.

Where is K.THORBERGSEN MEKANISKE AS based?

K.THORBERGSEN MEKANISKE AS has its business address in Hamarøy.

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.