BIZTRAC BETA
Computer programming activities

PEXIP HOLDING ASA

Org. no. 919850175 Public limited company (ASA) Oslo Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −19.9m
Equity NOK 1.3bn
Incorporated 2017
Share capital NOK 1.6m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−19,9 mill kr).

PEXIP HOLDING ASA is registered as a public limited company in Oslo, Oslo with organisation number 919850175. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2017. Registered share capital is NOK 1.6m, divided into 104429671 shares. The company's stated purpose is: “Å drive, eie og/eller investere i virksomhet eller utvikling relatert til telekommunikasjonstjenester og telekommunikasjonsløsninger, investering i andre selskaper eller utvikling av annen virksomhet, og alt som står i forbindelse med de forannevnte virksomheter.”.

Key figures · 2024

Operating profit
NOK −19.9m
Equity
NOK 1.3bn
Est. value
NOK 703.2m

Financial health · 2024

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

Who owns PEXIP HOLDING ASA?

HOLMEN SPESIALFOND
PEXIP HOLDING ASA
· NOK −19.9m profit

PEXIP HOLDING ASA has 20+ registered shareholders:

All shareholders and roles →

Which companies does PEXIP HOLDING ASA own?

PEXIP HOLDING ASA holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about PEXIP HOLDING ASA

Who owns PEXIP HOLDING ASA?

HOLMEN SPESIALFOND is the largest registered owner, with 8.3%.

Who is the general manager of PEXIP HOLDING ASA?

Trond Klethagen Johannessen is registered as general manager of PEXIP HOLDING ASA.

Where is PEXIP HOLDING ASA based?

PEXIP HOLDING ASA 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.