BIZTRAC BETA
Other investment companies, except captive companies

CREDO CYBER HOLDING AS

Org. no. 833224832 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −893,000
Equity NOK 83.0m
Incorporated 2024
Share capital NOK 2.4m

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−893k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-22 Aksjekapital registrert 2026-04-22.

CREDO CYBER HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 833224832. The business is classified under other investment companies, except captive companies (NACE 64.312). The company was incorporated in 2024. Registered share capital is NOK 2.4m, divided into 2369070 shares. The company's stated purpose is: “Å investere i og eie aksjer og andre finansielle instrumenter eller andeler samt virksomhet som naturlig hører til dette.”.

Key figures · 2024

Operating profit
NOK −893,000
Equity
NOK 83.0m
Est. value
NOK 75.7m

Financial health · 2024

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

Who owns CREDO CYBER HOLDING AS?

FARVATN PRIVATE EQUITY AS
CREDO CYBER HOLDING AS
· NOK −893,000 profit

CREDO CYBER HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does CREDO CYBER HOLDING AS own?

CREDO CYBER HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about CREDO CYBER HOLDING AS

Who owns CREDO CYBER HOLDING AS?

FARVATN PRIVATE EQUITY AS is the largest registered owner, with 36.3%.

Where is CREDO CYBER HOLDING AS based?

CREDO CYBER HOLDING 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.