BIZTRAC BETA
Construction of residential and non-residential buildings

PVP EIENDOM AS

Org. no. 929397312 Limited company (AS) Kongsvinger Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −36,000
Equity NOK −214,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−214k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−36k kr).

PVP EIENDOM AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 929397312. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Oppføring av bygg og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”.

Key figures · 2024

Operating profit
NOK −36,000
Equity
NOK −214,000

Financial health · 2024

Liquidity
220.18
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-9.7%
Weak
Equity as a share of total capital

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

Who owns PVP EIENDOM AS?

KEV HOLDING AS
PVP EIENDOM AS
· NOK −36,000 profit

PVP EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PVP EIENDOM AS

Who owns PVP EIENDOM AS?

KEV HOLDING AS is the largest registered owner, with 33.3%.

Who is the general manager of PVP EIENDOM AS?

Bjørn Haakon Pramm Platek is registered as general manager of PVP EIENDOM AS.

Where is PVP EIENDOM AS based?

PVP EIENDOM AS has its business address in Kongsvinger.

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.