BIZTRAC BETA
Activities of excursion and event organisers

ALL ONBOARD ADVENTURE AS

Org. no. 924640537 Limited company (AS) Tønsberg Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 11.4m
Operating profit NOK 496,000
Equity NOK 421,000
Incorporated 2020
Employees 32
Share capital NOK 30,000

ALL ONBOARD ADVENTURE AS is registered as a limited company in Tønsberg, Vestfold with organisation number 924640537. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2020 and has 32 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Planlegge, selge og gjennomføre event i Norge og utlandet.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.4m in revenue and NOK 496,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.4m
Operating profit
NOK 496,000
Equity
NOK 421,000
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns ALL ONBOARD ADVENTURE AS?

AGR RØNNING INVEST AS
ALL ONBOARD ADVENTURE AS
NOK 11.4m rev. · NOK 496,000 profit

ALL ONBOARD ADVENTURE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ALL ONBOARD ADVENTURE AS own?

ALL ONBOARD ADVENTURE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ALL ONBOARD ADVENTURE AS

Who owns ALL ONBOARD ADVENTURE AS?

AGR RØNNING INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of ALL ONBOARD ADVENTURE AS?

ALL ONBOARD ADVENTURE AS had revenue of NOK 11.4m in 2024.

Where is ALL ONBOARD ADVENTURE AS based?

ALL ONBOARD ADVENTURE AS has its business address in Tolvsrød.

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.