BIZTRAC BETA
Construction of utility projects for fluids

PA ENTREPRENØR AS

Org. no. 952159429 Limited company (AS) Oslo Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 273.4m
Operating profit NOK 16.5m
Equity NOK 86.2m
Incorporated 1989
Employees 110
Share capital NOK 20.6m

PA ENTREPRENØR AS is registered as a limited company in Oslo, Oslo with organisation number 952159429. The business is classified under construction of utility projects for fluids (NACE 42.210). The company was incorporated in 1989 and has 110 registered employees. Registered share capital is NOK 20.6m, divided into 34317 shares. The company's stated purpose is: “Alle typer virksomhet også ved deltakelse i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 273.4m in revenue and NOK 16.5m in operating profit.

Key figures · 2025

Revenue
NOK 273.4m
Operating profit
NOK 16.5m
Equity
NOK 86.2m
Est. value
NOK 99.4m

Financial health · 2025

Liquidity
2.11
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
55.0%
Very good
Equity as a share of total capital

Who owns PA ENTREPRENØR AS?

BUKTA INVEST AS
PA ENTREPRENØR AS
NOK 273.4m rev. · NOK 16.5m profit

PA ENTREPRENØR AS has 4 registered shareholders:

All shareholders and roles →

Which companies does PA ENTREPRENØR AS own?

PA ENTREPRENØR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PA ENTREPRENØR AS

Who owns PA ENTREPRENØR AS?

BUKTA INVEST AS is the largest registered owner, with 47.4%.

What is the revenue of PA ENTREPRENØR AS?

PA ENTREPRENØR AS had revenue of NOK 273.4m in 2025.

Who is the general manager of PA ENTREPRENØR AS?

Lars-Fredrik Moe-Helgesen is registered as general manager of PA ENTREPRENØR AS.

Where is PA ENTREPRENØR AS based?

PA ENTREPRENØR AS has its business address in Oslo.

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.