BIZTRAC BETA
Site preparation

LUNDVOLL SERVICE AS

Org. no. 926425781 Limited company (AS) Lyngen Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 318,000
Equity NOK 294,000
Incorporated 2020
Share capital NOK 30,000

LUNDVOLL SERVICE AS is registered as a limited company in Lyngen, Troms with organisation number 926425781. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Maskinentreprenør, herunder kjøp og salg av maskiner, utleie av sjåførtjenester og maskiner. Byggvedlikehold, snekkring og montasje, utleie av slike tjenester og kjøp og salg av bygg og fast eiendom. Samt det som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 318,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 318,000
Equity
NOK 294,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns LUNDVOLL SERVICE AS?

JOHN ARNE LUNDVOLL
LUNDVOLL SERVICE AS
NOK 1.6m rev. · NOK 318,000 profit

LUNDVOLL SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUNDVOLL SERVICE AS

Who owns LUNDVOLL SERVICE AS?

JOHN ARNE LUNDVOLL is the largest registered owner, with 100.0%.

What is the revenue of LUNDVOLL SERVICE AS?

LUNDVOLL SERVICE AS had revenue of NOK 1.6m in 2024.

Who is the general manager of LUNDVOLL SERVICE AS?

John Arne Lundvoll is registered as general manager of LUNDVOLL SERVICE AS.

Where is LUNDVOLL SERVICE AS based?

LUNDVOLL SERVICE AS has its business address in Lyngseidet.

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.