BIZTRAC BETA
Other technical consultancy

HSX MASKINUTVIKLING AS

Org. no. 985338736 Limited company (AS) Bamble Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 13.0m
Operating profit NOK 598,000
Equity NOK 6.5m
Incorporated 2002
Employees 5
Share capital NOK 100,000

HSX MASKINUTVIKLING AS is registered as a limited company in Bamble, Telemark with organisation number 985338736. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2002 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive med handel, konsulent- og servicevirksomhet, eie og forvalte fast eiendom, samt ved aksjetegning eller på annen måte delta i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.0m in revenue and NOK 598,000 in operating profit.

Key figures · 2025

Revenue
NOK 13.0m
Operating profit
NOK 598,000
Equity
NOK 6.5m
Est. value
NOK 7.0m

Financial health · 2025

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

Who owns HSX MASKINUTVIKLING AS?

HALVOR SANNES
HSX MASKINUTVIKLING AS
NOK 13.0m rev. · NOK 598,000 profit

HSX MASKINUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HSX MASKINUTVIKLING AS

Who owns HSX MASKINUTVIKLING AS?

HALVOR SANNES is the largest registered owner, with 100.0%.

What is the revenue of HSX MASKINUTVIKLING AS?

HSX MASKINUTVIKLING AS had revenue of NOK 13.0m in 2025.

Who is the general manager of HSX MASKINUTVIKLING AS?

Halvor Sannes is registered as general manager of HSX MASKINUTVIKLING AS.

Where is HSX MASKINUTVIKLING AS based?

HSX MASKINUTVIKLING AS has its business address in Stathelle.

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.