BIZTRAC BETA
Other business support service activities n.e.c.

PKO AS

Org. no. 915678157 Limited company (AS) Lier Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −11,000
Equity NOK −34,000
Incorporated 2015
Share capital NOK 40,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−34k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−11k kr).

PKO AS is registered as a limited company in Lier, Buskerud with organisation number 915678157. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 2015. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Utøve næringsvirksomhet ved salg av tjenester, lT tjenester og deltagelse i andre foretak og det som naturlig står i forbindelse hermed. Samt investeringer og aksjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK −34,000

Financial health · 2024

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

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

Who owns PKO AS?

RAFAL MICHAL BAKLARZ
PKO AS
NOK 0 rev. · NOK −11,000 profit

PKO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PKO AS

Who owns PKO AS?

RAFAL MICHAL BAKLARZ is the largest registered owner, with 50.0%.

What is the revenue of PKO AS?

PKO AS had revenue of NOK 0 in 2024.

Who is the general manager of PKO AS?

Barbara Halstensen is registered as general manager of PKO AS.

Where is PKO AS based?

PKO AS has its business address in Lier.

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.