BIZTRAC BETA
Activities of tour guides

OFFBEAT ADVENTURES AS

Org. no. 930555274 Limited company (AS) Vestnes Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 290,000
Operating profit NOK −150,000
Equity NOK 41,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−150k kr).

OFFBEAT ADVENTURES AS is registered as a limited company in Vestnes, Møre og Romsdal with organisation number 930555274. The business is classified under activities of tour guides (NACE 79.902). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Guidede bærekraftige opplevelser i fjord-Norge.”. The most recent filed accounts, for the 2025 financial year, show NOK 290,000 in revenue and NOK −150,000 in operating profit.

Key figures · 2025

Revenue
NOK 290,000
Operating profit
NOK −150,000
Equity
NOK 41,000
Est. value
NOK 204,000

Financial health · 2025

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

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

Who owns OFFBEAT ADVENTURES AS?

ANNIKEN AAKVIK
OFFBEAT ADVENTURES AS
NOK 290,000 rev. · NOK −150,000 profit

OFFBEAT ADVENTURES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OFFBEAT ADVENTURES AS

Who owns OFFBEAT ADVENTURES AS?

ANNIKEN AAKVIK is the largest registered owner, with 100.0%.

What is the revenue of OFFBEAT ADVENTURES AS?

OFFBEAT ADVENTURES AS had revenue of NOK 290,000 in 2025.

Who is the general manager of OFFBEAT ADVENTURES AS?

Anniken Aakvik is registered as general manager of OFFBEAT ADVENTURES AS.

Where is OFFBEAT ADVENTURES AS based?

OFFBEAT ADVENTURES AS has its business address in Vestnes.

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.