BIZTRAC BETA
Civil engineering activities

PL CONSULTING AS

Org. no. 928831213 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK 26,000
Incorporated 2022
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

PL CONSULTING AS is registered as a limited company in Bærum, Akershus with organisation number 928831213. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2022. Registered share capital is NOK 50,000, divided into 5 shares. The company's stated purpose is: “Konsulentvirksomhet innenfor bygg og anlegg og andre områder som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2024

Operating profit
NOK −9,000
Equity
NOK 26,000
Est. value
NOK 43,000

Financial health · 2024

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

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

Who owns PL CONSULTING AS?

PER OLOF LARSSON
PL CONSULTING AS
· NOK −9,000 profit

PL CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PL CONSULTING AS own?

PL CONSULTING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PL CONSULTING AS

Who owns PL CONSULTING AS?

PER OLOF LARSSON is the largest registered owner, with 100.0%.

Who is the general manager of PL CONSULTING AS?

Per Olof Larsson is registered as general manager of PL CONSULTING AS.

Where is PL CONSULTING AS based?

PL CONSULTING AS has its business address in Lommedalen.

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.