BIZTRAC BETA
Refrigeration installation, heat pump installation and installation of fireplaces

ENVATEC HOLDING AS

Org. no. 927009188 Limited company (AS) Hole Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −261,000
Equity NOK 12.7m
Incorporated 2021
Share capital NOK 80,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−261k kr).

ENVATEC HOLDING AS is registered as a limited company in Hole, Buskerud with organisation number 927009188. The business is classified under refrigeration installation, heat pump installation and installation of fireplaces (NACE 43.222). The company was incorporated in 2021. Registered share capital is NOK 80,000, divided into 100 shares. The company's stated purpose is: “Investeringer og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, og kjøp og slag av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2024

Operating profit
NOK −261,000
Equity
NOK 12.7m
Est. value
NOK 13.0m

Financial health · 2024

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

Who owns ENVATEC HOLDING AS?

KJELL ARILD AAEN
ENVATEC HOLDING AS
· NOK −261,000 profit

ENVATEC HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ENVATEC HOLDING AS own?

ENVATEC HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

ENVATEC HOLDING AS er morselskap for 2 datterselskaper:

Frequently asked questions about ENVATEC HOLDING AS

Who owns ENVATEC HOLDING AS?

KJELL ARILD AAEN is the largest registered owner, with 100.0%.

Where is ENVATEC HOLDING AS based?

ENVATEC HOLDING AS has its business address in Krokkleiva.

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.