BIZTRAC BETA
Other captive investment companies

INTERAKTIV INVEST AS

Org. no. 988983195 Limited company (AS) Sandnes Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −26,000
Equity NOK 5.4m
Incorporated 2005
Share capital NOK 100,000

Signals

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

INTERAKTIV INVEST AS is registered as a limited company in Sandnes, Rogaland with organisation number 988983195. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg av nødstrømsrelaterte produkter, kjøp og salg av verdipapirer, deltakelse i virksomheter og hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −26,000
Equity
NOK 5.4m
Est. value
NOK 3.7m

Financial health · 2025

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

Who owns INTERAKTIV INVEST AS?

ALV BRUELAND
INTERAKTIV INVEST AS
NOK 0 rev. · NOK −26,000 profit

INTERAKTIV INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INTERAKTIV INVEST AS

Who owns INTERAKTIV INVEST AS?

ALV BRUELAND is the largest registered owner, with 100.0%.

What is the revenue of INTERAKTIV INVEST AS?

INTERAKTIV INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of INTERAKTIV INVEST AS?

Alv Brueland is registered as general manager of INTERAKTIV INVEST AS.

Where is INTERAKTIV INVEST AS based?

INTERAKTIV INVEST AS has its business address in Sandnes.

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.