BIZTRAC BETA
Rental and operating of own or leased real estate

HPC EIENDOM AS

Org. no. 984414420 Limited company (AS) Elverum Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 209,000
Operating profit NOK 69,000
Equity NOK 43,000
Incorporated 2002
Share capital NOK 100,000

HPC EIENDOM AS is registered as a limited company in Elverum, Innlandet with organisation number 984414420. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i fast eiendom, finansielle investeringer og deltagelse i i andre selskaper samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 209,000 in revenue and NOK 69,000 in operating profit.

Key figures · 2025

Revenue
NOK 209,000
Operating profit
NOK 69,000
Equity
NOK 43,000
Est. value
NOK 148,000

Financial health · 2025

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

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

Who owns HPC EIENDOM AS?

HANS PETTER CARLSSON
HPC EIENDOM AS
NOK 209,000 rev. · NOK 69,000 profit

HPC EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HPC EIENDOM AS

Who owns HPC EIENDOM AS?

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

What is the revenue of HPC EIENDOM AS?

HPC EIENDOM AS had revenue of NOK 209,000 in 2025.

Who is the general manager of HPC EIENDOM AS?

Hans Petter Carlsson is registered as general manager of HPC EIENDOM AS.

Where is HPC EIENDOM AS based?

HPC EIENDOM AS has its business address in Elverum.

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.