BIZTRAC BETA
Activities of excursion and event organisers

ACTIVE ADVENTURE TRAVEL AS

Org. no. 914917700 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 413,000
Equity NOK 227,000
Incorporated 2015
Share capital NOK 30,000

ACTIVE ADVENTURE TRAVEL AS is registered as a limited company in Oslo, Oslo with organisation number 914917700. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp og salg av opplevelsesreiser, forretningsreiser, aktivitetsreiser, treningsreiser, trening, kurs og coaching.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 413,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 413,000
Equity
NOK 227,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns ACTIVE ADVENTURE TRAVEL AS?

VIBEKE BEATHE BJERG
ACTIVE ADVENTURE TRAVEL AS
NOK 2.5m rev. · NOK 413,000 profit

ACTIVE ADVENTURE TRAVEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ACTIVE ADVENTURE TRAVEL AS

Who owns ACTIVE ADVENTURE TRAVEL AS?

VIBEKE BEATHE BJERG is the largest registered owner, with 100.0%.

What is the revenue of ACTIVE ADVENTURE TRAVEL AS?

ACTIVE ADVENTURE TRAVEL AS had revenue of NOK 2.5m in 2024.

Who is the general manager of ACTIVE ADVENTURE TRAVEL AS?

Vibeke Beathe Bjerg is registered as general manager of ACTIVE ADVENTURE TRAVEL AS.

Where is ACTIVE ADVENTURE TRAVEL AS based?

ACTIVE ADVENTURE TRAVEL AS has its business address in Oslo.

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.