BIZTRAC BETA
Construction of roads and motorways

LUNDEBY AS

Org. no. 918552618 Limited company (AS) Indre Østfold Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 31.6m
Operating profit NOK 6.0m
Equity NOK 14.4m
Incorporated 2017
Employees 9
Share capital NOK 150,000

LUNDEBY AS is registered as a limited company in Indre Østfold, Østfold with organisation number 918552618. The business is classified under construction of roads and motorways (NACE 42.110). The company was incorporated in 2017 and has 9 registered employees. Registered share capital is NOK 150,000, divided into 100 shares. The company's stated purpose is: “Veitransport, hovedsakelig med lastebil. Snøbrøyting, leiekjøring og annen tjenesteyting. Utleie av maskiner og utstyr. Deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 31.6m in revenue and NOK 6.0m in operating profit.

Key figures · 2024

Revenue
NOK 31.6m
Operating profit
NOK 6.0m
Equity
NOK 14.4m
Est. value
NOK 25.6m

Financial health · 2024

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

Who owns LUNDEBY AS?

LARS ERIK LUNDEBY
LUNDEBY AS
NOK 31.6m rev. · NOK 6.0m profit

LUNDEBY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LUNDEBY AS own?

LUNDEBY AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LUNDEBY AS

Who owns LUNDEBY AS?

LARS ERIK LUNDEBY is the largest registered owner, with 100.0%.

What is the revenue of LUNDEBY AS?

LUNDEBY AS had revenue of NOK 31.6m in 2024.

Who is the general manager of LUNDEBY AS?

Lars Erik Lundeby is registered as general manager of LUNDEBY AS.

Where is LUNDEBY AS based?

LUNDEBY AS has its business address in Hærland.

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.