BIZTRAC BETA
Other captive investment companies

STRAISVANN INVEST AS

Org. no. 989133187 Limited company (AS) Kristiansand Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5
Equity NOK 9.3m
Incorporated 2005
Share capital NOK 90,000

Signals

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

STRAISVANN INVEST AS is registered as a limited company in Kristiansand, Agder with organisation number 989133187. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 90,000, divided into 18000 shares. The company's stated purpose is: “Investere i annen forretningsvirksomhet, herunder delta i andre selskaper som aksjeeier eller ansvarlig deltaker.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5
Equity
NOK 9.3m
Est. value
NOK 14.5m

Financial health · 2025

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

Who owns STRAISVANN INVEST AS?

TOR ERLING TOBIASSEN
STRAISVANN INVEST AS
NOK 0 rev. · NOK −5 profit

STRAISVANN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STRAISVANN INVEST AS own?

STRAISVANN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STRAISVANN INVEST AS

Who owns STRAISVANN INVEST AS?

TOR ERLING TOBIASSEN is the largest registered owner, with 100.0%.

What is the revenue of STRAISVANN INVEST AS?

STRAISVANN INVEST AS had revenue of NOK 0 in 2025.

Where is STRAISVANN INVEST AS based?

STRAISVANN INVEST AS has its business address in Kristiansand S.

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.