BIZTRAC BETA
Construction of residential and non-residential buildings

HP BYGGSERVICE AS

Org. no. 995215810 Limited company (AS) Asker Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 557,000
Operating profit NOK −201,000
Equity NOK −67,000
Incorporated 2010
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−67k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−201k kr).

HP BYGGSERVICE AS is registered as a limited company in Asker, Akershus with organisation number 995215810. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Bygge- og anleggsvirksomhet samt handel med brukte- og antikke varer og varepartier.”. The most recent filed accounts, for the 2025 financial year, show NOK 557,000 in revenue and NOK −201,000 in operating profit.

Key figures · 2025

Revenue
NOK 557,000
Operating profit
NOK −201,000
Equity
NOK −67,000

Financial health · 2025

Liquidity
0.46
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-31.4%
Weak
Equity as a share of total capital

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

Who owns HP BYGGSERVICE AS?

ERIK HAUBJERG PETERSEN
HP BYGGSERVICE AS
NOK 557,000 rev. · NOK −201,000 profit

HP BYGGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HP BYGGSERVICE AS

Who owns HP BYGGSERVICE AS?

ERIK HAUBJERG PETERSEN is the largest registered owner, with 100.0%.

What is the revenue of HP BYGGSERVICE AS?

HP BYGGSERVICE AS had revenue of NOK 557,000 in 2025.

Where is HP BYGGSERVICE AS based?

HP BYGGSERVICE AS has its business address in Nesøya.

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.