BIZTRAC BETA
Construction of residential and non-residential buildings

LM BYGGPROSJEKT AS

Org. no. 927826801 Limited company (AS) Lillehammer Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 326,000
Equity NOK 50,000
Incorporated 2021
Share capital NOK 30,000

LM BYGGPROSJEKT AS is registered as a limited company in Lillehammer, Innlandet with organisation number 927826801. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Oppføring av bygg, kjøp og salg av eiendom, utleie av eiendom og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 326,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 326,000
Equity
NOK 50,000
Est. value
NOK 1.0m

Financial health · 2024

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.6%
Weak
Equity as a share of total capital

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

Who owns LM BYGGPROSJEKT AS?

ARNE LISTAD
LM BYGGPROSJEKT AS
NOK 3.0m rev. · NOK 326,000 profit

LM BYGGPROSJEKT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LM BYGGPROSJEKT AS

Who owns LM BYGGPROSJEKT AS?

ARNE LISTAD is the largest registered owner, with 50.0%.

What is the revenue of LM BYGGPROSJEKT AS?

LM BYGGPROSJEKT AS had revenue of NOK 3.0m in 2025.

Who is the general manager of LM BYGGPROSJEKT AS?

Arne Listad is registered as general manager of LM BYGGPROSJEKT AS.

Where is LM BYGGPROSJEKT AS based?

LM BYGGPROSJEKT AS has its business address in Lillehammer.

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.