BIZTRAC BETA
Development of building projects

PREG EIENDOMSUTVIKLING AS

Org. no. 913566173 Limited company (AS) Malvik Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 11.8m
Operating profit NOK 2.4m
Equity NOK 1.5m
Incorporated 2014
Share capital NOK 30,000

PREG EIENDOMSUTVIKLING AS is registered as a limited company in Malvik, Trøndelag with organisation number 913566173. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 600 shares. The company's stated purpose is: “Bygging, kjøp og salg av boliger, samt hva som står i nær forbindelse. Selskapet kan også delta økonomisk eller på annen måte i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.8m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 11.8m
Operating profit
NOK 2.4m
Equity
NOK 1.5m
Est. value
NOK 6.6m

Financial health · 2025

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

Who owns PREG EIENDOMSUTVIKLING AS?

KENT ARNE BJERKE
PREG EIENDOMSUTVIKLING AS
NOK 11.8m rev. · NOK 2.4m profit

PREG EIENDOMSUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PREG EIENDOMSUTVIKLING AS

Who owns PREG EIENDOMSUTVIKLING AS?

KENT ARNE BJERKE is the largest registered owner, with 50.0%.

What is the revenue of PREG EIENDOMSUTVIKLING AS?

PREG EIENDOMSUTVIKLING AS had revenue of NOK 11.8m in 2025.

Who is the general manager of PREG EIENDOMSUTVIKLING AS?

Erik Stubø is registered as general manager of PREG EIENDOMSUTVIKLING AS.

Where is PREG EIENDOMSUTVIKLING AS based?

PREG EIENDOMSUTVIKLING AS has its business address in Vikhammer.

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.