BIZTRAC BETA
Wholesale of metals and metal ores

SVERDRUP STEEL AS

Org. no. 862380592 Limited company (AS) Stavanger Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 2.3bn
Operating profit NOK 268.2m
Equity NOK 1.0bn
Incorporated 1991
Employees 43
Share capital NOK 5.0m

SVERDRUP STEEL AS is registered as a limited company in Stavanger, Rogaland with organisation number 862380592. The business is classified under wholesale of metals and metal ores (NACE 46.820). The company was incorporated in 1991 and has 43 registered employees. Registered share capital is NOK 5.0m, divided into 8850 shares. The company's stated purpose is: “Handel og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3bn in revenue and NOK 268.2m in operating profit.

Key figures · 2024

Revenue
NOK 2.3bn
Operating profit
NOK 268.2m
Equity
NOK 1.0bn
Est. value
NOK 1.5bn

Financial health · 2024

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

Who owns SVERDRUP STEEL AS?

SVERDRUP HOLDINGS INC
SVERDRUP STEEL AS
NOK 2.3bn rev. · NOK 268.2m profit

SVERDRUP STEEL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SVERDRUP STEEL AS own?

SVERDRUP STEEL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SVERDRUP STEEL AS

Who owns SVERDRUP STEEL AS?

SVERDRUP HOLDINGS INC is the largest registered owner, with 100.0%.

What is the revenue of SVERDRUP STEEL AS?

SVERDRUP STEEL AS had revenue of NOK 2.3bn in 2024.

Who is the general manager of SVERDRUP STEEL AS?

Kristian Gjerdrum Rosenberg is registered as general manager of SVERDRUP STEEL AS.

Where is SVERDRUP STEEL AS based?

SVERDRUP STEEL AS has its business address in Stavanger.

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.