BIZTRAC BETA
Construction of utility projects for electricity and telecommunications on land

BERGUM ANLEGGSTEKNIKK AS

Org. no. 926526421 Limited company (AS) Luster Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 18.0m
Operating profit NOK 2.2m
Equity NOK 4.9m
Incorporated 2021
Employees 6
Share capital NOK 30,000

BERGUM ANLEGGSTEKNIKK AS is registered as a limited company in Luster, Vestland with organisation number 926526421. The business is classified under construction of utility projects for electricity and telecommunications on land (NACE 42.222). The company was incorporated in 2021 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utføring av maskin og anleggstjenester, reparasjon av maskiner og utstyr, annet som naturlig hører med under dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.0m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 18.0m
Operating profit
NOK 2.2m
Equity
NOK 4.9m
Est. value
NOK 9.1m

Financial health · 2024

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

Who owns BERGUM ANLEGGSTEKNIKK AS?

LYKKESTEIN HOLDING AS
BERGUM ANLEGGSTEKNIKK AS
NOK 18.0m rev. · NOK 2.2m profit

BERGUM ANLEGGSTEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGUM ANLEGGSTEKNIKK AS

Who owns BERGUM ANLEGGSTEKNIKK AS?

LYKKESTEIN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BERGUM ANLEGGSTEKNIKK AS?

BERGUM ANLEGGSTEKNIKK AS had revenue of NOK 18.0m in 2024.

Where is BERGUM ANLEGGSTEKNIKK AS based?

BERGUM ANLEGGSTEKNIKK AS has its business address in Marifjøra.

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.