BIZTRAC BETA
Other captive investment companies

VASSTVEDT HOLDING AS

Org. no. 989081683 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −29,000
Equity NOK 11.7m
Incorporated 2005
Share capital NOK 148,000

Signals

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

VASSTVEDT HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 989081683. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 148,000, divided into 4924872 shares. The company's stated purpose is: “investeringer i andre selskaper, investeringer i fast eiendom, samt finansielle investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −29,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −29,000
Equity
NOK 11.7m
Est. value
NOK 11.4m

Financial health · 2025

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

Who owns VASSTVEDT HOLDING AS?

KRISTINE SKOLT GROSÅS
VASSTVEDT HOLDING AS
NOK 0 rev. · NOK −29,000 profit

VASSTVEDT HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does VASSTVEDT HOLDING AS own?

VASSTVEDT HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VASSTVEDT HOLDING AS

Who owns VASSTVEDT HOLDING AS?

KRISTINE SKOLT GROSÅS is the largest registered owner, with 69.5%.

What is the revenue of VASSTVEDT HOLDING AS?

VASSTVEDT HOLDING AS had revenue of NOK 0 in 2025.

Where is VASSTVEDT HOLDING AS based?

VASSTVEDT HOLDING AS has its business address in Snarøya.

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.