BIZTRAC BETA
Rental and operating of own or leased real estate

BYGGVEKST AS

Org. no. 911953420 Limited company (AS) Nesbyen Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 210,000
Operating profit NOK −22,000
Equity NOK −615,000
Incorporated 2013
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−615k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).

BYGGVEKST AS is registered as a limited company in Nesbyen, Buskerud with organisation number 911953420. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Kjøp,salg og utvikling av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 210,000 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 210,000
Operating profit
NOK −22,000
Equity
NOK −615,000

Financial health · 2025

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

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

Who owns BYGGVEKST AS?

MORTEN LEONSEN
BYGGVEKST AS
NOK 210,000 rev. · NOK −22,000 profit

BYGGVEKST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BYGGVEKST AS

Who owns BYGGVEKST AS?

MORTEN LEONSEN is the largest registered owner, with 50.0%.

What is the revenue of BYGGVEKST AS?

BYGGVEKST AS had revenue of NOK 210,000 in 2025.

Who is the general manager of BYGGVEKST AS?

Morten Leonsen is registered as general manager of BYGGVEKST AS.

Where is BYGGVEKST AS based?

BYGGVEKST AS has its business address in Nesbyen.

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.