BIZTRAC BETA
Wholesale of metals and metal ores

NORWAY STEEL SOLUTIONS AS

Org. no. 987429119 Limited company (AS) Skien Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 15.0m
Operating profit NOK 291,000
Equity NOK 3.3m
Incorporated 2004
Share capital NOK 2.8m

NORWAY STEEL SOLUTIONS AS is registered as a limited company in Skien, Telemark with organisation number 987429119. The business is classified under wholesale of metals and metal ores (NACE 46.820). The company was incorporated in 2004. Registered share capital is NOK 2.8m, divided into 440 shares. The company's stated purpose is: “Handel, fabrikasjon og montasje av stålkonstruksjoner, salg av konsulenttjenester, samt virksomhet som naturlig hører sammen med dette. Selskapet skal videre kunne eie aksjer i andre selskaper, og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.0m in revenue and NOK 291,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.0m
Operating profit
NOK 291,000
Equity
NOK 3.3m
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns NORWAY STEEL SOLUTIONS AS?

NORWAY STEEL GROUP AS
NORWAY STEEL SOLUTIONS AS
NOK 15.0m rev. · NOK 291,000 profit

NORWAY STEEL SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORWAY STEEL SOLUTIONS AS

Who owns NORWAY STEEL SOLUTIONS AS?

NORWAY STEEL GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of NORWAY STEEL SOLUTIONS AS?

NORWAY STEEL SOLUTIONS AS had revenue of NOK 15.0m in 2024.

Where is NORWAY STEEL SOLUTIONS AS based?

NORWAY STEEL SOLUTIONS AS has its business address in Skien.

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.