BIZTRAC BETA
Electrical installation

KONGSHAVN AUTOMASJON AS

Org. no. 988987409 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 290,000
Equity NOK 40,000
Incorporated 2005
Share capital NOK 102,000

KONGSHAVN AUTOMASJON AS is registered as a limited company in Bergen, Vestland with organisation number 988987409. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2005. Registered share capital is NOK 102,000, divided into 102 shares. The company's stated purpose is: “Elektroinstallasjon og automasjon, engineering-og konsulenttjenester, samt dertil hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 290,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 290,000
Equity
NOK 40,000
Est. value
NOK 806,000

Financial health · 2024

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.5%
Weak
Equity as a share of total capital

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

Who owns KONGSHAVN AUTOMASJON AS?

SKAUGE INNOVASJON AS
KONGSHAVN AUTOMASJON AS
NOK 2.5m rev. · NOK 290,000 profit

KONGSHAVN AUTOMASJON AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KONGSHAVN AUTOMASJON AS

Who owns KONGSHAVN AUTOMASJON AS?

SKAUGE INNOVASJON AS is the largest registered owner, with 50.0%.

What is the revenue of KONGSHAVN AUTOMASJON AS?

KONGSHAVN AUTOMASJON AS had revenue of NOK 2.5m in 2025.

Who is the general manager of KONGSHAVN AUTOMASJON AS?

Harry Haldorsen is registered as general manager of KONGSHAVN AUTOMASJON AS.

Where is KONGSHAVN AUTOMASJON AS based?

KONGSHAVN AUTOMASJON AS has its business address in Godvik.

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.