BIZTRAC BETA
Wholesale of machine tools

STAVANGER KORROSJON AS

Org. no. 938111278 Limited company (AS) Randaberg Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 8.3m
Operating profit NOK 608,000
Equity NOK 10.9m
Incorporated 1986
Employees 5
Share capital NOK 150,000

STAVANGER KORROSJON AS is registered as a limited company in Randaberg, Rogaland with organisation number 938111278. The business is classified under wholesale of machine tools (NACE 46.620). The company was incorporated in 1986 and has 5 registered employees. Registered share capital is NOK 150,000. The company's stated purpose is: “Salg og service av maskiner og utstyr for moderne overflatebehandling, samt hva hermed står i forbindelse, herunder å delta i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.3m in revenue and NOK 608,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.3m
Operating profit
NOK 608,000
Equity
NOK 10.9m
Est. value
NOK 7.9m

Financial health · 2024

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

Who owns STAVANGER KORROSJON AS?

BJØRG EVY SOLA
STAVANGER KORROSJON AS
NOK 8.3m rev. · NOK 608,000 profit

STAVANGER KORROSJON AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STAVANGER KORROSJON AS

Who owns STAVANGER KORROSJON AS?

BJØRG EVY SOLA is the largest registered owner, with 50.0%.

What is the revenue of STAVANGER KORROSJON AS?

STAVANGER KORROSJON AS had revenue of NOK 8.3m in 2024.

Who is the general manager of STAVANGER KORROSJON AS?

Leon Ragnar Sola is registered as general manager of STAVANGER KORROSJON AS.

Where is STAVANGER KORROSJON AS based?

STAVANGER KORROSJON AS has its business address in Randaberg.

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.