BIZTRAC BETA
Other education activities

CREDO KOMPETANSESENTER AS

Org. no. 925058823 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 640,000
Equity NOK 1.2m
Incorporated 2020
Share capital NOK 30,000

CREDO KOMPETANSESENTER AS is registered as a limited company in Oslo, Oslo with organisation number 925058823. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Et non-profit aksjeselskap som jobber for å endre kunnskap, ferdigheter og holdninger om verdien av jorden. Denne kompetansen skal formidle og engasjere oppmerksomheten til alle som er relevant for et helt livsløp. Selskapet skal søke og motta bidrag fra andre for å oppnå formålet, både nasjonalt og internasjonalt. Selskapet kan selge produkter og tjenester, men har ikke som formål å drive næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 640,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 640,000
Equity
NOK 1.2m
Est. value
NOK 3.0m

Financial health · 2024

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

Who owns CREDO KOMPETANSESENTER AS?

No shareholders are registered for CREDO KOMPETANSESENTER AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about CREDO KOMPETANSESENTER AS

What is the revenue of CREDO KOMPETANSESENTER AS?

CREDO KOMPETANSESENTER AS had revenue of NOK 1.1m in 2024.

Where is CREDO KOMPETANSESENTER AS based?

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