BIZTRAC BETA
Sports activities n.e.c.

CREDO II AS

Org. no. 826434392 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 223.3m
Operating profit NOK 190.0m
Equity NOK 67.2m
Incorporated 2021
Share capital NOK 399,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-02-21 Aksjekapital registrert 2026-02-21.

CREDO II AS is registered as a limited company in Oslo, Oslo with organisation number 826434392. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 2021. Registered share capital is NOK 399,000, divided into 39483 shares. The company's stated purpose is: “Investere i og eie aksjer og andre finansielle instrumenter eller andeler samt virksomhet som naturlig hører med til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 223.3m in revenue and NOK 190.0m in operating profit.

Key figures · 2024

Revenue
NOK 223.3m
Operating profit
NOK 190.0m
Equity
NOK 67.2m
Est. value
NOK 465.1m

Financial health · 2024

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

Who owns CREDO II AS?

MANGO HOLDING AS
CREDO II AS
NOK 223.3m rev. · NOK 190.0m profit

CREDO II AS has 15 registered shareholders:

All shareholders and roles →

Which companies does CREDO II AS own?

CREDO II AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about CREDO II AS

Who owns CREDO II AS?

MANGO HOLDING AS is the largest registered owner, with 17.1%.

What is the revenue of CREDO II AS?

CREDO II AS had revenue of NOK 223.3m in 2024.

Where is CREDO II AS based?

CREDO II 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.