BIZTRAC BETA
Construction of residential and non-residential buildings

LUNDEBYGG AS

Org. no. 980643034 Limited company (AS) Bærum Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 324,000
Operating profit NOK 13,000
Equity NOK −90,000
Incorporated 1998
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−90k kr).

LUNDEBYGG AS is registered as a limited company in Bærum, Akershus with organisation number 980643034. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1998. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drive innenfor bygg og anlegg samt utleie og alt i forbindelse hermed.”. The most recent filed accounts, for the 2024 financial year, show NOK 324,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2024

Revenue
NOK 324,000
Operating profit
NOK 13,000
Equity
NOK −90,000
Est. value
NOK 66,000

Financial health · 2024

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1848.4%
Weak
Equity as a share of total capital

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

Who owns LUNDEBYGG AS?

LARS DIDRIK LUNDE
LUNDEBYGG AS
NOK 324,000 rev. · NOK 13,000 profit

LUNDEBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUNDEBYGG AS

Who owns LUNDEBYGG AS?

LARS DIDRIK LUNDE is the largest registered owner, with 100.0%.

What is the revenue of LUNDEBYGG AS?

LUNDEBYGG AS had revenue of NOK 324,000 in 2024.

Who is the general manager of LUNDEBYGG AS?

Lars Didrik Lunde is registered as general manager of LUNDEBYGG AS.

Where is LUNDEBYGG AS based?

LUNDEBYGG AS has its business address in Kolsås.

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.