BIZTRAC BETA
Other captive investment companies

MARIANNE VONSTETT AS

Org. no. 989114336 Limited company (AS) Bamble Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −9,000
Equity NOK 415,000
Incorporated 2005
Share capital NOK 135,000

Signals

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

MARIANNE VONSTETT AS is registered as a limited company in Bamble, Telemark with organisation number 989114336. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 135,000, divided into 4 shares. The company's stated purpose is: “Investering og deltakelse i andre selskaper og det som naturlig hører innunder dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 415,000
Est. value
NOK 228,000

Financial health · 2024

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

Who owns MARIANNE VONSTETT AS?

No shareholders are registered for MARIANNE VONSTETT AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does MARIANNE VONSTETT AS own?

MARIANNE VONSTETT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MARIANNE VONSTETT AS

What is the revenue of MARIANNE VONSTETT AS?

MARIANNE VONSTETT AS had revenue of NOK 0 in 2024.

Who is the general manager of MARIANNE VONSTETT AS?

Marianne Vonstett is registered as general manager of MARIANNE VONSTETT AS.

Where is MARIANNE VONSTETT AS based?

MARIANNE VONSTETT AS has its business address in Stathelle.

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.