BIZTRAC BETA
Electrical installation

AASEBØ & ULVESTAD INSTALLASJON AS

Org. no. 979476205 Limited company (AS) Volda Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 17.4m
Operating profit NOK 2.3m
Equity NOK 7.4m
Incorporated 1997
Employees 11
Share capital NOK 108,000

AASEBØ & ULVESTAD INSTALLASJON AS is registered as a limited company in Volda, Møre og Romsdal with organisation number 979476205. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 1997 and has 11 registered employees. Registered share capital is NOK 108,000, divided into 540 shares. The company's stated purpose is: “Elektrisk installasjonsverksemd, handel, utleige av fast eigedom og det som står i samband med dette, medrekna å ta del i andre selskap med liknande verksemd.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.4m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 17.4m
Operating profit
NOK 2.3m
Equity
NOK 7.4m
Est. value
NOK 10.7m

Financial health · 2024

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

Who owns AASEBØ & ULVESTAD INSTALLASJON AS?

SVEIN KÅRE FLOTE
AASEBØ & ULVESTAD INSTALLASJON AS
NOK 17.4m rev. · NOK 2.3m profit

AASEBØ & ULVESTAD INSTALLASJON AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about AASEBØ & ULVESTAD INSTALLASJON AS

Who owns AASEBØ & ULVESTAD INSTALLASJON AS?

SVEIN KÅRE FLOTE is the largest registered owner, with 33.1%.

What is the revenue of AASEBØ & ULVESTAD INSTALLASJON AS?

AASEBØ & ULVESTAD INSTALLASJON AS had revenue of NOK 17.4m in 2024.

Where is AASEBØ & ULVESTAD INSTALLASJON AS based?

AASEBØ & ULVESTAD INSTALLASJON AS has its business address in Volda.

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.