BIZTRAC BETA
Construction of residential and non-residential buildings

LEREGGEN BYGG AS

Org. no. 935512700 Limited company (AS) Melhus Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 897,000
Operating profit NOK 103,000
Equity NOK 167,000
Incorporated 2025
Share capital NOK 100,000

LEREGGEN BYGG AS is registered as a limited company in Melhus, Trøndelag with organisation number 935512700. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Tilby tømrertjenester, inkludert, men ikke begrenset til, oppføring, vedlikehold, og reparasjon av bygninger, konstruksjon av trestrukturer, og andre relaterte tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 897,000 in revenue and NOK 103,000 in operating profit.

Key figures · 2025

Revenue
NOK 897,000
Operating profit
NOK 103,000
Equity
NOK 167,000
Est. value
NOK 376,000

Financial health · 2025

Liquidity
0.89
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.6%
Good
Equity as a share of total capital

Who owns LEREGGEN BYGG AS?

VEGARD LEREGGEN
LEREGGEN BYGG AS
NOK 897,000 rev. · NOK 103,000 profit

LEREGGEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEREGGEN BYGG AS

Who owns LEREGGEN BYGG AS?

VEGARD LEREGGEN is the largest registered owner, with 100.0%.

What is the revenue of LEREGGEN BYGG AS?

LEREGGEN BYGG AS had revenue of NOK 897,000 in 2025.

Who is the general manager of LEREGGEN BYGG AS?

Vegard Lereggen is registered as general manager of LEREGGEN BYGG AS.

Where is LEREGGEN BYGG AS based?

LEREGGEN BYGG AS has its business address in Melhus.

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.