BIZTRAC BETA
Civil engineering activities

BP3 PROSJEKT AS

Org. no. 913031725 Limited company (AS) Narvik Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 13.1m
Operating profit NOK 1.3m
Equity NOK 2.7m
Incorporated 2013
Employees 7
Share capital NOK 231,000

BP3 PROSJEKT AS is registered as a limited company in Narvik, Nordland with organisation number 913031725. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2013 and has 7 registered employees. Registered share capital is NOK 231,000, divided into 231 shares. The company's stated purpose is: “Å levere tjenester innen prosjektledelse og andre tjenester/produkter som naturlig faller sammen med dette, kjøp og salg av aksjer, samt kjøp, salg og forvaltning av fast eiendom, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.1m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 13.1m
Operating profit
NOK 1.3m
Equity
NOK 2.7m
Est. value
NOK 7.5m

Financial health · 2025

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

Who owns BP3 PROSJEKT AS?

BP3 HOLDING AS
BP3 PROSJEKT AS
NOK 13.1m rev. · NOK 1.3m profit

BP3 PROSJEKT AS has 8 registered shareholders:

All shareholders and roles →

Frequently asked questions about BP3 PROSJEKT AS

Who owns BP3 PROSJEKT AS?

BP3 HOLDING AS is the largest registered owner, with 31.6%.

What is the revenue of BP3 PROSJEKT AS?

BP3 PROSJEKT AS had revenue of NOK 13.1m in 2025.

Who is the general manager of BP3 PROSJEKT AS?

Svein-Erik Høiem is registered as general manager of BP3 PROSJEKT AS.

Where is BP3 PROSJEKT AS based?

BP3 PROSJEKT AS has its business address in Narvik.

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.