BIZTRAC BETA
Activities of adventure companies

ARCTIC RIB EVENT AS

Org. no. 985480117 Limited company (AS) Bodø Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 410,000
Operating profit NOK 116,000
Equity NOK 592,000
Incorporated 2003
Share capital NOK 180,000

ARCTIC RIB EVENT AS is registered as a limited company in Bodø, Nordland with organisation number 985480117. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2003. Registered share capital is NOK 180,000, divided into 120 shares. The company's stated purpose is: “Forestå natur/båtopplevelser for kunder. Båtforhandler. Eventbyrå.”. The most recent filed accounts, for the 2024 financial year, show NOK 410,000 in revenue and NOK 116,000 in operating profit.

Key figures · 2024

Revenue
NOK 410,000
Operating profit
NOK 116,000
Equity
NOK 592,000
Est. value
NOK 664,000

Financial health · 2024

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

Who owns ARCTIC RIB EVENT AS?

ODD IVAR JOHNSEN
ARCTIC RIB EVENT AS
NOK 410,000 rev. · NOK 116,000 profit

ARCTIC RIB EVENT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ARCTIC RIB EVENT AS own?

ARCTIC RIB EVENT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ARCTIC RIB EVENT AS

Who owns ARCTIC RIB EVENT AS?

ODD IVAR JOHNSEN is the largest registered owner, with 50.0%.

What is the revenue of ARCTIC RIB EVENT AS?

ARCTIC RIB EVENT AS had revenue of NOK 410,000 in 2024.

Who is the general manager of ARCTIC RIB EVENT AS?

Johnny Marthin Johnsen is registered as general manager of ARCTIC RIB EVENT AS.

Where is ARCTIC RIB EVENT AS based?

ARCTIC RIB EVENT AS has its business address in Bodø.

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.