BIZTRAC BETA
COMPANY REGISTER PROFILE
913856368 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

PKL INVEST AS

Org. no. 913856368 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 1.1m
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

PKL INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 913856368. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Eie aksjer og/eller andeler i PricewaterhouseCoopers, i tillegg til at selskapet kan inneha andre finansielle eiendeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 1.1m
Est. value
NOK 614,000

Financial health · 2025

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

Who owns PKL INVEST AS?

PÅL KULØ LØNSETH
PKL INVEST AS
NOK 0 rev. · NOK −14,000 profit

PKL INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PKL INVEST AS

Who owns PKL INVEST AS?

PÅL KULØ LØNSETH is the largest registered owner, with 100.0%.

What is the revenue of PKL INVEST AS?

PKL INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of PKL INVEST AS?

Pål Kulø Lønseth is registered as general manager of PKL INVEST AS.

Where is PKL INVEST AS based?

PKL INVEST 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.