BIZTRAC BETA
Other captive investment companies

8COM ADVENTURES AS

Org. no. 928944972 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −3,000
Equity NOK 110,000
Incorporated 2022
Share capital NOK 120,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

8COM ADVENTURES AS is registered as a limited company in Oslo, Oslo with organisation number 928944972. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2022. Registered share capital is NOK 120,000, divided into 120000 shares. The company's stated purpose is: “Investere i aksjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 110,000
Est. value
NOK 100,000

Financial health · 2024

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

Who owns 8COM ADVENTURES AS?

KRISTIN AANELAND
8COM ADVENTURES AS
NOK 0 rev. · NOK −3,000 profit

8COM ADVENTURES AS has 8 registered shareholders:

All shareholders and roles →

Which companies does 8COM ADVENTURES AS own?

8COM ADVENTURES AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about 8COM ADVENTURES AS

Who owns 8COM ADVENTURES AS?

KRISTIN AANELAND is the largest registered owner, with 12.5%.

What is the revenue of 8COM ADVENTURES AS?

8COM ADVENTURES AS had revenue of NOK 0 in 2024.

Who is the general manager of 8COM ADVENTURES AS?

Marie Ameln is registered as general manager of 8COM ADVENTURES AS.

Where is 8COM ADVENTURES AS based?

8COM ADVENTURES 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.