BIZTRAC BETA
Machining of metals

STM MASKINERING AS

Org. no. 990663467 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 36.1m
Operating profit NOK 2.2m
Equity NOK 12.3m
Incorporated 2006
Employees 14
Share capital NOK 1.2m

STM MASKINERING AS is registered as a limited company in Bergen, Vestland with organisation number 990663467. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2006 and has 14 registered employees. Registered share capital is NOK 1.2m, divided into 1000 shares. The company's stated purpose is: “Mekanisk produksjon og handel samt eierskap i selskaper som er naturlig og som står i dets forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 36.1m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 36.1m
Operating profit
NOK 2.2m
Equity
NOK 12.3m
Est. value
NOK 15.9m

Financial health · 2024

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

Who owns STM MASKINERING AS?

BYFJORD AS
STM MASKINERING AS
NOK 36.1m rev. · NOK 2.2m profit

STM MASKINERING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does STM MASKINERING AS own?

STM MASKINERING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about STM MASKINERING AS

Who owns STM MASKINERING AS?

BYFJORD AS is the largest registered owner, with 40.0%.

What is the revenue of STM MASKINERING AS?

STM MASKINERING AS had revenue of NOK 36.1m in 2024.

Who is the general manager of STM MASKINERING AS?

Sindre Buen Eidsnes is registered as general manager of STM MASKINERING AS.

Where is STM MASKINERING AS based?

STM MASKINERING AS has its business address in Laksevåg.

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.