BIZTRAC BETA
Site preparation

LYNGHAUG FJELLSPRENGNING AS

Org. no. 923003673 Limited company (AS) Sørreisa Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 22.5m
Operating profit NOK 4.3m
Equity NOK 12.2m
Incorporated 2019
Employees 8
Share capital NOK 30,000

LYNGHAUG FJELLSPRENGNING AS is registered as a limited company in Sørreisa, Troms with organisation number 923003673. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2019 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Tjenester innenfor boring, sprengning og graving, samt det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 22.5m in revenue and NOK 4.3m in operating profit.

Key figures · 2024

Revenue
NOK 22.5m
Operating profit
NOK 4.3m
Equity
NOK 12.2m
Est. value
NOK 19.7m

Financial health · 2024

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

Who owns LYNGHAUG FJELLSPRENGNING AS?

ROBIN STORELVMO LYNGHAUG
LYNGHAUG FJELLSPRENGNING AS
NOK 22.5m rev. · NOK 4.3m profit

LYNGHAUG FJELLSPRENGNING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LYNGHAUG FJELLSPRENGNING AS

Who owns LYNGHAUG FJELLSPRENGNING AS?

ROBIN STORELVMO LYNGHAUG is the largest registered owner, with 50.0%.

What is the revenue of LYNGHAUG FJELLSPRENGNING AS?

LYNGHAUG FJELLSPRENGNING AS had revenue of NOK 22.5m in 2024.

Who is the general manager of LYNGHAUG FJELLSPRENGNING AS?

Robin Storelvmo Lynghaug is registered as general manager of LYNGHAUG FJELLSPRENGNING AS.

Where is LYNGHAUG FJELLSPRENGNING AS based?

LYNGHAUG FJELLSPRENGNING AS has its business address in Sørreisa.

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.