BIZTRAC BETA
Activities of adventure companies

TEAM ADVENTURE AS

Org. no. 928993019 Limited company (AS) Farsund Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 25,000
Equity NOK 168,000
Incorporated 2022
Share capital NOK 30,000

TEAM ADVENTURE AS is registered as a limited company in Farsund, Agder with organisation number 928993019. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utvikle, markedsføre, selge og gjennomføre opplevelser relatert til vannsport samt guiding av turister og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 25,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 25,000
Equity
NOK 168,000
Est. value
NOK 220,000

Financial health · 2025

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

Who owns TEAM ADVENTURE AS?

KARI SCHIBEVAAG AS
TEAM ADVENTURE AS
NOK 1.3m rev. · NOK 25,000 profit

TEAM ADVENTURE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TEAM ADVENTURE AS

Who owns TEAM ADVENTURE AS?

KARI SCHIBEVAAG AS is the largest registered owner, with 50.0%.

What is the revenue of TEAM ADVENTURE AS?

TEAM ADVENTURE AS had revenue of NOK 1.3m in 2025.

Who is the general manager of TEAM ADVENTURE AS?

Kari Schibevaag is registered as general manager of TEAM ADVENTURE AS.

Where is TEAM ADVENTURE AS based?

TEAM ADVENTURE AS has its business address in Farsund.

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.