BIZTRAC BETA
Rental and operating of own or leased real estate

BPO EIENDOM AS

Org. no. 925787744 Limited company (AS) Overhalla Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 762,000
Equity NOK 1.6m
Incorporated 2020
Share capital NOK 85,000

BPO EIENDOM AS is registered as a limited company in Overhalla, Trøndelag with organisation number 925787744. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 85,000, divided into 847 shares. The company's stated purpose is: “Besitte, erverve, avhende eller leie ut fast eiendom, samt virksomhet som naturlig står i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 762,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 762,000
Equity
NOK 1.6m
Est. value
NOK 2.3m

Financial health · 2024

Liquidity
0.45
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.6%
Satisfactory
Equity as a share of total capital

Who owns BPO EIENDOM AS?

BPO HOLDING AS
BPO EIENDOM AS
NOK 2.7m rev. · NOK 762,000 profit

BPO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BPO EIENDOM AS own?

BPO EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BPO EIENDOM AS

Who owns BPO EIENDOM AS?

BPO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BPO EIENDOM AS?

BPO EIENDOM AS had revenue of NOK 2.7m in 2024.

Who is the general manager of BPO EIENDOM AS?

Erlend Hasselvold is registered as general manager of BPO EIENDOM AS.

Where is BPO EIENDOM AS based?

BPO EIENDOM AS has its business address in Overhalla.

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.