BIZTRAC BETA
Construction of residential and non-residential buildings

HP BYGG AS

Org. no. 916543107 Limited company (AS) Vågå Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 17.7m
Operating profit NOK 893,000
Equity NOK 2.0m
Incorporated 2016
Employees 7
Share capital NOK 30,000

HP BYGG AS is registered as a limited company in Vågå, Innlandet with organisation number 916543107. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Byggevirksomhet, samt annen virksomhet som faller naturlig inn under dette, herunder å eie aksjer i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 17.7m in revenue and NOK 893,000 in operating profit.

Key figures · 2025

Revenue
NOK 17.7m
Operating profit
NOK 893,000
Equity
NOK 2.0m
Est. value
NOK 3.9m

Financial health · 2025

Liquidity
1.41
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.8%
Good
Equity as a share of total capital

Who owns HP BYGG AS?

HANS PETTER BAKKE
HP BYGG AS
NOK 17.7m rev. · NOK 893,000 profit

HP BYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HP BYGG AS own?

HP BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HP BYGG AS

Who owns HP BYGG AS?

HANS PETTER BAKKE is the largest registered owner, with 100.0%.

What is the revenue of HP BYGG AS?

HP BYGG AS had revenue of NOK 17.7m in 2025.

Who is the general manager of HP BYGG AS?

Hans Petter Bakke is registered as general manager of HP BYGG AS.

Where is HP BYGG AS based?

HP BYGG AS has its business address in Tessanden.

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.