BIZTRAC BETA
COMPANY REGISTER PROFILE
925604208 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

RITORNO AS

Org. no. 925604208 Limited company (AS) Moss Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2020
Share capital NOK 30,000

RITORNO AS is registered as a limited company in Moss, Østfold with organisation number 925604208. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i norske og utenlandske selskap, kjøp og salg av fast eiendom.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 30,000
▲ +0 %
Est. value
NOK 35,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RITORNO AS?

RITORNO AS
· NOK 0 profit

RITORNO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RITORNO AS own?

RITORNO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RITORNO AS

Who owns RITORNO AS?

PER-ARNE SOLBERG is the largest registered owner, with 100.0%.

Where is RITORNO AS based?

RITORNO AS has its business address in Moss.

Property

Business address Rådyrveien 9, 1534 Moss
Cadastral unit 3103-3/1176/0/0
Building Enebolig m/hybel/sokkelleil. · 2 units

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.