BIZTRAC BETA
COMPANY REGISTER PROFILE
833849972 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

MONSVIK HOLDING AS

Org. no. 833849972 Limited company (AS) Stavanger Incorporated 2024 Active
Ownership graph ↗
Equity NOK 30,000
Incorporated 2024
Share capital NOK 30,000

MONSVIK HOLDING AS is registered as a limited company in Stavanger, Rogaland with organisation number 833849972. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Equity
NOK 30,000
Est. value
NOK 35,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MONSVIK HOLDING AS?

ALEXANDER MERKET MONSVIK
MONSVIK HOLDING AS

MONSVIK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MONSVIK HOLDING AS own?

MONSVIK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Group structure

MONSVIK HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about MONSVIK HOLDING AS

Who owns MONSVIK HOLDING AS?

ALEXANDER MERKET MONSVIK is the largest registered owner, with 100.0%.

Who is the general manager of MONSVIK HOLDING AS?

Alexander Merket Monsvik is registered as general manager of MONSVIK HOLDING AS.

Where is MONSVIK HOLDING AS based?

MONSVIK HOLDING AS has its business address in Hundvåg.

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.