biztrac. BETA
COMPANY REGISTER PROFILE
929874595 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠ROSESOL AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Rental and leasing of water transport equipment

ROSESOL AS

Org. no. 929874595 Limited company (AS) Giske Incorporated 2022 In liquidation
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK −15,000
Incorporated 2022
Share capital NOK 30,000

Signals

4 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−15k kr).
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ROSESOL AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 929874595. The business is classified under rental and leasing of water transport equipment (NACE 77.340). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer i fartøy og annet som naturlig faller sammen med dette.”.

Key figures · 2025

Operating profit
NOK −11,000
▼ −194 %
Equity
NOK −15,000
▼ −268 %

Financial health · 2025

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

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

Who owns ROSESOL AS?

ROSESOL AS
· NOK −11,000 profit

ROSESOL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROSESOL AS

Who owns ROSESOL AS?

U&R SHIPPING AS is the largest registered owner, with 100.0%.

Where is ROSESOL AS based?

ROSESOL AS has its business address in Valderøya.

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

Report a problem

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