biztrac. BETA
COMPANY REGISTER PROFILE
932418045 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other education activities

CALDENBY KOMPETANSE AS

Org. no. 932418045 Limited company (AS) Askøy Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 5.1m
Operating profit NOK 695,000
Equity NOK 1.1m
Incorporated 2023
Share capital NOK 30,000

CALDENBY KOMPETANSE AS is registered as a limited company in Askøy, Vestland with organisation number 932418045. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Opplæring og undervisningstjenester og annet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.1m in revenue and NOK 695,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.1m
▲ +10 %
Operating profit
NOK 695,000
▲ +65 %
Equity
NOK 1.1m
▲ +33 %
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
1.91
Good
Current assets ÷ current liabilities
Profitability
33.1%
Very good
Return on total assets
Solidity
44.6%
Very good
Equity as a share of total capital

Who owns CALDENBY KOMPETANSE AS?

CALDENBY KOMPETANSE AS
NOK 5.1m rev. · NOK 695,000 profit

CALDENBY KOMPETANSE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does CALDENBY KOMPETANSE AS own?

CALDENBY KOMPETANSE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CALDENBY KOMPETANSE AS

Who owns CALDENBY KOMPETANSE AS?

Torill Bakke is the largest registered owner, with 50.0%.

What is the revenue of CALDENBY KOMPETANSE AS?

CALDENBY KOMPETANSE AS had revenue of NOK 5.1m in 2025.

Where is CALDENBY KOMPETANSE AS based?

CALDENBY KOMPETANSE AS has its business address in Kleppestø.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.