BIZTRAC BETA
Wholesale of other machinery and equipment

PIXIMA AS

Org. no. 988143332 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 3,000
Operating profit NOK −35,000
Equity NOK −596,000
Incorporated 2005
Share capital NOK 102,000

Signals

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

PIXIMA AS is registered as a limited company in Oslo, Oslo with organisation number 988143332. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2005. Registered share capital is NOK 102,000, divided into 102000 shares. The company's stated purpose is: “Kjøp og salg av varer og tjenester innenfor IT, elektronikk og økonomi samt deltagelse i tilsvarende virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 3,000 in revenue and NOK −35,000 in operating profit.

Key figures · 2024

Revenue
NOK 3,000
Operating profit
NOK −35,000
Equity
NOK −596,000

Financial health · 2024

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

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

Who owns PIXIMA AS?

ODD SVEIN KJELDSBERG
PIXIMA AS
NOK 3,000 rev. · NOK −35,000 profit

PIXIMA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PIXIMA AS

Who owns PIXIMA AS?

ODD SVEIN KJELDSBERG is the largest registered owner, with 100.0%.

What is the revenue of PIXIMA AS?

PIXIMA AS had revenue of NOK 3,000 in 2024.

Who is the general manager of PIXIMA AS?

Odd Svein Kjeldsberg is registered as general manager of PIXIMA AS.

Where is PIXIMA AS based?

PIXIMA 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.