BIZTRAC BETA
Rental and operating of own or leased real estate

BENTZEN & MYRVOLD VEKST AS

Org. no. 994235761 Limited company (AS) Asker Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 10.7m
Operating profit NOK 2.4m
Equity NOK 38.5m
Incorporated 2009
Share capital NOK 238,000

BENTZEN & MYRVOLD VEKST AS is registered as a limited company in Asker, Akershus with organisation number 994235761. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 238,000, divided into 100000 shares. The company's stated purpose is: “Investeringer av enhver art samt deltagelse i andre selskaper og hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.7m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 10.7m
Operating profit
NOK 2.4m
Equity
NOK 38.5m
Est. value
NOK 31.0m

Financial health · 2024

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

Who owns BENTZEN & MYRVOLD VEKST AS?

HOGNE MYRVOLD
BENTZEN & MYRVOLD VEKST AS
NOK 10.7m rev. · NOK 2.4m profit

BENTZEN & MYRVOLD VEKST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BENTZEN & MYRVOLD VEKST AS own?

BENTZEN & MYRVOLD VEKST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BENTZEN & MYRVOLD VEKST AS

Who owns BENTZEN & MYRVOLD VEKST AS?

HOGNE MYRVOLD is the largest registered owner, with 70.0%.

What is the revenue of BENTZEN & MYRVOLD VEKST AS?

BENTZEN & MYRVOLD VEKST AS had revenue of NOK 10.7m in 2024.

Where is BENTZEN & MYRVOLD VEKST AS based?

BENTZEN & MYRVOLD VEKST AS has its business address in Hvalstad.

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.