BIZTRAC BETA
Rental and operating of own or leased real estate

VPM HOLDING AS

Org. no. 913287908 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 891,000
Operating profit NOK 427,000
Equity NOK 978,000
Incorporated 2014
Share capital NOK 30,000

VPM HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 913287908. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av aksjer. Kjøp og salg av eiendom. Eierskap av andre firmaer, og andre tjenester og produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 891,000 in revenue and NOK 427,000 in operating profit.

Key figures · 2024

Revenue
NOK 891,000
Operating profit
NOK 427,000
Equity
NOK 978,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns VPM HOLDING AS?

ARSHAD MUNIR
VPM HOLDING AS
NOK 891,000 rev. · NOK 427,000 profit

VPM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VPM HOLDING AS own?

VPM HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VPM HOLDING AS

Who owns VPM HOLDING AS?

ARSHAD MUNIR is the largest registered owner, with 100.0%.

What is the revenue of VPM HOLDING AS?

VPM HOLDING AS had revenue of NOK 891,000 in 2024.

Who is the general manager of VPM HOLDING AS?

Arshad Munir is registered as general manager of VPM HOLDING AS.

Where is VPM HOLDING AS based?

VPM HOLDING AS has its business address in Oslo.

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.