BIZTRAC BETA
Buying and selling of own real estate

PERIVECO AS

Org. no. 977197791 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Operating profit NOK −305,000
Equity NOK 764.5m
Incorporated 1997
Share capital NOK 2.4m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−305k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

PERIVECO AS is registered as a limited company in Oslo, Oslo with organisation number 977197791. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1997. Registered share capital is NOK 2.4m, divided into 2148516 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av kapital, herunder fast eiendom, aksjer og næringsvirksomhet av enhver art, samt å drive produksjon, handel og konsulentvirksomhet og hva dermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −305,000
Equity
NOK 764.5m
Est. value
NOK 1.2bn

Financial health · 2024

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

Who owns PERIVECO AS?

HANNE MADSEN
PERIVECO AS
· NOK −305,000 profit

PERIVECO AS has 3 registered shareholders:

All shareholders and roles →

Which companies does PERIVECO AS own?

PERIVECO AS holds stakes in 14 companies:

See the full ownership structure →

Group structure

PERIVECO AS er morselskap for 1 datterselskap:

Frequently asked questions about PERIVECO AS

Who owns PERIVECO AS?

HANNE MADSEN is the largest registered owner, with 49.0%.

Who is the general manager of PERIVECO AS?

Per Werner Madsen is registered as general manager of PERIVECO AS.

Where is PERIVECO AS based?

PERIVECO 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.