BIZTRAC BETA
Business and other management consultancy activities

ICECO2 HOLDING AS

Org. no. 920219152 Limited company (AS) Øygarden Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −106,000
Equity NOK 1.9m
Incorporated 2017
Share capital NOK 480,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−106k kr).

ICECO2 HOLDING AS is registered as a limited company in Øygarden, Vestland with organisation number 920219152. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2017. Registered share capital is NOK 480,000, divided into 75000 shares. The company's stated purpose is: “Investeringer i aksjer og andre selskaper, konsulentvirksomhet innen endringsledelse og midlertidig ledelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −106,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −106,000
Equity
NOK 1.9m
Est. value
NOK 3.5m

Financial health · 2025

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

Who owns ICECO2 HOLDING AS?

LARS BJARNE NORDÅS
ICECO2 HOLDING AS
NOK 0 rev. · NOK −106,000 profit

ICECO2 HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ICECO2 HOLDING AS own?

ICECO2 HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ICECO2 HOLDING AS

Who owns ICECO2 HOLDING AS?

LARS BJARNE NORDÅS is the largest registered owner, with 33.3%.

What is the revenue of ICECO2 HOLDING AS?

ICECO2 HOLDING AS had revenue of NOK 0 in 2025.

Where is ICECO2 HOLDING AS based?

ICECO2 HOLDING AS has its business address in Straume.

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.