BIZTRAC BETA
Computer consultancy and computer facilities management activities

PARTUM CONSULT AS

Org. no. 922747881 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −32,000
Equity NOK 640,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

PARTUM CONSULT AS is registered as a limited company in Oslo, Oslo with organisation number 922747881. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet, finansiell og annen tjenesteyting, kjøp og salg av verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −32,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −32,000
Equity
NOK 640,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns PARTUM CONSULT AS?

PREBEN CHRISTIAN ANKER
PARTUM CONSULT AS
NOK 0 rev. · NOK −32,000 profit

PARTUM CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PARTUM CONSULT AS

Who owns PARTUM CONSULT AS?

PREBEN CHRISTIAN ANKER is the largest registered owner, with 100.0%.

What is the revenue of PARTUM CONSULT AS?

PARTUM CONSULT AS had revenue of NOK 0 in 2025.

Who is the general manager of PARTUM CONSULT AS?

Preben Christian Anker is registered as general manager of PARTUM CONSULT AS.

Where is PARTUM CONSULT AS based?

PARTUM CONSULT 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.