BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

RICON AS

Org. no. 961172594 Limited company (AS) Stavanger Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 518,000
Operating profit NOK −84,000
Equity NOK 508,000
Incorporated 1991
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−84k kr).

RICON AS is registered as a limited company in Stavanger, Rogaland with organisation number 961172594. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 1991. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og produksjon av stålkonstruksjoner og byggevarer av enhver art, og å delta i andre selskaper med lignende formål, samt eie og utleie av utstyr og bygninger.”. The most recent filed accounts, for the 2024 financial year, show NOK 518,000 in revenue and NOK −84,000 in operating profit.

Key figures · 2024

Revenue
NOK 518,000
Operating profit
NOK −84,000
Equity
NOK 508,000
Est. value
NOK 410,000

Financial health · 2024

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

Who owns RICON AS?

SVEIN MAGNE SØRBØ
RICON AS
NOK 518,000 rev. · NOK −84,000 profit

RICON AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RICON AS

Who owns RICON AS?

SVEIN MAGNE SØRBØ is the largest registered owner, with 60.0%.

What is the revenue of RICON AS?

RICON AS had revenue of NOK 518,000 in 2024.

Who is the general manager of RICON AS?

Inger Sissel Arnesen Sørbø is registered as general manager of RICON AS.

Where is RICON AS based?

RICON 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.