BIZTRAC BETA
Machining of metals

STÅLSENTERET AS

Org. no. 992688343 Limited company (AS) Karmøy Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 35.9m
Operating profit NOK 15,000
Equity NOK 7.6m
Incorporated 2008
Employees 9
Share capital NOK 1.3m

STÅLSENTERET AS is registered as a limited company in Karmøy, Rogaland with organisation number 992688343. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2008 and has 9 registered employees. Registered share capital is NOK 1.3m, divided into 1332 shares. The company's stated purpose is: “Engroshandel med metaller og metallholdig malm, bearbeiding av metaller, forvalte aksjer og eiendom, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 35.9m in revenue and NOK 15,000 in operating profit.

Key figures · 2025

Revenue
NOK 35.9m
Operating profit
NOK 15,000
Equity
NOK 7.6m
Est. value
NOK 4.1m

Financial health · 2025

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

Who owns STÅLSENTERET AS?

TIBNOR AKTIEBOLAG (556004-4447)
STÅLSENTERET AS
NOK 35.9m rev. · NOK 15,000 profit

STÅLSENTERET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STÅLSENTERET AS

Who owns STÅLSENTERET AS?

TIBNOR AKTIEBOLAG (556004-4447) is the largest registered owner, with 100.0%.

What is the revenue of STÅLSENTERET AS?

STÅLSENTERET AS had revenue of NOK 35.9m in 2025.

Who is the general manager of STÅLSENTERET AS?

Hege Elisabeth Sjursen Ekornsæter is registered as general manager of STÅLSENTERET AS.

Where is STÅLSENTERET AS based?

STÅLSENTERET AS has its business address in Torvastad.

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.