BIZTRAC BETA
Computer consultancy and computer facilities management activities

PROVATO CDI AS

Org. no. 922693838 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.6m
Operating profit NOK −3,000
Equity NOK 417,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

PROVATO CDI AS is registered as a limited company in Oslo, Oslo with organisation number 922693838. 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 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen IT og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6m in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.6m
Operating profit
NOK −3,000
Equity
NOK 417,000
Est. value
NOK 4.6m

Financial health · 2024

Liquidity
1.49
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.8%
Good
Equity as a share of total capital

Who owns PROVATO CDI AS?

ANDREAS VATNE
PROVATO CDI AS
NOK 2.6m rev. · NOK −3,000 profit

PROVATO CDI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROVATO CDI AS

Who owns PROVATO CDI AS?

ANDREAS VATNE is the largest registered owner, with 100.0%.

What is the revenue of PROVATO CDI AS?

PROVATO CDI AS had revenue of NOK 2.6m in 2024.

Who is the general manager of PROVATO CDI AS?

Andreas Vatne is registered as general manager of PROVATO CDI AS.

Where is PROVATO CDI AS based?

PROVATO CDI 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.