biztrac. BETA
COMPANY REGISTER PROFILE
996914658 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
In liquidation UPDATED 03.10.2026
⚠CADIO AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Manufacture of non-domestic air conditioning equipment

CADIO AS

Org. no. 996914658 Limited company (AS) Trondheim Incorporated 2011 In liquidation
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −60,000
Equity NOK 145,000
Incorporated 2011
Share capital NOK 200,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−60k kr).

CADIO AS is registered as a limited company in Trondheim, Trøndelag with organisation number 996914658. The business is classified under manufacture of non-domestic air conditioning equipment (NACE 28.250). The company was incorporated in 2011. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Utvikling, produksjon og salg av kuldeanlegg med naturlige kuldemedier og system for varmegjenvinning i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −60,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −60,000
▼ −155 %
Equity
NOK 145,000
▼ −29 %

Financial health · 2025

Liquidity
24.80
Very good
Current assets ÷ current liabilities
Profitability
-14.6%
Not satisfactory
Return on total assets
Solidity
96.0%
Very good
Equity as a share of total capital

Who owns CADIO AS?

CADIO AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about CADIO AS

Who owns CADIO AS?

Martin Lillebudal is the largest registered owner, with 39.0%.

What is the revenue of CADIO AS?

CADIO AS had revenue of NOK 0 in 2025.

Where is CADIO AS based?

CADIO AS has its business address in Heimdal.

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.