biztrac. BETA
COMPANY REGISTER PROFILE
918679235 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

CADEL SOLUTIONS AS

Org. no. 918679235 Limited company (AS) Stavanger Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 30.4m
Operating profit NOK 7.1m
Equity NOK 3.0m
Incorporated 2017
Employees 10
Share capital NOK 135,000

CADEL SOLUTIONS AS is registered as a limited company in Stavanger, Rogaland with organisation number 918679235. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2017 and has 10 registered employees. Registered share capital is NOK 135,000, divided into 150 shares. The company's stated purpose is: “Rådgivning, BIM og konsulentarbeid innen elektro, automasjon og telecom, samt annen virksomhet som faller naturlig under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 30.4m in revenue and NOK 7.1m in operating profit.

Key figures · 2025

Revenue
NOK 30.4m
▲ +20 %
Operating profit
NOK 7.1m
▲ +15 %
Equity
NOK 3.0m
▲ +33 %
Est. value
NOK 27.7m

Financial health · 2025

Liquidity
1.21
Satisfactory
Current assets ÷ current liabilities
Profitability
52.7%
Very good
Return on total assets
Solidity
18.2%
Good
Equity as a share of total capital

Who owns CADEL SOLUTIONS AS?

CADEL SOLUTIONS AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about CADEL SOLUTIONS AS

Who owns CADEL SOLUTIONS AS?

LEAN HOLDING AS is the largest registered owner, with 16.7%.

What is the revenue of CADEL SOLUTIONS AS?

CADEL SOLUTIONS AS had revenue of NOK 30.4m in 2025.

Who is the general manager of CADEL SOLUTIONS AS?

Kristoffer Melhus Rødne is registered as general manager of CADEL SOLUTIONS AS.

Where is CADEL SOLUTIONS AS based?

CADEL SOLUTIONS AS has its business address in Stavanger.

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.