BIZTRAC BETA
Activities of excursion and event organisers

OCEAN RALLY AS

Org. no. 932969041 Limited company (AS) Ålesund Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 216,000
Operating profit NOK −194,000
Equity NOK −194,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−194k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−194k kr).

OCEAN RALLY AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 932969041. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Arrangør av festivaler og eventer.”. The most recent filed accounts, for the 2024 financial year, show NOK 216,000 in revenue and NOK −194,000 in operating profit.

Key figures · 2024

Revenue
NOK 216,000
Operating profit
NOK −194,000
Equity
NOK −194,000

Financial health · 2024

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

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

Who owns OCEAN RALLY AS?

Trym Vetle Aasen
OCEAN RALLY AS
NOK 216,000 rev. · NOK −194,000 profit

OCEAN RALLY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OCEAN RALLY AS

Who owns OCEAN RALLY AS?

Trym Vetle Aasen is the largest registered owner, with 100.0%.

What is the revenue of OCEAN RALLY AS?

OCEAN RALLY AS had revenue of NOK 216,000 in 2024.

Who is the general manager of OCEAN RALLY AS?

Trym Vetle Aasen is registered as general manager of OCEAN RALLY AS.

Where is OCEAN RALLY AS based?

OCEAN RALLY AS has its business address in Ålesund.

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.