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

ØEN KULDETEKNIKK AS

Org. no. 834263602 Limited company (AS) Volda Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −500
Equity NOK 22,000
Incorporated 2024
Employees 18
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−500 kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ØEN KULDETEKNIKK AS is registered as a limited company in Volda, Møre og Romsdal with organisation number 834263602. The business is classified under refrigeration installation, heat pump installation and installation of fireplaces (NACE 43.222). The company was incorporated in 2024 and has 18 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Prosjektering, levering, montering av kulde- varmepumpeanlegg og El-tavler.”.

Key figures · 2024

Operating profit
NOK −500
Equity
NOK 22,000
Est. value
NOK 23,000

Financial health · 2024

Liquidity
4.13
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
75.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ØEN KULDETEKNIKK AS?

NYE ØEN INVEST AS
ØEN KULDETEKNIKK AS
· NOK −500 profit

ØEN KULDETEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØEN KULDETEKNIKK AS own?

ØEN KULDETEKNIKK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ØEN KULDETEKNIKK AS

Who owns ØEN KULDETEKNIKK AS?

NYE ØEN INVEST AS is the largest registered owner, with 100.0%.

Where is ØEN KULDETEKNIKK AS based?

ØEN KULDETEKNIKK AS has its business address in Hornindal.

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.